Generally: It is NOT a WinBuilder issue, because WinBuilder does not even know that shortcuts exist, and therefore does not work with them.
WinBuilder only executes code coming from scripts, which handles shortcuts.
For the nativeEx world (nativeEx_barebone, NaughtyPE, nativePE, LiveXP, ...) I wrote the package 'BuildModel' which handles shortcuts.
In my opinion ....
There exists an API interface, which gets as input more easier commands than BuildModel needs and wraps to
- nativeEx world
- Vista / Win7 world
- caused by the host OS, because it does not generate shortcuts in the 'currently known' way
- caused by the API because it does not generate the suited calls to BuildModel
- imaginary problems because the user assumes something, which cannot be done neither by the API nor by BuildModel
Restriction: On my systems German XP SP3, German Vista 64 bit, English Win7 RC1
For that I uploaded a special nativeEx minimized version having only one Test.Script app.
This script generates:
- a *.bat file
- a *.cmd file
- a *.scr file
All of them in the BuildModel call do not define any icon.
On my 3 systems all icons are displayed well, and the corresponding commands are executed correctly.
- Download the test project from the nativeEx server
- Unzip into any directrory (preferrable WITH spaces in the path)
- Start WinBuilder
- Define the path to your source CD and build
(Factory setting is 'Emulate in VirtualBox', if you do not have VirtualBox, you can choose between qEmu and VMWare)
- Test the PE
Download URL: http://nativeex.boot...ShortcutTest.7z