For fiddlers, like me, the old record function to vb seemed to store a lot more information that the new record macro function does. Is there any way to record to vba like we did in V8i?
Hi Bear,
at first, please be aware this is not MicroStation related group, but common development one. So I recommend to move the post (using More > Move) to MicroStation Programming forum. Also, as recommended by best practices, always specify your product and version exactly (even when your question is quite common).
Bear said:the old record function to vb seemed to store a lot more information that the new record macro function does.
Yes, because in V8 the recorder creates VBA code, whereas in CE, the recorder use simplified script language. It's described in MicroStation help.
There is also explained, how to promote MicroStation macro (.mbr) to standard MicroStation VBA code (.mvba).
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Move as requested, didn't start there as I'm actually using OBD.
I've seen the promote option, but the reality is the simplified scripting means we lose a LOT of good information that we used to capture using the record function. Great shame.
Hi,
in CONNECT Edition the default output format is Bentley Macro Recorder (.BMR), but this does not mean a loss of information, the promoted VBA still provides the same level of information like it did in V8i.And BMR is just the default output format. With stopping a recording a dialog box opens to allow the user to provide a name to save the recordings. Here also VBA can directly be selected. The dialog box can be extended (small triangle) and allows to select VBA like here displayed, please see the screenshot below:
Best regards,
Artur
I have tried that Artur, I'm just surprised on how little information is captured compared to V8i. I'm guessing that is in part to the ribbon interface, but the few I have tried it on capture very little usable information.
Bear said:I'm just surprised on how little information is captured compared to V8i. I'm guessing that is in part to the ribbon interface
honestly, I am confused: You told that in CE less information is recorded (which I have not seen yet), but at the same time you mentioned ribbon, that did not exist in V8i, so no comparison more/less information can be done.
I recommend to split the discussion (when you will see it as valuable) to two topics:
Without the mentioned step, this discussion is finished, because CE VBA recorder works in the same way as did in V8i, so on the current general discussion level, not too much more can be told.
Bear said:I'm just surprised on how little information is captured compared to V8i.
Although as Jan provides fair points Ribbon vs Pulldown Menu design changes; where the former is a newer interface and functionality and new surface area of consideration for recording; maybe the best thing to focus on and help you with is - what are you trying to record or accomplish?
Knowing this given it may not be one of many items that may not be recorded (or recordable - there is a difference) at least we can focus on helping resolve the problem/challenge at hand more quickly than the topic of recording w/less information and still not knowing the what component to test/assist with.
Please let us know and we'll be glad to help make progress on that/those item(s).
HTH,Bob
No need to split Jan, my comments were only in comparison and trying to work out if this is WAD (ie. a function of the ribbon interface), or an issue with the way I have been recording. From what I am gathering, this is WAD, which is a shame.
Bob, I've always found it handy to find out how to set some fields is dialogs where it wasn't obvious via a keyin. One I have been looking at in Connect is to be able to set a members size in the 'place beam' or 'place column' tool either via vb or a keyin. First time I've used the record function and was just a little surprised as to how little or the process was passed through.
I have started a discussion in the group regarding one of them, no response as yet. Might be better off logging a SR.
Thanks,
Bear said: and trying to work out if this is WAD
unfortunately no particular test case has been provided and discussed so far, so it's not clear what "WAD" behavior you mean.
Bear said:ie. a function of the ribbon interface
Ribbon is nothing else than "a messenger", that when an icon is clicked, a configured command / tool is invoked. The most of remaining ribbon functionality is about e.g. when particular icon should be displayed, collapsed etc.
Bear said:I've always found it handy to find out how to set some fields is dialogs where it wasn't obvious via a keyin.
Yes, that's right approach, even when the first step should always be to check whether "set item toolsettings" key-in is available or not. When it's not (because not supported by a particular tool or something outside Tool Settings dialog should be set), to try to record VBA is the best way.
Bear said:One I have been looking at in Connect is to be able to set a members size in the 'place beam' or 'place column' tool either via vb or a keyin.
If the tool can be set using key-in and what is recorded by VBA is solely responsibility of the tool itself (and consequently, of the programmer who implemented the tool). So when the following options are not available:
it's not the question of VBA recorder, but wrong design or implementation of the tool. And in my opinion there is zero link to ribbon itself.
Bear said: First time I've used the record function and was just a little surprised as to how little or the process was passed through.
I am not familiar with OBD tools, so I am not sure how they are implemented. The most of MicroStation tools (but exceptions still exist) support both "set item toolsettings" key-in and can be recorded by VBA recorder. Probably OBD does it in more close manner :-(
Bear said:I have started a discussion in the group regarding one of them, no response as yet. Might be better off logging a SR.
Can you provide a link to this discussion, to share the context?
I agree SR can be the way, because it's probably OBD feature.
Personally, my (very limited) experience with OBD customization and programming is very bad: It's the only from "open" product that has no own programming forum (even when asked many times) and it seems to be developed in a way not very open for customization and extensions.
'my (very limited) experience with OBD customization and programming is very bad: It's the only from "open" product that has no own programming forum (even when asked many times) and it seems to be developed in a way not very open for customization and extensions.'
Agreed there and the latest edition makes customisation extremely hard.
'Can you provide a link to this discussion, to share the context?'
communities.bentley.com/.../obd-u7---keyin-to-load-member