An item in the navigator (a webpage) is marked with an “A” in left corner - see picture. I don 't know how it came there, and it was no problem in xojo2015R2.4, BUT it is in the new version xojo2015R3. Can anybody tell me how to remedy this situation, and possibly why the “A” is there in the first place?
The “A” means that that item has attributes assigned to it. Select it in the Inspector, click the Advanced tab of the Inspector (the “Gear” icon) and see what is specified for Attributes.
[h]Is there a bug in xojo2015R3 ?[/h]
Thank you, Paul. With that knowlegde, it proved not to be the cause of the error:
The code
gives NilObjectException in version xojo2015R3, but runs without error in xojo2015R2.4.
What attribute is set on that control?
We suspected the attribute was causing the Unhandled NilObjectException, as it was the only webpage marked with an A. The attribute gave a name of a radiobutton no longer existing. (This parameter was set unintentionally.)
The Unhandled NilObjectException is still being thrown with the attrubute removed.
Another special thing with this page is that it is shown with an open dialog, using DialogContact1.Show in the webpage.shown event handler. We have one more page in the project that it is shown with an open dialog; this functions without problem in r3. We have played with different dialog types (sheet vs. modal), but with no change.
It functions in 2015r2.4, but throws an Unhandled NilObjectException in Xojo 2015r3.
By the way; pressing resume, I get the following information:
[code]This application has encountered an error and cannot continue.
Unhandled NilObjectException
Message:
Stack:
MyInfoPage.MyInfoPage.Constructor%%o<MyInfoPage.MyInfoPage>
Session.Session.MyInfoPage%o<MyInfoPage.MyInfoPage>%o<Session.Session>
MyInfoPage.MyInfoPage%o<MyInfoPage.MyInfoPage>%
MenuPageContainer.MenuPageContainer.GotoPage%%o<MenuPageContainer.MenuPageContainer>
MenuPageContainer.MenuPageContainer.btGoToPage_Action%%o<MenuPageContainer.MenuPageContainer>o
Delegate.IM_Invoke%%o
AddHandler.Stub.29%%
WebButton._ExecuteEvent%b%osA1v
WebControl.!_ExecuteEvent%b%ssA1v
WebSession._HandleEvent%%oso<_HTTPServer.HTTPRequestContext>
WebSession._HandleRequest%i4%oso<_HTTPServer.HTTPRequestContext>
WebApplication._HandleHTTPRequest%%oo<_HTTPServer.HTTPRequestContext>
_HTTPServer.HTTPRequestThread.Event_Run%%o<_HTTPServer.HTTPRequestThread>[/code]
Did you create your own constructor for the webpage?
No, it follows the pattern we use for most webpages.
We just made a complete new page from scratch, exactly like the one which throws the error. This new functions without problems in r3.
When we duplicated the page, the duplicate gave error. So it must have been some “gravel” in the machinery, perhaps caused by the errounious attribute given to the original page.
Thank you, Paul and Greg, for your swift answers and eager to solve the problem - highly appreciated!