When I record a macro it successfully captures and can regurgitate, effectively, an angle readout precision setting.
But the working units setting, quite analogous, is completely ignored. the macro contains nothing.
it would seem there should be a step corresponding to
MbeSetAppVariable "DGNSET", "dgnSet.angleReadoutPrec", 9&
but there isn't. rather than guess, many times, what might be the name of
dgnSet.workingunitsReadoutPrec, .... ( 2 digits fewer than angle ..?!?!...)
can I find it documented somewhere?
F1 help doesnt know about it.
thanks
Jim
Draftsman Two said:MbeSetAppVariable
Presumably you're attempting to write a BASIC macro for MicroStation V8i?
First, switch to VBA! Why? Read these notes, and why VBA is better than BASIC.
Regards, Jon Summers LA Solutions
Jon thanks; my reason for using Basic is that there is a tool, 'create basic macro', which allows me to do that,
very quickly, with almost no special knowledge. And mostly, they work; but sometimes not. It took me a long
while to work out why it couldn't find files - no spaces allowed in names. I have a problem with PD not
remembering settings, eg tentative is middle mouse button, cursor is full width, dimension offset is
-.5, which I have to set every application start. My basic macro cannot set the tentative, It mostly can
attach the correct cell library, but sometimes not. I accept that I have to take time out to learn VBA.
Its just that that free time never arrives, and when it does, I need to relax, not do more uStn!
Draftsman Two said:there is a tool, 'create basic macro'
There is another tool record VBA macro.
Hi Jim,
you did not specify what product and version you use (please read and follow MicroStation Programming forum best practices as well as BE Communities best practices).
Draftsman Two said:my reason for using Basic
For lat at least 10 years there is no reason to use MicroStation BASIC. From first version of MicroStation V8 (2001!) it's recommended to use MicroStation VBA and from I guess V8 2004 Edition ii has been recommended to migrate BASIC code to MicroStation VBA. It means to use MicroStation BASIC in 2019 is always bad decision regardless reasons.
Draftsman Two said:It took me a long while to work out why
MicroStation VBA is better documented, there are bigger knowledge base (because for "pure VBA" issues you can use any discussion about VBA like Office / Word / Excel / etc.) and VBA Editor helps you with code.
Draftsman Two said:I have a problem with PD not remembering settings
They are not programming issues, but admin issues. Ask for a solution in Administration or MicroStation forums. When product installation or configuration is not correct or is even broken, to use code to fix it is bad approach. The configuration itself has to be fixed at first.
Draftsman Two said:Macro to set angle readout precision and working units readout precision
How to modify model working units have been discussed several times, e.g. here or recently here. Do not reinvent the wheel again.
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point