02013: "gtime" parameter is hex

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
02013	Debugger	Feature	Always	Jul 15, 2008, 20:04	Feb 6, 2012, 20:04

Tester	Firewave	View Status	Public	Platform	MAME (Self-compiled)
Assigned To		Resolution	Fixed	OS
Status [?]	Resolved			Driver
Version	0.126	Fixed in Version		Build	Debug
		Fixed in Git Commit		Github Pull Request #

Summary	02013: "gtime" parameter is hex
Description	I had trouble in the past using the "gtime" command in the debugger. It would always run more than the amount of milliseconds I specified. I finally dug into it and before I figured it out myself, Cowering pointed out, that all values in the MAME debugger are hex. This is quite confusing as the help of the debugger states, that you have to pass the milliseconds as parameter and I wouldn't assume those to be in hex. There might be other commands, that are affect by this like "step" or "over".
Steps To Reproduce
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems

Attached Files

No.01642 Firewave Senior Tester Jul 15, 2008, 20:13	The output when "gtime" reached it's stoptime is also confusing as it's printed with the "%.1g" format, which will pretty fast go into the "1e+001" (that's the value for 12 seconds wait time) format, which is pretty useless. It should print the value in either milliseconds or seconds with milliseconds.
No.01646 Tafoid Administrator Jul 16, 2008, 04:16	This might be more a feature request rather than a bug .. since all the commands are known to work with hex input.
No.01651 Robbbert Senior Tester Jul 16, 2008, 11:52	Step and Over count in hex - which is what I always expected. I'd think this is a feature request, maybe along the lines of adding an inifile setting to determine if you prefer to work in hex or decimal. As it stands, the debugger works as designed as far as I can see.
No.01668 Firewave Senior Tester Jul 17, 2008, 21:53	OK, I wasn't aware of this. I never used the debugger and recently looked into it again to do some scripting for regression tests with it. I still think the message when "gtime" finishes should be changed to a more proper format.
No.08152 Tafoid Administrator Feb 6, 2012, 20:04	This seems fine. gtime from debugger only accepts millisecond increments in the form of: "gtime #100" = 100 milliseconds. "gtime 100" = 256 milliseconds.