@sebastian
this is NOT a uncommon usage.
Think about, that there can be some data in the document itself! (for example a edit-line with a "search"-button which opens a "search-Window" - a datetimepicker for example)

I am using such a window while getting (asynchron) data from the server. I open such a window modal with the text ("please wait, getting data from the server"). after i get the data from the server, i close this window and the user can now continue his work. (making it NOT modal means, that the user can comtinue working WITHOUT the needet data.

another usage:
i have a native window with some data as a list. after the user clicks at ONE item in this list, i open a QxWindow "inside" the native window to allow the user to edit the "clicked" data.

i think, this are TWO common usages of such a window ;_)

Olli

Sebastian Werner schrieb:

Ok,

the problem was only existing if there is only one window and if this window is modal (a IMHO uncommon usage). It is fixed now in CVS. I added a setActive(false) to the close command to be sure that the active window is not already closed (this is really correct and it is IMHO a good idea - also if we have not had this bug before)

Sebastian


Dietrich Streifert schrieb:

Hi!

Here is my example for the "remaining modal after QxWindow closed" bug:

Load the example and then click on the "Open the dialog" button.

Then close the opened QxWindow by hitting "OK" or "Cancel". The window disappers.

After this all elements on the page are blocked, because the "invisible modal making div" is still there.

Try again to click on the "Open the dialog" button. This would not work.

Verified the bug on InternetExplorer 6, FireFox 1.0.7.

Regards...



Oliver Vogel schrieb:

Is in my TODO-List for Xmas (to write a little demo where the error occours)

Olli


==================================================
Diplom-Informatiker
Oliver Vogel
Geschaeftsfuehrer

Meins und Vogel GmbH  E-Mail: [EMAIL PROTECTED]
Esslinger Str. 45     Tel.:   +49 (7153) 6136-20
                      Fax:    +49 (7153) 6136-99
D 73207 Plochingen    http://www.muv.com/

Handelsregister: Esslingen am Neckar HRB 3536
Geschäftsführer: Dipl.-Inf. Klaus  Meins
                 Dipl.-Inf. Oliver Vogel
==================================================
"wer Rechtschreibfehler findet darf sie behalten"
-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Sebastian Werner
Gesendet: Donnerstag, 24. November 2005 08:55
An: [email protected]
Betreff: Re: [qooxdoo-devel] a little flaw in windows-handling modal

[EMAIL PROTECTED] schrieb:
@ sebastian

i opened a QxWindow (NOT A NATIVE ONE!) with (this is only

a stub, there is more code):
-------------
wm1 = new QxWindow("Bitte warten");
wm1.setSpace(200, 50, 200, 50);
wm1.setModal(true);
window.application.getClientWindow().getClientDocument().add(wm1);
wm1.open();

{{{then there is some magic.}}}

wm1.close();

----------
and i thought, this was all (because closing a modal

window) makes it "unmodal". But this was not the case!
so please add the line:

wm1.setModal(false);

This does work in our demos. Something must be different from your code to ours. The close automatically informs the window manager.

Add setModal(false) will change the settings of the window and is IMHO a bad idea. If this is really a bug - in some case - we should really find the correct reason why it goes wrong.

Sebastian


in the .close() - Method of the QxWindow. i think many

other people can have the same problem.
Olli


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep

through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the web.

DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel





-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


--
Mit freundlichen Grüßen
Dietrich Streifert
Visionet GmbH


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

Modal dialog with QxForm and QxTextArea




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel





-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to