Unexpected Behavior with Event Handlers (Revisited)

0
0

I had previously posted this question puzzling about how my app would lock up while navigating pages.  My initial thought was that it was caused by the Messagebox being used to return a DialogResult.  Without a solution I simply avoided using the Messagebox in that way.  I have since seen that the lock-up problem seems to present itself without the messagebox and I can’t determine the problem.   I recreated the problem in my test case (attached) and I hope you can shed some light on the problem.  I’m using Wisej 2.5.22.

Thanks!

Gerry

Attachment
NavigatePagesTest.zip
General
Share
  • You must to post comments
Filter
Sort by: Recently Active
0
0

Thanks!

  • You must to post comments
0
0

Hi Gerald,

It appen beacause you create both a Desktop and a Page, the page is above the desktop. Cannot have both at the same time!
Comment out Application.Desktop = new MyDesktop() and it’ll works fine. PreviousPage is fine.

Happy coding
Kevin(ITG)
  • Gerald Lemay
    Thanks! I built the project initially as a desktop app. Didn’t know switching caused problems. Are there any other issues with switching it in mid stream? Web.Config, Default.JSON, etc.
  • Luca (ITG)
    Desktop and Page are both top level containers and both have a window manage in it. Only once can be active at any given time. If you need both, a Desktop control can be a child of a Page and all floating windows are inside the child desktop control. You can switch between a Desktop and a Page but only one of them can be visible/active.
  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.