Loops like this aren’t unique to VBA-indeed, they’re a common feature in most programming languages, allowing a program or script to run continuously in a sequence with a start and end point. For instance, if you want a macro that repeats an action by a certain number of times, you can use a VBA For Loop.
VBA is a useful programming language for new data analysts to learn as it supercharges the functionality of Excel, making it easier to perform certain tasks automatically (and repeatedly) with custom-made macro scripts. Macros are automated scripts, typically written using Visual Basic for Applications (VBA), to help you perform certain actions in Excel, such as automate a button press or perform a calculation. This is just an alternative that doesn't clog up the menus with every little script you may use.If you’re looking to automate your Excel spreadsheets, macros are a good way to do so. It is true that instead of this you can just have a macro show up in any of the dropdown menus, and I do this for some of the main scripts. RBA::FileDialog::ask_open_file_name("Choose file", File.expand_path("C:\your_preferred_filepath"), "All files (*)") Not only does it get around the issue described here (which it seems only I have!) but scripts can run much faster.
LAYOUTEDITOR MACRO LOOPS CODE
Instead I have attached the following code to a toolbar button. In the meantime, if it helps anyone else: I usually don't run scripts from the macro editor.
But I'll try that in a week or two and let you know if I find anything. I have tried everything I can think of except a complete reinstall, which I am putting off until after an upcoming tapeout deadline in case one of my needed scripts breaks. (Currently I actually use an actual notepad app for this, because of this issue.) Disabling this toggle button would allow much faster running of intensive scripts at the cost of debugging mode. Basically in the latter case the Macro Editor is simply a notepad with "Save" and "Run" features. When disabled however, the running script doesn't stop for any breakpoints, doesn't return focus to the Macro Editor after a script is run, doesn't output to the console, etc. This prompts a suggestion: Perhaps in a future release, the Macro Editor would have a toggle button that enables/disables debugging mode. If you need more examples I'd be happy to try the other functions and report which ones exhibit the bug Perhaps by glancing at this list you can tell what is the common factor that defines one list or the other. It is clear it has issue on some functions but not on others. Any Qt dialog that you've coded in a Ruby scriptĪnyway, that's just a sampling.File > Layout statistics, if you don't have a current layout open (because in that case it says "No current view to show layout statistics for" and you click OK, and it doesn't have any issues.File > Import > Other file into current.The crash does not happen if you have Macro Editor open and do any of the following functions that open a dialog box: (this is not a complete list) The crash does happen if you have Macro Editor open and do any of the following functions: (this is not a complete list)
LAYOUTEDITOR MACRO LOOPS WINDOWS
You mentioned you were not aware of that bug because you use KL on Linux, so it must be a Windows thing.Īnyway in an effort to help you track down that bug I have tried a few things. A short time ago I posted about how on Win 7 with KL 0.23.3 I am observing problems - when the Macro Editor is open and you do some KLayout function that opens another dialog window (such as "Move By"), the second dialog window (eg "Move By" dialog) and the Macro Editor both flicker and become unresponsive, and eventually the program crashes.
0 kommentar(er)
