EXAMPLE:
start "Aibel AS. Iso2Ustn for MicroStation Connect Edition" /D %Appl_Root% /HIGH %app% -S%StartupFile% -WK%CurrentWorkSpace% -WW%currentWorkSet% %StartupCadFile%
I have to agree with Roald Tvedt, mvba isn't an ideal substitute for -s switch. The cons of mvba including, but not limited to:
- Non text base
- require external dependencies (com server installation etc.)
- need signing in High Security mode
- require mvba knowledge
And with the latest addition of the userpref option, we admins have to incorporate another check to ensure that userpref stay on. If I can get things done using a bunch of keyins, that would always be my 1st preference.
Tuan Le said:require external dependencies (com server installation etc.)
Which is part already part of the MicroStation installation so not really a relevant point.
Tuan Le said:need signing in High Security mode
Sucks to be a CONNECT user, I guess.
Tuan Le said:require mvba knowledge
Assuming startup script syntax is the same as standard key-ins, I would say this point is not really valid as you are only encapsulating standard key-in's in CadInputQueue.SendCommand "insert command here". Pretty straightforward for anyone to easily pick up compared to something like C++.
Tuan Le said:Non text base
For that we should be thankful. One of the things my Macro does, is check if the DGN file contains a sheet model, if it does, activate it and fit all to the view. Are you confident you can do the same with a Startup Script?
mwlong said: I was able to download a simple AutoRun.mvba
As a general point for the benefit of those who don't know already, it should be clarified that the name AutoRun is purely one of descriptive convenience and not a must-have for the Macro (my own version is named Open_Close_Design_File_Events.mvba). What is important is that it contains the relevant Module and Class code (as approximately outlined by Roald elsewhere in the thread).
Tuan Le said:And with the latest addition of the userpref option, we admins have to incorporate another check to ensure that userpref stay on.
Do you really? I've yet to hear a definitive reason why this setting is such a bad thing. Whilst I do the same role, I do find it amusing that such things are seen as a weakness in a Workspace and 'must be locked down at all costs'. After all, it's so easy for any user(with some basic knowledge) to bypass CAD Admin 'restrictions'. Predefined standards & settings are there to followed and used of course, but if users are not doing so then I would be inclined to find out why. If the effects of their actions are negative and warnings ignored, its really an issue to be escalated and dealt with by a company's management.
Or you could have just read the previous post where it was clearly written...
Barry Lothian said:I don't use CONNECT but have you considered looking in the CONNECT version capability.list file to see if there is a capability which can lock down that user preference setting?
Perhaps you should make a suggestion to Bentley that V8i users shouldn't be allow to comment on CONNECT threads, perhaps that'll be more to your liking, but in the meantime, feel free to continue with your passive-aggressive sarcasm, it sure does brighten up my morning.
the ask Inga post was posted before this option was available and maybe should be updated ?
it states the following: the -s command line switch which dumps the contents of a "startup file" into the MicroStation key-in window for immediate execution.
What I believe the new option is doing as I have stated before is, it is doing this AT startup rather than AFTER startup. You seem to keep skipping over this. Bentley must believe there is an issue with this differentiation or they would not have put it in the software.
There is nothing in the capability list that will lock this down.
Also, I do not want to lock this down, I simply would like this option in a place where it is not a user specific option (you may say that this is the same thing). I don't feel a user should have the ability to change a processing order.
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Barry Lothian said:Perhaps you should make a suggestion to Bentley that V8i users shouldn't be allow to comment on CONNECT threads
I appreciate you're just trying to contribute to a conversation Barry. I'm here voicing my concern specifically about the implementation of startup script in CE, and having my concern dismissed by you with your preference of VBA over startup script, even though I've said there are risks with using VBA in general and specifically in CE.
Tim Hickman said:What I believe the new option is doing as I have stated before is, it is doing this AT startup rather than AFTER startup. You seem to keep skipping over this. Bentley must believe there is an issue with this differentiation or they would not have put it in the software.
The -s switch was actually sort of working in CE prior to U16, if you open the directly into a dgn. Using below commandline as an example:
microstation.exe -s"Startup File Path" "DGN file path"
In V8i: "DGN file path" is optional, -s works regardless
In CE pre U16: "DGN file path" is required. If a file is manually selected to open in back page, script file is ignored.
I'm not skipping over anything, I'm merely saying that based on the only documented evidence on startup files (that I've seen), the content of such a startup file is only noticeable when a DGN is open and that the exampled key-ins can have no effect during the startup procedure. I've not seen anything that confirms the previous functionality of the -S switch is has now been changed, and that it now does something entirely different, and that the type of key-ins which can be put there, are also very different. You seem to believe that to be the case (and it may well be), but where is it confirmed? Where is the Bentley announcement in a Superceded/Deprecated Features or What's New etc... that confirms this?
If your theory is correct, you should be able rig up a simple test and see the result in a debug output.
I don't disagree that the discussed option being in User Preference is strange. To me, its very existence is even more strange.
However, I'm now done with this discussion and I'll leave it for those more relevantly affected to continue.