2024-04-16 22:30 CEST
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0005271WHDLoad[All Projects] Generalpublic2021-06-28 23:562022-01-15 23:13
ReporterPaul Head 
Assigned ToWeplProject InfoHD-Installer for OS-Killer
http://whdload.de/		 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionno change required 
Product Version18.7beta 
Target VersionFixed in Version 
Summary0005271: Command line interpretation of Config options
DescriptionPlease refer to page 12, post 234 on this thread on EAB

https://eab.abime.net/showthread.php?p=1493038#post1493038

jmprice_314159
"Hello, I'm using TinyLauncher and enabled tooltypes. However, when running a game, WHDLoad doesn't show all the options in the splashscreen. For example, r-type has 2 available cheats, and both are shown when launching the game outside of TinyLaucher by double clicking the game icon. When launching r-type in TinyLauncher, only the first cheat is shown in the WHDLoad splashscreen. Any idea why?"

My reply:
"What's happening is that the ; on the Config entry in the tooltypes of the game icon comments out the remainder of the argument for that line (from an AmigaDOS perspective), so the second button C2:B:Custom2 never gets displayed. This is not a TinyLauncher fault, but perhaps an over site of WHDLoad. I shall report the issue on the WHDLoad Mantis."

---Snip---

Am I missing something here? If so, how do I make those two buttons appear from the command line? Only one button appears because after the ; the remaining button(s) are ignored (quite rightly by the CLI).
TagsNo tags attached.
MachineUAE
CPU68020
CPUSpeed50
ChipSetAGA
GFXCardNone
ChipMem2 MB
FastMem0 MB
WorkbenchOS 3.0
KickROM39 - Kick 3.0
KickSoftNone
WHDLoad18.7beta
Attached Files

-Relationships
+Relationships

-Notes

note ~0010477

Wepl (manager)

2021-06-30 11:30

 TinyLauncher has to put the config (better all) argument into "" so that the shell doesn't interpret the ;
Parsing ToolTypes and CLI arguments are different and has to be considered by TinyLauncher.
Also numerical values can be used in hex e.g. $22 which is not possible in the CLI!

note ~0010478

Paul Head (reporter)

2021-06-30 12:32

 Apologies, I'm sure I fiddled with putting "" everywhere on it the other day but obviously not as indeed, I've got it working with the following:

whdload r-type.slave config="c1:b:Custom1;c2:b:Custom2"

So what you're saying is that those games that have for example $22 hex in their tooltypes on the Config line would fail anyway when run from the CLI, and so we'd be better off ignoring any lines of the tooltypes with Config in? If so, why are these options (Config) available in WHDLoad via the CLI?
Do you know if it works if the $ is changed via .DOLLAR in a command file/script? Is that a work around for the $xx? Or is it easier to just ignore the Config line...because it's not really important is it?

note ~0010480

Wepl (manager)

2021-06-30 15:10

 Numerical values can be used with all options of the type 'numerical', see table in http://whdload.de/docs/en/opt.html
These values can specified only decimal in the CLI because parsed by dos.ReadArgs. As ToolTypes also hex numbers can be used like $7c. It is parsed by WHDLoad itself.
The Config option is a string, so this doesn't applies here.
If TinyLauncher likes to use the ToolTypes as CLI arguments it had to convert:
 numericals -> make them decimal if hex is used, quitkey=$59 -> quitkey=89
 strings -> put "" around, config=c1:b:#1;c2:b:#2 -> config="c1:b:#1;c2:b:#2"

note ~0010481

Paul Head (reporter)

2021-06-30 16:44

 Thanks for prompt reply. That's good then that all that a Config line needs is quotes inserting, that's easy-peasy. At first, I thought you meant that there could be hex values in the Config line! I'm glad there's not.

Are you indirectly saying that a .dollar to change $ to something else in a command file wouldn't work in order to get WHDLoad to read in hex values from the tooltypes? I might try it myself...unless WHDLoad will always expect decimal if not run from Workbench tooltypes? Reason I ask is that I have my own AmigaDOS script that reads these tooltypes and creates its own WHDLoad command line, and converting them from hex to dec sounds to be a lot more difficult for me. In AMOS it would be obviously more straight forward.

Michael (the TinyLauncher author) hasn't got back to me yet, unfortunately.

note ~0010483

Wepl (manager)

2021-07-01 09:14

 Yes, WHDLoad will always expect decimal if not run from Workbench tooltypes. Dos.ReadArgs only supports decimal.

note ~0010503

Paul Head (reporter)

2021-07-08 11:42

 Great. If you don't mind me asking, are there only these four arguments that may be hex in the tooltypes?

QuitKey
RestartKey
FreezeKey
DebugKey

note ~0010508

Wepl (manager)

2021-07-08 23:21

 It is possible for all numerical options:
ConfigDelay
Custom1
Custom2
Custom3
Custom4
Custom5
DebugKey
FreezeKey
LogBuffer
PreloadSize
QuitKey
ReadDelay
RestartKey
SplashDelay
TimeOut
WriteDelay
I don't know if all of them are used with hex but it is possible.

note ~0010512

Paul Head (reporter)

2021-07-12 21:30

 That's fantastic information. Cheers!!
+Notes

-Issue History
Date Modified Username Field Change
2021-06-28 23:56 Paul Head New Issue
2021-06-30 11:26 Wepl Assigned To => Wepl
2021-06-30 11:26 Wepl Status new => assigned
2021-06-30 11:30 Wepl Note Added: 0010477
2021-06-30 11:31 Wepl Status assigned => resolved
2021-06-30 11:31 Wepl Resolution open => no change required
2021-06-30 12:32 Paul Head Note Added: 0010478
2021-06-30 15:10 Wepl Note Added: 0010480
2021-06-30 16:44 Paul Head Note Added: 0010481
2021-07-01 09:14 Wepl Note Added: 0010483
2021-07-08 11:42 Paul Head Note Added: 0010503
2021-07-08 23:21 Wepl Note Added: 0010508
2021-07-12 21:30 Paul Head Note Added: 0010512
2022-01-15 23:13 Wepl Status resolved => closed
+Issue History