1 reply to this topic

[pscEx]

There was sometimes the issue that in the PE some application icons where missing. They appeared after the first double click onto the shown standard icon.

This is fixed now with buildModel.Script Version 012

For the normal user: Just copy the script into your project and try.

If you have a drive with the %PEDrive% letter (usually X:) in your host system, it may still not work for all cases. This cannot be fixed by buildModel.Script. In this case the only way is to rename the drive or choose a different %PEDrive%.

For those who are interested about theory:

When the shortcut is created and inserted into ModelRAM, the link adress really has to exist in order to catch the icon.
This usually is the case with %WinDir%\app.exe and similar. Sometimes it is the case with %\ProgramFiles%\MyProg\Myprog.exe. Sometimes means: If the program is installed and %ProgramFiles% is identical for your host and the WinBuilder target (same languages).
It is really not the case if you use %PEDrive% for the shortcut.

To fix this issue:
I map (using the 'subst' command) %Target% temporarily to %PEDrive% and resolve the variables %SystemRoot%, %SystemDrive% and %WinDir% to use %PEDrive%.

Peter

[pscEx]

The solution I found before seems not to be the best one.

Mainly MedEvil did send me a lot of PMs to explain some issues. Thanks to him
@MedEvil: Immer noch 'Alter Nörgler': Vielen Dank für deine Hartnäckigkeit und deine gut fundamentierten Untersuchungen! Mach weiter so!

I added a different procedure to the shortcut generating module.
The new scripts can use %SystemDrive% in addition to %PEDrive%.

The changes are a trial. In my system they are working well.
To test, go to nativeEX_barebone WEB server and download buildModel and as samples ob1 and PENetwork.

I'm waiting for your response!

Pewter