VladimirII
New Member
Presets can be loaded by 'overwriting' all actual settings or by 'adding' the preset information to the already done settings.
In the Post-Setup screen a strange behaviour can be observed.
When already some things are added to the post-setup and a preset is attached that has 'Item' entrys with 'Index' 1, 2 and so forth. All Item entrys with an index number that is already used in the actual configuration is skipped instead of added as someone would expect.
Merge post-setup configurations from different Image-Projects get complicate through that.
I also see auto-saved settings that add post-setup entrys have higher 'Item' numbers than 1. I guess to prevent this skipping behaviour when recreating from scratch?
Instead of just looking for the 'Index' number a comparison of the 'Path' is better.
The way how it compares and adds could be different for every 'Item trype'.
Suggestion:
1) Every 'Command' Item type is always added.
- every user has to check it´s command entrys and can after adding easily delete duplicates
- Most commands are just doing the same without crashing what they are there for when executed multiple times.
2) Also passive 'File' item types can be always added.
- either only the path was changed if not identical or it doesn´t exist anymore
- an added file that is not executed only occupies space if not needed
- but oversee that a needed file was not added can make the Image useless. At least for USB-Images easy to fix afterwards
3) For Installer 'File' items, the exe/bat-filename should be compared, if identical the 'Params'.
- Either the user is asked if different parameters should be added to the actual parameters, the actual parameters replaced or a window appears with both entrys to choose one of them and/or directly edit the 'Params' that will be added to the active project.
As said, merge different Post-Setup Presets is already in some way a lot of work.
The 'Placeholder' makes it more difficult. The description doest´t give me the use of it.
One Feature-suggestion.
For example the nvidia-installer. The downloadable exe is an self-extractor that can´t start a silent install.
For a silent install the extracted files have to be used which includes folders. But folders can only be added by copying them manually into the $OEM$ folder afterwards.
An option to add folders would be nice.
In the Post-Setup screen a strange behaviour can be observed.
When already some things are added to the post-setup and a preset is attached that has 'Item' entrys with 'Index' 1, 2 and so forth. All Item entrys with an index number that is already used in the actual configuration is skipped instead of added as someone would expect.
Merge post-setup configurations from different Image-Projects get complicate through that.
I also see auto-saved settings that add post-setup entrys have higher 'Item' numbers than 1. I guess to prevent this skipping behaviour when recreating from scratch?
Instead of just looking for the 'Index' number a comparison of the 'Path' is better.
The way how it compares and adds could be different for every 'Item trype'.
Suggestion:
1) Every 'Command' Item type is always added.
- every user has to check it´s command entrys and can after adding easily delete duplicates
- Most commands are just doing the same without crashing what they are there for when executed multiple times.
2) Also passive 'File' item types can be always added.
- either only the path was changed if not identical or it doesn´t exist anymore
- an added file that is not executed only occupies space if not needed
- but oversee that a needed file was not added can make the Image useless. At least for USB-Images easy to fix afterwards
3) For Installer 'File' items, the exe/bat-filename should be compared, if identical the 'Params'.
- Either the user is asked if different parameters should be added to the actual parameters, the actual parameters replaced or a window appears with both entrys to choose one of them and/or directly edit the 'Params' that will be added to the active project.
As said, merge different Post-Setup Presets is already in some way a lot of work.
The 'Placeholder' makes it more difficult. The description doest´t give me the use of it.
One Feature-suggestion.
For example the nvidia-installer. The downloadable exe is an self-extractor that can´t start a silent install.
For a silent install the extracted files have to be used which includes folders. But folders can only be added by copying them manually into the $OEM$ folder afterwards.
An option to add folders would be nice.