Logo Platform
logo amplifiers simplified

Constant error when using the "Popup the first notification on the list" hotkey (N)

Reply
Copied to clipboard!
9 years ago
Apr 9, 2016, 7:07:58 PM
NullReferenceException: Object reference not set to an instance of an object

--------------------------------------------------------------------------------

Amplitude.Unity.Gui.GuiNotification.GetGuiElementName ()

NotificationItem.OnToggleEventCB (UnityEngine.GameObject obj)

UnityEngine.Component:SendMessage(String, Object, SendMessageOptions)

NotificationListPanel:CheckShortcut()

c__Iterator485:MoveNext()



--------------------------------------------------------------------------------

V1.4.2 S3 (64-bit)




It's not a critical error, since I can continue playing normally after it. Still a bit annoying, since it makes using the hotkey a nuisance. Not sure if it's Shifters specific or not, since I started messing around with the UI just lately.



Should be 100% reproductable with these steps:



1. Go to game options -> notifications -> turn all the auto pop-ups off.

2. At the start of your turn in-game exhaust all the notifications in the right corner by using the "Popup the first notification on the list" (default: N). Close all notifications until there's only 1 left.

3. Press N again and the error appears.



Here's a screenshot with the same error:

https://www.dropbox.com/s/s333400l0gksf9t/20160409215757_1.jpg?dl=0
0Send private message
9 years ago
Apr 9, 2016, 9:03:19 PM
Seems to be a null reference exception.

I think this one is easy to fix. I mean c'mon, null pointer checking every here and there isn't that hard ^^
0Send private message
9 years ago
Apr 20, 2016, 8:19:45 PM
Update on this: The null reference exception seems to appearing exactly when you press 'N' too quickly while the previous notification is still closing. At least happens 100% of time at my end.
0Send private message
0Send private message
9 years ago
Apr 30, 2016, 9:52:55 PM
Hey Pikou, glad to hear that. I'm reporting just in case that this is still happening to me in 1.4.4, in a case the patch was supposed to fix it.
0Send private message
9 years ago
May 12, 2016, 3:59:41 PM
Hello,

I just wanted to confirm the bug is still pending because considering we have other priorities at this moment (and few resources) it won't be fix is such a short notice I'm afraid.
0Send private message
?

Click here to login

Reply
Comment

Characters : 0
No results
0Send private message