29 replies to this topic

[pscEx]

You can download the actual version of myOptions.Script from here.

---------------------------------------------------------------------------
Version 6 available.
Some changes needed for the WMManager script.

---------------------------------------------------------------------------
Version 5 available.
Added 'Verbose Log' and 'Debug Log'
Thanks Alexei!



---------------------------------------------------------------------------
Version 4 available.
Included suggestions by Alexei
'Select' status is saved and restored.
Optional the script generates a log file.
'CleansUp' itself. .exe is deleted after run.



---------------------------------------------------------------------------
Version 3 available:
Now also restore of scripts' options is optional



---------------------------------------------------------------------------
Version 2 available:
I added the choice to restore script.project and WinBuilder.ini data



----------------------------------------------------------------------------

Currently there are two issues which really do not make work with WinBuilder enjoyable:

- If you have in different projects the same Archive script linked and if the different projects have different user options ...
- If you do an download e.g from the sandbox or a newer version of a script ...

... then before running the project you first have to check and redefine your user options

I wrote a script using a Delphi program which does this automatically.

The current options are stored in myOptions.ini like this

[Scripts]
Count=21
[Script1]
Entries=1
FullPath=C:\Do ... script.project
Entry1=pCheckBox1=True
SourceDir=V:\BCD\cds\XPP_DE_SP2
TargetDir=%ProjectDir%\Target
ISOfile=%baseDir%\ISO\Standard.iso
[Script2]
Entries=1
FullPath=C:\Do ... BootfromRAM.Script
Entry1=pFileBox1=V:\BCD\cds\W2003_R2_DEU\I386
[Script3]
Entries=22
FullPath=C:\Do ... DisplayProperties.script
Entry1=pCheckBox1=True
Entry2=pCheckBox10=False
Entry3=pCheckBox11=False
Entry4=pCheckBox2=True
...

Peter

[edborg]

Wow!
This helps not to get crazy with the 'management of change'.
Thanks
edborg

[phox]

FullPath=C:\Dokumente und Einstellungen ... script.project

Could “Dokumente und Einstellungen” be
replaced with “Documents and Settings”?

[edborg]

Could “Dokumente und Einstellungen” be
replaced with “Documents and Settings”?

You're not supposed to use somebody else's 'MyOptions.ini'.
When you generate your own 'MyOptions.ini' (by running the script) you get your path.
edborg

[pscEx]

Could “Dokumente und Einstellungen” be
replaced with “Documents and Settings”?

Of course!
The program stores the actual project's paths.
You here see a sample made on my German system.

You can make a 'no-risk' try:
Create an empty test directory.
Unzip Basic_Latest into it.
Unzip Sandbox_Latest into it.
(Optionally you can replace WinBuilder.exe by the latest WinBuilder.exe beta)
Save myOptions.Script in the Archive\Tools folder and a link in Projects\Standard\Tools folder.

Let myOptions.Script save the options.
Change some options e.g.shortcuts.
Let myOptions.Script restore the options.
Check the result.

To be very sure, build the project 'before' and 'after' and compare.

Peter

[edborg]

I've used the script in my actual project.
It's really helpful when playing around with different versions of the same scripts!
edborg

[pscEx]

Version 2 is available!

See first post.

Peter

[pscEx]

Version 3 is available!

See first post.

Peter

[TheHive]

Thanks.

[Alexei]

Version 3 is available!

See first post.

Peter

Peter,
- Please don't forget to include "myOptions" in the upcoming sandbox!
- Probably it should cleanup after itself (I mean scriptData.exe )
- Selected= should be saved/restored (user option).
- What happens if script moved to another folder?
- Doesn't look good on my PC (see below).
- The merge must produce log, otherwise how would I know what failed or went wrong?
- The log should be available for immediate view by additional "vew log" button.
- Viewing the log should be done with "cmd /C start ...." (or something similar), so I would be able to look at the log while making changes in the scripts if automation failed
That's all for now I see a great potential here

Alexei

Attached Thumbnails

• 

[pscEx]

- Please don't forget to include "myOptions" in the upcoming sandbox!

I'll do so!

- Probably it should cleanup after itself smile.gif (I mean scriptData.exe )

Please explain more!

- Selected= should be saved/restored (user option).

Will be in version 004!

- What happens if script moved to another folder?

I do not know whether just 'nothing done' or 'program crash'. That's an item I have to look for. Thanks!

- Doesn't look good on my PC (see below).

I wrote an bug report about that.

- The merge must produce log, otherwise how would I know what failed or went wrong?
- The log should be available for immediate view by additional "vew log" button.
- Viewing the log should be done with "cmd /C start ...." (or something similar), so I would be able to look at the log while making changes in the scripts if automation failed smile.gif

I think on this for version 00?

That's all for now I see a great potential here

Thanks

Peter

[Alexei]

- Probably it should cleanup after itself smile.gif (I mean scriptData.exe )
Please explain more!

I meant FileDelete on %exename% after ShellExecute. Yes, delete each time after use

- What happens if script moved to another folder?
I do not know whether just 'nothing done' or 'program crash'.

Suggestion:
1. Same folder - just use it.
2. See if script file name is unique in project tree, YES - it's the match, NO - error.

- The merge must produce log....
I think on this for version 00?

Let's set priorities (1st - highest):
1. Make a log! Even if the program has bugs, user still can do his job looking at the log How would you like to deal with bug-reports without log attached? Without log I have to go over all scripts to see if they auto-fixed correctly
2. "Selected=" - major omission.
3. Locating matching script in other folder.
4. Asynch view of the log.
5. Erase %exename% file.

Alexei
PS
My programming life tought me two major lessons:
- Add comments to understand what you wrote and why
- Include debugging log before the first attempt to run the program

[pscEx]

Version 4 available!

See first post.

Peter

[Alexei]

Version 4 available!

See first post.

Peter

Nice progress
Is it possible to include in the log more details about the merge? I mean values and names.
Something like abc=123->345. So, if you see "zzz=123->true", that would point your attension
Such things may happen if developer redisigned the interface.

Alexei

[pscEx]

Nice progress
Is it possible to include in the log more details about the merge? I mean values and names.
Something like abc=123->345. So, if you see "zzz=123->true", that would point your attension
Such things may happen if developer redisigned the interface.

Alexei

You are arduous
Possible: Of course!
Will make: I'm thinking about!

Peter

[pscEx]

Version 5 available

See first post.

Peter

[edborg]

Version 5 available

See first post.

Peter

I must be stupid.
I was amongst the first ones to use your script, and it worked perfectly!
Now I'm no longer able to make it work, and don't know why.
I'm using version 5 (still reporting version 004), which freezes. When I kill it i get this log for the script:

Log generated by psc program 'myOptions' version 004
Date: 2006-nov-13 10:25:48
Command Line: -PG:\WinBuilder\Projects\Standar

with the attached Winbuilder log.
Any idea?
edborg

Attached Files

•  log.html   2.95KB   445 downloads

[pscEx]

I must be stupid.
I was amongst the first ones to use your script, and it worked perfectly!
Now I'm no longer able to make it work, and don't know why.
I'm using version 5 (still reporting version 004), which freezes. When I kill it i get this log for the script:

with the attached Winbuilder log.
Any idea?
edborg

Currently no idea
Please delete myOptions.ini and myOptions*.log in the %ProjectDir% and try again.

If that does not work, please zip your Winbuilder folder (W/O Tools ISO, Source(S) and Target(s) and PM me.

Peter

BTW I changed the 004 in the log output to 005. Thanks!

[edborg]

Currently no idea
Please delete myOptions.ini and myOptions*.log in the %ProjectDir% and try again.

I had already tried that, to no avail!

However, in the meantime I've tested the new WB052 package (not only the program) from Nuno, and your script works fine there.
So it's certainly something due to my Winbuilder folder, as you rightly suggest, not to your script.
I'll have a better look to it soon and either let you know the outcome or send it to you for further help.
Thanks for now.
edborg

[pscEx]

So it's certainly something due to my Winbuilder folder, as you rightly suggest, not to your script.

Inspite of that: Please send the folder which did not work. I have to find out what caused myOptions to hang, and find a way to catch that issue.

Peter

[pscEx]

Version 6 is available
It contains some changes I added for the WBManager script.

Peter

[edborg]

Please send the folder which did not work. I have to find out what caused myOptions to hang, and find a way to catch that issue.
Peter

When I read your replay I had already rebuilt my Winbuilder folder and recreated ini files and the like to make it work.
It now works, but I don't know exactly what caused the hang, neither have I a non-working folder to send you to further check, sorry.
In any case, as said, the problem wasn't with your script.

Version 6 is available
It contains some changes I added for the WBManager script.
Peter

Version 6 works also, but I get an error with WBManager script.
edborg

Attached Thumbnails

• 

[pscEx]

Version 6 works also, but I get an error with WBManager script.

When testing later, I got it, too.
New versions of WBManager and myOptions are uploaded under the old version number.

Sorry

Peter

[Brito]

Wasn't this an error due to RTL70.BPL?

http://forums.devshe...hine-92352.html

[edborg]

Or isn't this due to the fact that rtl70.bpl is really missing?
I don't have it in my WinXP SP2 system, and if I add it to the host's system32 everything works.
Perhaps such file should be encoded and extracted from the script, to work with all hosts.
edborg