I read at least one other post from someone who described this (without a response), so I thought I'd report it again and see if anyone can confirm/address it.
I need to place a stamp at a variable location (putting up a three-digit build number on the Startup Screen, which is turning out to be a MONSTROUSLY difficult task). In the stamp event box, you can enter X and Y coordinates for the stamp's placement. However, it only takes numerical values; any non-numeric value (like &&gb;_cursor_x) is turned to a 0 when "+" is clicked.
I know this is possible because the score display events in the Cosmic Memory source have variables in these boxes, but again, if you try to edit them, they turn to zeros.
In the end, the only way I was able to do this was through a very dangerous hack: manually edit the binary .cet file with a hex editor, overwriting dummy text in the cursor locations with equal-length variable name strings. To be specific, changing "1.234568+e11" to "&&gb;_cursorx" (had to rename the global to get it down to 12 characters, which is the longest a floating-point value like the one above can be). This is a wicked hack, extremely dangerous, and likely to crash the system if you place one byte out of place. Don't do it.
What I'm wondering is whether this is a known bug, or whether there's an undocumented method to force a non-numeric value to be accepted in numeric fields, or to allow a global variable to be specified. I tried every trick I could think of.
If it is a bug, is there time to squeeze it into the 1.0.1 patch? I can see I'm going to have to do a LOT with globals, and it would be nice to have this all working.
System: OSX 10.1.5, full registered version.
Thanks for any tips.
------------------