"invalid context" error messages
Post MTG Forge Related Programming Questions Here
Moderators: timmermac, Blacksmith, KrazyTheFox, Agetian, friarsol, CCGHQ Admins
2 posts
• Page 1 of 1
"invalid context" error messages
by Chris H. » 04 Jul 2012, 13:25
For several weeks I have noticed a strange error message when I run Forge. I see this message in the console when forge is run from within Eclipse. I also see this same message when I launch the forge jar file from my Mac's terminal app.
The four lines below all start with the string:
The four lines below all start with the string:
Date + time + my local network name
java[274] <Error>: CGContextGetCTM: invalid context 0x0
java[274] <Error>: CGContextSetBaseCTM: invalid context 0x0
java[274] <Error>: CGContextGetCTM: invalid context 0x0
java[274] <Error>: CGContextSetBaseCTM: invalid context 0x0
-
Chris H. - Forge Moderator
- Posts: 6320
- Joined: 04 Nov 2008, 12:11
- Location: Mac OS X Yosemite
- Has thanked: 644 times
- Been thanked: 643 times
Re: "invalid context" error messages
by Chris H. » 04 Jul 2012, 19:03
Did a few google searches and this appears to be a problem with the recent Mac OS X Lion 10.7.4 update.
I found a link that suggests that the setIconImage() method is causing this to happen. There is a single instance of this command located in the forge.view.FView class and I commented out line 62.
Rebuilt the project and ran forge and did not receive the error in the console log.
From what I have read on this matter this problem appears to be fixed in the upcoming Mountain Lion 10.8 release.
It looks like this is more of a nuisance than a game stopping bug. It looks like it is limited to the Mac OS X Lion 10.7.4 update.
I found a link that suggests that the setIconImage() method is causing this to happen. There is a single instance of this command located in the forge.view.FView class and I commented out line 62.
Rebuilt the project and ran forge and did not receive the error in the console log.
From what I have read on this matter this problem appears to be fixed in the upcoming Mountain Lion 10.8 release.
It looks like this is more of a nuisance than a game stopping bug. It looks like it is limited to the Mac OS X Lion 10.7.4 update.
-
Chris H. - Forge Moderator
- Posts: 6320
- Joined: 04 Nov 2008, 12:11
- Location: Mac OS X Yosemite
- Has thanked: 644 times
- Been thanked: 643 times
2 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 43 guests