It looks like you're new here. If you want to get involved, click one of these buttons!
I continue to be impressed by this software. A few miscellaneous observations or questions (I'm running 0.23 on Windows 7):
When you add a shortcut key from a menu item, if there is already an existing use for that shortcut key, then I typically find that both functions cease to work. For instance if you write a script and assign it Ctrl-B then not only does your current script not run with Ctrl-B but also the original binding for Ctrl-B (which happens to be "Duplicate selected object" fails to work. Right now my workaround is to first do File > Setup > Key bindings, and scroll down the list to find a shortcut key not in use, then using it for the Ruby script I'm writing. I suggest it would be preferable for the script to generate a warning or error at runtime if you try to assign a key that's already in use..
When you use Ruby to remove a shortcut key from an existing key binding (by assigning it "") or to replace a shortcut key by overwriting it with another one, the changes are not reflected in the list found at File > Setup > Key Bindings.
I love this program and want to help others to not have a hard time learning how to write macros. I have a bunch of scripts I'd like to share. At worst these would be example scripts others could learn from but may not use directly. At best these would be nicely commented and robust tools that others can actually use, as-is, in their daily work flow. I think or hope others in the community would also want to contribute. I could post each one as a Forum post, but then they get lost in the other posts. Are there any plans for a sort of "Matlab File Exchange"-type of community website where anyone can post scripts along with descriptions and example usages (and going further, eventually user comments, ratings, etc)? I think this would be a valuable tool, but am aware it is a lot of work to set up on your website. Do you have any other suggestions for how I can make my scripts publicly accessible and easy to find or stumble upon and therefore useful for others both in learning and production stages?
In an old forum post, someone mentioned you are working on a 3d software, but I find no links online with a quick Google search. Is this public yet and do you wish to share a link? I'd be very interested in what else you've come up with.
I think the following may be a Windows thing. When I have Macro Editor open, say I select a polygon and then run a script via a shortcut key or a toolbar or menu item. Then the window focus shifts immediately back to the Macro Editor, regardless of whether that particular script is open in the macro editor or not. This is mildly annoying as it disrupts workflow (for instance if you want to press a second shortcut key immediately after the first, then the second key will get sent to the Macro editor rather than to KLayout proper. Of course I could just close the Macro Editor window, but I often need to be editing a macro and then intermittently doing other KLayout functions as part of the testing procedure etc. Or sometimes it's just more convenient to leave both Windows open (I understand this means all my scripts run slower, but most scripts are small and this isn't noticeable). So I'd suggest if there is any way to change it so Macro Editor window didn't take focus each time any script is run (but it can maintain focus if it already had focus) then that would be preferable.
Related to the previous one, there is a far bigger problem on Windows (I haven't tried it on Linux so can't comment on that). When you have Macro editor open and you open any other KLayout dialog (for instance, you have macro editor open, then you click to select a shape in the layout, and choose "move by" in the Edit menu) then it goes wack-o. The two windows (the main KLayout window and the Macro window) flicker really quickly like they are both trying to get focus and are rapidly flicking back and forth between the two. At any rate, both windows and the dialog box become unresponsive. If you try to click on either window during this period of confusion, windows takes over and tries to help - Windows greys out both windows and says "This program is unresponsive. Would you like to wait, kill it, or cancel this helpful dialog?" Sometimes it resolves itself if you wait but it usually takes 60 seconds of flickering, while other times it doesn't resolve within my patience limit and so I have to kill KLayout in Windows Task Manager.
In practice I get around this by just never doing any KLayout functions that require a dialog box, while I have Macro Editor open (so if I want to "move by" then I close Macro Editor, do the "move by", then re-open the macro editor) but it's mildly annoying. Again I assume that this is just due to how Windows chooses what window is in focus, and Windows may be having an argument with itself. I could be wrong there though - that is just an assumption.
I am frankly amazed that as far as I can tell, you wrote and maintain all this software single-handedly. I would be really interested to know your story and how or why Klayout came to be, perhaps you could share a short version here or on the About page..
There is no rush on the replies, I understand I've given quite a lot to chew on up there.