RadWindow.ShowDialog() bug?

[Ivan Kopcanski]

Hi Telerik,

          We are creating RadWIndow() in code-behind and show the window calling its .Show() method (let's say window A).
     That window contains the button that should open another window in the dialog mode.

     Again, we simply create another RadWindow() on button click and call its .ShowDialog() method (let's say modal window B).

     The modal window B appears for a moment with blue modal background and suddenly 
     the underlying window A is shown above that modal window B. The modal window B becomes modal only if it is manually clicked.
     After that everything works fine (window A is not selectable anymore), but this sound like an enormeous oversight and a blocker issue.

     We were using 2009.2.0724.1020 version of Telerik.Windows.Controls.Navigation.dll and everything worked fine, no issues.
     Described issue appeared after we took 2009.2.0904.1030 version (actually, new version of your whole product).

     I've tried with calling .BringToFront() method and .Focus() method after .ShowDialog() call, but nothing significant happens.

     Can you investigate this little further, cause this puts us in a big problem?

[Boyan]

Hi Ivan Kopcanski,

That is strange, we fixed this problem for SP1 which was on the 12fth of August. I checked the issue as you described it with the 2009.2.0904.1030 version which is in fact our Latest Internal Build but was not able to reproduce it. Could you please send me a sample project where I can reproduce it. It will be good if you can send me the dll's you are using with the project as well.
 Sorry for the inconvenience.
 

All the best,
Boyan
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[Ivan Kopcanski]

Hi, Boyan,

     Thank you for your time and effort. I post the support ticket no. 241993 regarding this issue.
There you will find, I hope, all the info that is needed to reproduce the bug so we can continue
the correspondance there. Again, if you are missing some details that you wish to have about it,
please, leave the the note about it on the support ticket thread. We are monitoring it constantly
and we'll give you the needed feedback as soon as possible. Thanks again ;)

[Ivan Kopcanski]

Hi, Boyan,

      Could you please respond to our issue, it causing us big problem that should be fixed as soon as possible?

[Boyan]

Hello Ivan Kopcanski,

 I have answered in the other thread that you entered, the Bug report  N241993 .

Best wishes,
Boyan
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[Ivan Kopcanski]

Hi, Boyan,

       Thank you for your answers, please, re-check the support ticket, I will immediate update it with the correct data.
The staging environment url was wrong, sorry for that. Also, I will try to make some short version of test project to ease
the bug reproduction. Let us continue this on support ticket thread.

[Ivan Kopcanski]

The problem is resolved, modal window B was opening by listening to buttons MouseLeftButtonDown event,
and right after opening that modal window, the underlying window A containing the button was receiving bubbled event.
Because of that it was shown above the modal window, since it figured it out as an "user action" and it brought itself to the top.
The simple solution is to listen to the MouseLeftButtonUp event. Somehow it is either handled by button and not bubbled up 
or the window A does not consider mouse up button as a situation for focusing itself. Thanks again, Boyan, your suggestion for switching from mouse down to mouse up event works ;)