Originally posted by Ulfius@May 3 2007, 05:50 I have one machine that everything's working fine on (that I've tested) and another that's giving me an "Error In Screen Pos Routine" as soon as I start the program. I'm using the 4347 global file and 1.1.2
Ahh ok I found it, 1.1.3 is coming soon and will address that problem.
[img]text2schild.php?smilienummer=1&text=1.1.3 Is Now Available' border='0' alt='1.1.3 Is Now Available' />
More fixes including hopefully a fix to "Error In Screen Pos Routine" problem.
Added version numbering to the memory address table, now shows ver and path of mem table when you hover the mouse pointer over the word ver at the left of the main box and it also tells you when you do a reset in the MOS screen.
Don't forget to load the new memory table more addresses now added,
still waiting before I do HP stuff and the ore drops tho.
Changed the keyboard close buttons, now ctrl+shift+1 to ctrl+shift+9 was too easy to trigger by accident before.
TY all for the karma, I'm glad your liking the new features.
I get this error when opening and everytime i try to move the program from the top left hand corner of the screen. Which is where its resetting position to.
---------------------------
CO2m8
---------------------------
Error In Screen Pos Routine, resetting positions to 0
---------------------------
OK
---------------------------
Originally posted by Botter2daMax@May 4 2007, 17:55 I get this error when opening and everytime i try to move the program from the top left hand corner of the screen. Which is where its resetting position to.
---------------------------
CO2m8
---------------------------
Error In Screen Pos Routine, resetting positions to 0
---------------------------
OK
---------------------------
Heres a pre-release of 1.1.4, can you test it and let me know if that fixes it.
Stranger and stranger, I can't replicate it here tried different operating systems and configurations.
Yeah it is most likely something to do with the new sticky dragging,
but what, scratches head
Heres another diag version, let me know what it reports.
Originally posted by Ulfius@May 5 2007, 03:01 This gives me "Error 713 at loc.4" and "Error 713 at loc.6"
Thanks for the feedback, this is a weird one not even the error number makes sense, some sort of glitch with sub-classing in some systems.
Will make another test version, lets see if I'm on the right track for a fix.