TGB Mac 1.1.1 fullscreen / cursor / menu bug
by Don Schaper · in Torque Game Builder · 09/04/2006 (1:26 pm) · 7 replies
On a brand new install of TGB 1.1.1 (Mac), on a PPC Mac mini running OS X 10.4.7, I'm getting the oddest bug.
If you change to fullscreen mode (at any resolution); TGB's editors menus cease to function. If you click on a menu, the cursor freezes for a moment; and the menu itself does not appear. If you move the cursor away, an image of the cursor remains on top of the menu you clicked on; while the 'real' cursor moves around the screen. If you click anywhere, the 'ghost' cursor image disappears.
At one point, I was getting the following console error message (i have no idea what it means)::
-- row mod changed: old state: 0x0 new state: 0x100 changes: 0x100
[As I was trying various things, to get the darn thing to work right; I actually had my Mac crash on me. It crashed so hard that it didn't even show a kernel panic - it simply shut itself off. I've only encountered a kernel panic a couple of times. I've never had the system simply die!]
[Pulldown menus, disclosure arrows, particle editor graph stuff, etc. all work just fine in fullscreen mode.]
Running TGB in windowed mode works okay (once you've manually edited the prefs to disable fullscreen mode).
Does anybody have any ideas on what's going on here?
If you change to fullscreen mode (at any resolution); TGB's editors menus cease to function. If you click on a menu, the cursor freezes for a moment; and the menu itself does not appear. If you move the cursor away, an image of the cursor remains on top of the menu you clicked on; while the 'real' cursor moves around the screen. If you click anywhere, the 'ghost' cursor image disappears.
At one point, I was getting the following console error message (i have no idea what it means)::
-- row mod changed: old state: 0x0 new state: 0x100 changes: 0x100
[As I was trying various things, to get the darn thing to work right; I actually had my Mac crash on me. It crashed so hard that it didn't even show a kernel panic - it simply shut itself off. I've only encountered a kernel panic a couple of times. I've never had the system simply die!]
[Pulldown menus, disclosure arrows, particle editor graph stuff, etc. all work just fine in fullscreen mode.]
Running TGB in windowed mode works okay (once you've manually edited the prefs to disable fullscreen mode).
Does anybody have any ideas on what's going on here?
#2
If the latter, then it's great to have feedback that our bugs are getting logged into a database. It gives you some assurance that they're going to be looked at. I've posted several bug reports recently that have had no reply, so it leaves me wondering if they're getting looked into.
09/04/2006 (10:41 pm)
Does "Bug #2046" mean this was a previously reported bug, or does it mean you've just added it to your database, and given it a new bug number? If the former, where can we see this database?If the latter, then it's great to have feedback that our bugs are getting logged into a database. It gives you some assurance that they're going to be looked at. I've posted several bug reports recently that have had no reply, so it leaves me wondering if they're getting looked into.
#3
When we ref a bug number like my above post, it means that the bug you reported is in the repo, or has been added.
It really doesn't matter which, but if it will put your mind more at ease on the duplicate-report thing, I'll say "Added Bug #1234" in future.
If you find a bug, and want to know if it has already been reported, then look through the bugs forum, or use the google site search to check. You may still duplicate a report, but as long as that sort of thing doesn't get spammish, don't worry about it.
/Paul
09/05/2006 (1:26 pm)
@Vern: Yes, bug reports get looked into. We have a private bug repository, using Mantis. When we ref a bug number like my above post, it means that the bug you reported is in the repo, or has been added.
It really doesn't matter which, but if it will put your mind more at ease on the duplicate-report thing, I'll say "Added Bug #1234" in future.
If you find a bug, and want to know if it has already been reported, then look through the bugs forum, or use the google site search to check. You may still duplicate a report, but as long as that sort of thing doesn't get spammish, don't worry about it.
/Paul
#4
I appreciate also that you won't mind if I accidentally submit a duplicate bug report. I'll of course try to avoid this, but I'm glad to hear it's not a problem. :-)
09/06/2006 (1:43 pm)
Alright, thanks Paul. Saying something to the effect of "Added Bug #1234" etc. is very helpful. Thanks! I appreciate also that you won't mind if I accidentally submit a duplicate bug report. I'll of course try to avoid this, but I'm glad to hear it's not a problem. :-)
#5
09/07/2006 (2:55 pm)
Resolved bug #2046
#6
I checked, and the downloadable version of TGB is still 1.1.1. When do you think that you'll be putting the next version, the one with all the recent bug fixes in it, up?
09/07/2006 (4:56 pm)
Thank you, Paul.I checked, and the downloadable version of TGB is still 1.1.1. When do you think that you'll be putting the next version, the one with all the recent bug fixes in it, up?
#7
09/19/2006 (1:02 pm)
There have been a number of "resolved" bugs (in 1.1.1) reported by Paul. Does anybody know when they will be rolled into a new version of TGB? 
Torque Owner Paul Scott
Default Studio Name