Just a small update here. It seems that when I use the Shortcut Creator and the AutoStart Script, the Script is not added at the end of the shortcut. An example: for "C:\Program Files (x86)\ ARC\ARC.exe" "C:\My Documents\MyFile.ezb" "InitScript", "InitScript" is missing. When I add it manually after shortcut creation, everything is fine.

By the way, I have notice that the script needed to be in is own window in order to be executed at startup. It don't work when the script is inside a Script Manager windows (it is the same when trying to load a script at connection in the "Connection Established Cmd").

Is there a way to use the scripts inside the Script Manager at startup or at connection?

Ok, so problem solved for the script start at connection, with ControlCommand("Script Manager", ScriptStart, "MyScript")... should have been more careful to the tutorial of Script Manager blush.

However this solution don't seem to work inside shortcuts, for script start at startup... is there a way?

As you follow through each step of the shortcut creator, you will see that only EZ-Script controls are displayed in the drop-down. EZ-Script Manager controls are not displayed in the drop-down of the shortcut creator.

@DJ. Thanks for the answer.

That's right, only EZ-Script controls are displayed in the drop-down... It explains why scripts in EZ-Script Manager dont load at startup

However, I have tested again with an EZ-Script control. When i select it in the drop-down from the shortcut creator, it is not taken account. It is not loaded at start and it don't appear in the "target" property of the shortcut in Windows... I have to add it manually. Maybe it is because I am using Windows 8? I don't know... But it is no big deal, it works this way and it don't prevent my Wall-E from growing...

Thanks again.

Check the latest release - i made a change for Windows 8. Seems to be a few issues with some of the native interop functionality between 7 and 8...

Downloaded. Tested... and validated! Problem solved. @DJ. I must admit I still don't understand how you manage to understand and solve so quickly every single tiny problem meet by users. This community is really lucky! Thanks.

:) Thanks dude! I'm a robot, didn't you know?

I really like the EZ-Load shortcut creator. It works as described but I'm not sure how to suppress the Assembly Instructions & servo Fine Tuning dialogs that need to be answered.

I'm not sure what I'm missing here as I'd like to implement some of the scenarios as described in this snip

Disable those features in the preferences menu of ARC. Preferences is a menu interface for ARC software to enable and disable options for your preferred operation. Lots of options in there!

Don't forget to hover on the question marks in the preferences menu for additional information of each option.

Excellent! Thanks Frank

Anytime

Since we're on the topic of preferences, I thought I'd take this opportunity to put in a request. Would it be reasonably feasible to put in a preference option for the scripts editor such that the automatic lower-casing of keywords could be inhibited? I prefer to have them as mixed case and would like to see them stay that way. I do that now by having the Start In part of the shortcut to a given project file set to a directory other than the default ARC directory. Problem is I also lose all color coding as well when I do that.

And ... since I've gone this far, I wonder if it would be possible to change the editor feature in which matching sets of parentheses are highlighted? Currently they are highlighted by changing the background color of the parenthesis character. This can be difficult to distinguish when highlighting the characters between the set of parentheses for a copy and paste operation. It always looks like the parentheses are being included in the copy. So, I was wondering if the highlighting could be modified to show a change of color instead, with the background remaining the same? I have been working with Maxscript lately and that is how they do it. I find it easier to use. In addition they use red to indicate that a given parenthesis is not yet matched by it's opposite, which is also handy.

Just a couple of suggestions. Certainly nothing dire or critical to usage. For all I know I may be the only user this anal about these points. But I figure no harm in asking.