question about the Variable Value by the compilerVariable:
is it correct that the max length is 259 by this field ?
the field - Value List have a max length from 1039.
Printable View
question about the Variable Value by the compilerVariable:
is it correct that the max length is 259 by this field ?
the field - Value List have a max length from 1039.
Hello,
I fear I do not understand.
The command line switches are documented in the F1 help or PDF manual. But the command line can't be used to "control" the functionality of your SKU feature. The command line compiler is there to automate the compilation process (no user intervention).
Friedrich
Hello,
Yes, this is correct. The limit of a single entry is 259 bytes and the limit of a SKU list is 1,039 bytes.
Friedrich
BTW, I am not sure yet but I "think" (we have to check this) that we can increase the limit of the "list" in the SKU (e.g. from 1,024 bytes to 5,196 bytes).
Friedrich
I also do not understand!
I feel it exactly automatism - I do not want user intervention - that is to serve only as a check! and if I use this function, the variable is read but do not seem right.
Am I the function: "Do not prompt when compiling from Command Line" activate ? So I do not see the error?
The same with "the increase of the "list" in the SKU (e.g. from 1,024 bytes to 5,196 bytes)."
Good - then I can grab three variables dialogs in one dialogs - but what good is that if the default value is limited to 259 bytes - nothing!
sorry - but you have not thought of this function to an end.
Thanks for your feedback.
With regard to your comment "but you have not thought of this function to an end". The SKU and the command line capability to pass compiler variables are completely different animals! The SKU can not (and should not) "process" command line arguments. We have added a not to the documentation to make clear that the SKU is not a command line processor.
Friedrich
I do not understand.
They have a great feature - which actually leaves something to be desired - but the existing fault - I call this a mistake - and thus to change its user to listen to their programs - they do not want.
Rather just write the documentation and change consequently the functioning dead.
Hello,
Of course, I see where you are coming from. But by design, the SKU can't process command line arguments. This is an oversight in the documentation on our part for which I apologize.
Let me check this again with you. As I understand it, you would like to define a compiler variable (e.g. _AUSWAHLRN_) with the SKU option enabled. Then you would like to pass the "Value List" (e.g. "|Standard - Deutsch/English|Fränkische|REHAU") via the command line to the compiler so the SKU Wizard displays:
Standard - Deutsch/English
Fränkische
REHAU
Is my assumption correct?
Friedrich
Thank You ! :)
ok
Here's an example:
SKU _Auswahl_ List dialog:
Test1
Test2
Test3
Test4
Test5
Test6
Test7
....
long list ;)
ok - this SKU dialogue has no entry in the Variable Value.
If we want to create a setup - the query comes up and the user selects eg Test1 and from Test59 -everything else happens in the script.
Now it is also true that there are certain setup is ALWAYS the Test1 Test3 + + Test44 .... included!
Now it makes sense to call the setup via command line so that they are always initialized!
The user can also see that everything was dialed correctly.
Another possibility is toat the end of the creation of a setup user settings via the function:
# Edit ini: C: \ setup.ini _Auswahl_ => INI Item = "[_Auswahl_]"
to save.
Why?
After the client setup has been tested - can this be with all setting on the command line again loaded and created -if an error was found and thus have again changed files!
Hello,
Okay. We have enhanced the SKU Wizard. For 'Combo entry with list of values (single-select)' and 'List entry with list of values (multi-select)' SKU items, it should be possible now to pass a list of items separated by a vertical bar ("|") via the command line.
See attached screenshot.
This enhancement will be available in V7.7
Friedrich