My scripts do not work when using MicroStation, but they work when using every other software and this is not an issue with the way the script is written. I think being able to use scripts from AutoHotkey will make my workflow more efficient as it does when using other software.
For example, I have a script that i use for inputting date and time when typing "]dt". When I make a pdf from MicroStation, I cannot use this script when the file explorer window opens, yet when I open File explorer myself, it works. Also the script doesnt work in text fields either. So I think MicroStation blocks it. Is there a way to turn off the blocking?
MicroStation has its own set of defined key-ins, which it recognizes - I would not expect it to know the key-ins from another program. I do not think MicroStation is blocking anything - it just does not know what you are typing. AutoHotKey shortcuts are picked up by Windows (I believe) not MicroStation.
MicroStation also has special text substitutions and variables that can be used to create custom date and time formats which are exposed via pen tables and they can be automatically applied to any session or by prot driver.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration Maryland DOT - State Highway Administration User Communities Page
Thank you for your reply. I'll ask AutoHotkey to see what's going on. The program is used for many different applications such as playing pc games which has "key-ins" defined for the game. Maybe the problem is on the AutoHotkey side.
Thank you! I need to learn more about MicroStation's text substitutions and also macros. I wonder how easy the macros are to create
You can record VBA macros and then edit them in the VBA IDE. It is somewhat different than Office VBA as it has the capability of being interactive. Or you can create macros that require a selection set and then operate upon the selection set. These are also stored in an external file (*.mvba) as opposed to being stored in the DGN file. One mbva file can contain multiple modules and each module can contain multiple procedures.
There are also things called Action Strings. These are designed to be put in a menu or function key. Search the MicroStation help, not the GEOPAK help, for Action Strings and it will show you examples.
Finally, there are scripts - which are simple a text file with key in commands, one per line. These can include an action string if not too elaborate. There are activated by entering @"filename" at the key in command line once in a session but can be added to a special shortcut that runs them when launched. I always keep the paths short with no spaces so it was easy to type them in.