My application puts up a login dialog before showing the main window. If the login information is not correct, it calls .Close() on the main window to shut down the application. Everything works except the RibbonView.
If I call Close() during the main window Loaded event, the RibbonView throws a null handle exception. I tried making the window start out invisible, and then showing it in the MainWindow ContentRendered event, but then the window (including the RibbonView) shuts down correctly, but with good login, the RibbonView does not show until the window is restored from maximized to be not full screen.
Be advised that the null handle exception does NOT happen when running in Visual Studio, only when running the built application. Is this a known bug, and is there a workaround? Thanks.
If I call Close() during the main window Loaded event, the RibbonView throws a null handle exception. I tried making the window start out invisible, and then showing it in the MainWindow ContentRendered event, but then the window (including the RibbonView) shuts down correctly, but with good login, the RibbonView does not show until the window is restored from maximized to be not full screen.
Be advised that the null handle exception does NOT happen when running in Visual Studio, only when running the built application. Is this a known bug, and is there a workaround? Thanks.
3 Answers, 1 is accepted
0
Hi Chick,
I tried to reproduce the described behavior on our side, but to no avail.
However, I might be missing an important part of your implementation. So, I attached the test project I used to test the described behavior, please feel free to modify it in order to show us how to reproduce the issue on our side.
Thank you for your cooperation.
Regards,
Milena
Telerik
I tried to reproduce the described behavior on our side, but to no avail.
However, I might be missing an important part of your implementation. So, I attached the test project I used to test the described behavior, please feel free to modify it in order to show us how to reproduce the issue on our side.
Thank you for your cooperation.
Regards,
Milena
Telerik
Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.
0
Chuck
Top achievements
Rank 1
Rank 1
answered on 07 Jul 2014, 09:45 AM
Thank you, Milena for your response. I see that your test project does not exhibit the behavior, so here is some more information:
the error is: Object reference not set to an instance of an object. It occurs in WindowChromeWorker.cs in ExtendGlassFrame() on line 193.
Does that help narrow it down?
Chuck
the error is: Object reference not set to an instance of an object. It occurs in WindowChromeWorker.cs in ExtendGlassFrame() on line 193.
Does that help narrow it down?
Chuck
0
Hello Chuck,
Thank you for getting back to us.
Unfortunately, given only the provided information we are not able to track-down the cause of the problem.
Can you elaborate more on your scenario by sending us a sample project which isolates the issue or by
modifying the test project I've sent in my last reply. This will allow us to test it locally and further investigate the reason behind this behavior.
Thank you in advance for your cooperation.
Regards,
Milena
Telerik
Thank you for getting back to us.
Unfortunately, given only the provided information we are not able to track-down the cause of the problem.
Can you elaborate more on your scenario by sending us a sample project which isolates the issue or by
modifying the test project I've sent in my last reply. This will allow us to test it locally and further investigate the reason behind this behavior.
Thank you in advance for your cooperation.
Regards,
Milena
Telerik
Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.