Oddities with gScreen.

Bug reports for the stable versions go here.
Post Reply
User avatar
AssumedPseudonym
Militia Captain
Militia Captain
Posts: 871
Joined: Thu Aug 29, 2013 5:18 am
Location: On the other side of the screen.

Oddities with gScreen.

Post by AssumedPseudonym » Fri Oct 31, 2014 4:19 am

 Atarlost and I were poking at this one over on IRC. Using the following:

Code: Select all

		<Events>
			<OnUpdate>
				(if (isError gScreen)
					(plyMessage gPlayer "Error!")
					(plyMessage gPlayer gScreen)
				)
			</OnUpdate>
			<OnGlobalPaneInit>
				(scrSetDesc gScreen (cat (scrGetDesc gScreen) "\n\n" gScreen))
			</OnGlobalPaneInit>
		</Events>
 It appears that gScreen always defines as the same number (which, at a guess, is somehow related to the date — it was 1303832 on 10/30/14, but changed to 1304352 at midnight), and is subsequently never undefined by anything short of relaunching Transcendence. This behavior holds true regardless of mods loaded, choice of playership, or adventure being played. Obviously the variable works for the screens it is supposed to called from, so I’m not sure that this could really be considered a bug. Even so, it seems like very odd behavior.
 Atarlost suspects a bad pointer.
Image

My mods on Xelerus: Click here!

Of all the things I’ve lost in life, I miss my mind the least. (I’m having a lot more fun without it!)

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest