trunk rev. 20565 broke my applikation: does not react on mouse or key events

View: New views
13 Messages — Rating Filter:   Alert me  

trunk rev. 20565 broke my applikation: does not react on mouse or key events

by Dietrich Streifert :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello everybody,

it seems that the change to the blocker broke my application.
The widgets which are added to the document root (a toolbar, a table
etc) don't react anymore on mouse clicks and keyinputs as if all was
blocked by a blocker ;-)
Windows (qx.ui.window.Window) and subwidgets of the window are accessible.

Happended with changeset 20565

A generate.py distclean and generate.py source did not help.

Reverting to rev 20564 solved the problem.

--
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner




------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: trunk rev. 20565 broke my applikation: does not react on mouse or key events

by Christian Schmidt-18 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Dietrich,

do you call block() twice, but unblock() once?

Cheers,
Chris

Dietrich Streifert schrieb:

> Hello everybody,
>
> it seems that the change to the blocker broke my application.
> The widgets which are added to the document root (a toolbar, a table
> etc) don't react anymore on mouse clicks and keyinputs as if all was
> blocked by a blocker ;-)
> Windows (qx.ui.window.Window) and subwidgets of the window are accessible.
>
> Happended with changeset 20565
>
> A generate.py distclean and generate.py source did not help.
>
> Reverting to rev 20564 solved the problem.
>
>  


--
Christian Schmidt
Software Entwickler

1&1 Internet AG - Web Technologies
Ernst-Frey-Straße 9 · DE-76135 Karlsruhe
schmidt.christian@...

Amtsgericht Montabaur / HRB 6484
Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen
Aufsichtsratsvorsitzender: Michael Scheeren


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: trunk rev. 20565 broke my applikation: does not react on mouse or key events

by Dietrich Streifert :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Chirs,

I'm not using any qx.ui.core.Blocker at all. I'm using my own blocking with a blocking window derived from qx.ui.window.Window which lays over the background and is closed on blocking end.



Christian Schmidt schrieb:
Hi Dietrich,

do you call block() twice, but unblock() once?

Cheers,
Chris

Dietrich Streifert schrieb:
  
Hello everybody,

it seems that the change to the blocker broke my application.
The widgets which are added to the document root (a toolbar, a table 
etc) don't react anymore on mouse clicks and keyinputs as if all was 
blocked by a blocker ;-)
Windows (qx.ui.window.Window) and subwidgets of the window are accessible.

Happended with changeset 20565

A generate.py distclean and generate.py source did not help.

Reverting to rev 20564 solved the problem.

  
    


  

-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: trunk rev. 20565 broke my applikation: does not react on mouse or key events

by Christian Schmidt-18 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Dietrich,

oh, it seems to me that it is more complex as expected. Could you pleas
provide a code snippet, which reproduce this issue.

Thanks,
Chris

Dietrich Streifert schrieb:

> Hi Chirs,
>
> I'm not using any qx.ui.core.Blocker at all. I'm using my own blocking
> with a blocking window derived from qx.ui.window.Window which lays
> over the background and is closed on blocking end.
>
>
>
> Christian Schmidt schrieb:
>> Hi Dietrich,
>>
>> do you call block() twice, but unblock() once?
>>
>> Cheers,
>> Chris
>>
>> Dietrich Streifert schrieb:
>>  
>>> Hello everybody,
>>>
>>> it seems that the change to the blocker broke my application.
>>> The widgets which are added to the document root (a toolbar, a table
>>> etc) don't react anymore on mouse clicks and keyinputs as if all was
>>> blocked by a blocker ;-)
>>> Windows (qx.ui.window.Window) and subwidgets of the window are accessible.
>>>
>>> Happended with changeset 20565
>>>
>>> A generate.py distclean and generate.py source did not help.
>>>
>>> Reverting to rev 20564 solved the problem.
>>>
>>>  
>>>    
>>
>>
>>  
>
> --
> Mit freundlichen Grüßen
> Dietrich Streifert
> --
> Visionet GmbH
> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
> Registergericht: Handelsregister Fürth, HRB 6573
> Geschäftsführer: Stefan Lindner
>
>
>  
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>  


--
Christian Schmidt
Software Entwickler

1&1 Internet AG - Web Technologies
Ernst-Frey-Straße 9 · DE-76135 Karlsruhe
schmidt.christian@...

Amtsgericht Montabaur / HRB 6484
Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen
Aufsichtsratsvorsitzender: Michael Scheeren


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: trunk rev. 20565 broke my applikation: does not react on mouse or key events

by Dietrich Streifert :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I'd like to use the playground for this. Is it possible to update the playground to rev > 20564?

As a first step I think I'll disable my own blocking code to test if there is some interference with the qx blocker.

But all this will happen on monday.

Meanwhile thank you for your help.

Christian Schmidt schrieb:
Hi Dietrich,

oh, it seems to me that it is more complex as expected. Could you pleas 
provide a code snippet, which reproduce this issue.

Thanks,
Chris

Dietrich Streifert schrieb:
  
Hi Chirs,

I'm not using any qx.ui.core.Blocker at all. I'm using my own blocking 
with a blocking window derived from qx.ui.window.Window which lays 
over the background and is closed on blocking end.



Christian Schmidt schrieb:
    
Hi Dietrich,

do you call block() twice, but unblock() once?

Cheers,
Chris

Dietrich Streifert schrieb:
  
      
Hello everybody,

it seems that the change to the blocker broke my application.
The widgets which are added to the document root (a toolbar, a table 
etc) don't react anymore on mouse clicks and keyinputs as if all was 
blocked by a blocker ;-)
Windows (qx.ui.window.Window) and subwidgets of the window are accessible.

Happended with changeset 20565

A generate.py distclean and generate.py source did not help.

Reverting to rev 20564 solved the problem.

  
    
        
  
      
-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner


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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
------------------------------------------------------------------------

_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
  
    


  

-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: trunk rev. 20565 broke my applikation: does not react on mouse or key events

by thron7-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message



Dietrich Streifert wrote:
I'd like to use the playground for this. Is it possible to update the playground to rev > 20564?

I guess you're referring to the online Playground (http://demo.qooxdoo.org/devel/Playground)? - It has been updated this afternoon to r20575.

Cheers,
T.


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: trunk rev. 20565 broke my applikation: does not react on mouse or key events

by Dietrich Streifert :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thank you Thomas. Yes it is the playground I've talked about.

thron7 schrieb:


Dietrich Streifert wrote:
I'd like to use the playground for this. Is it possible to update the playground to rev > 20564?

I guess you're referring to the online Playground (http://demo.qooxdoo.org/devel/Playground)? - It has been updated this afternoon to r20575.

Cheers,
T.


------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july

_______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@... https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: trunk rev. 20565 broke my applikation: does not react on mouse or key events

by Dietrich Streifert :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Well after disabling the "busy blocker" of my login widget (based on qx.ui.window.Window) the problem does not happen.

But what is going on here?

My "window is busy blocker"  is used to cover a window with a second window (the blocker, which is semi transparent and has no caption bar) and an atom which displays an animated gif and a text like "loading. please wait...". The atom is on top of the transparent blocker. Both the blocker window and the info atom are added to the application root.

So the effect should be that the user is not able to interact with any widget of the window but still can see what is in this window and has an information what is going on via the atom.

When a window goes in busy state the position and the size of the blocker is adapted to the window.
The zIndex of the blocker is set to the zIndex of the blocked window +1, the zIndex of the atom is set to the zIndex of the blocked window+2.
Both done to lay over the blocked window.
After this the blocker and the atom are made visible via setVisibility('visible').

When the window leaves the busy state both the blocker and the atom are made invisible via setVisibility('hidden').

After the first cycle of the algorithm obove is run there is no possiblity to reach the widget which are placed on the application root.

Does any part of this algorithm intefere with the qx blocker?

Are the zIndex calculations in any way problematic?

Any help would be great.



Dietrich Streifert schrieb:
I'd like to use the playground for this. Is it possible to update the playground to rev > 20564?

As a first step I think I'll disable my own blocking code to test if there is some interference with the qx blocker.

But all this will happen on monday.

Meanwhile thank you for your help.

Christian Schmidt schrieb:
Hi Dietrich,

oh, it seems to me that it is more complex as expected. Could you pleas 
provide a code snippet, which reproduce this issue.

Thanks,
Chris

Dietrich Streifert schrieb:
  
Hi Chirs,

I'm not using any qx.ui.core.Blocker at all. I'm using my own blocking 
with a blocking window derived from qx.ui.window.Window which lays 
over the background and is closed on blocking end.



Christian Schmidt schrieb:
    
Hi Dietrich,

do you call block() twice, but unblock() once?

Cheers,
Chris

Dietrich Streifert schrieb:
  
      
Hello everybody,

it seems that the change to the blocker broke my application.
The widgets which are added to the document root (a toolbar, a table 
etc) don't react anymore on mouse clicks and keyinputs as if all was 
blocked by a blocker ;-)
Windows (qx.ui.window.Window) and subwidgets of the window are accessible.

Happended with changeset 20565

A generate.py distclean and generate.py source did not help.

Reverting to rev 20564 solved the problem.

  
    
        
  
      
-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner


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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
------------------------------------------------------------------------

_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
  
    
  

-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner


  

------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july

_______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@... https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: trunk rev. 20565 broke my applikation: does not react on mouse or key events

by Christian Schmidt-18 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Dietrich,

I have changed the blocker algorithm from unblock() and
unblockContent(). Both methods now take care of the amount of calls
(block/blockContent). It seems to me that the content blocker is not
removed, because a unblockContent call is missing.

How do you set the zIndex for the blocker? Do you call
blockContent(zIndex)? If you set the index with blockContent(zIndex),
please call unblockContent() when you call setVisibility("hidden"). This
should solve you blocking issue.

I will talk with Fabian next week, perhaps only unblock() should take
care of the amount of block() calls.

Cheers,
Chris

Dietrich Streifert schrieb:

> Well after disabling the "busy blocker" of my login widget (based on
> qx.ui.window.Window) the problem does not happen.
>
> But what is going on here?
>
> My "window is busy blocker"  is used to cover a window with a second
> window (the blocker, which is semi transparent and has no caption bar)
> and an atom which displays an animated gif and a text like "loading.
> please wait...". The atom is on top of the transparent blocker. Both
> the blocker window and the info atom are added to the application root.
>
> So the effect should be that the user is not able to interact with any
> widget of the window but still can see what is in this window and has
> an information what is going on via the atom.
>
> When a window goes in busy state the position and the size of the
> blocker is adapted to the window.
> The zIndex of the blocker is set to the zIndex of the blocked window
> +1, the zIndex of the atom is set to the zIndex of the blocked window+2.
> Both done to lay over the blocked window.
> After this the blocker and the atom are made visible via
> setVisibility('visible').
>
> When the window leaves the busy state both the blocker and the atom
> are made invisible via setVisibility('hidden').
>
> After the first cycle of the algorithm obove is run there is no
> possiblity to reach the widget which are placed on the application root.
>
> Does any part of this algorithm intefere with the qx blocker?
>
> Are the zIndex calculations in any way problematic?
>
> Any help would be great.
>
>
>
> Dietrich Streifert schrieb:
>> I'd like to use the playground for this. Is it possible to update the
>> playground to rev > 20564?
>>
>> As a first step I think I'll disable my own blocking code to test if
>> there is some interference with the qx blocker.
>>
>> But all this will happen on monday.
>>
>> Meanwhile thank you for your help.
>>
>> Christian Schmidt schrieb:
>>> Hi Dietrich,
>>>
>>> oh, it seems to me that it is more complex as expected. Could you pleas
>>> provide a code snippet, which reproduce this issue.
>>>
>>> Thanks,
>>> Chris
>>>
>>> Dietrich Streifert schrieb:
>>>  
>>>> Hi Chirs,
>>>>
>>>> I'm not using any qx.ui.core.Blocker at all. I'm using my own blocking
>>>> with a blocking window derived from qx.ui.window.Window which lays
>>>> over the background and is closed on blocking end.
>>>>
>>>>
>>>>
>>>> Christian Schmidt schrieb:
>>>>    
>>>>> Hi Dietrich,
>>>>>
>>>>> do you call block() twice, but unblock() once?
>>>>>
>>>>> Cheers,
>>>>> Chris
>>>>>
>>>>> Dietrich Streifert schrieb:
>>>>>  
>>>>>      
>>>>>> Hello everybody,
>>>>>>
>>>>>> it seems that the change to the blocker broke my application.
>>>>>> The widgets which are added to the document root (a toolbar, a table
>>>>>> etc) don't react anymore on mouse clicks and keyinputs as if all was
>>>>>> blocked by a blocker ;-)
>>>>>> Windows (qx.ui.window.Window) and subwidgets of the window are accessible.
>>>>>>
>>>>>> Happended with changeset 20565
>>>>>>
>>>>>> A generate.py distclean and generate.py source did not help.
>>>>>>
>>>>>> Reverting to rev 20564 solved the problem.
>>>>>>
>>>>>>  
>>>>>>    
>>>>>>        
>>>>>  
>>>>>      
>>>> --
>>>> Mit freundlichen Grüßen
>>>> Dietrich Streifert
>>>> --
>>>> Visionet GmbH
>>>> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
>>>> Registergericht: Handelsregister Fürth, HRB 6573
>>>> Geschäftsführer: Stefan Lindner
>>>>
>>>>
>>>>  
>>>> ------------------------------------------------------------------------
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>>>> trial. Simplify your report design, integration and deployment - and focus on
>>>> what you do best, core application coding. Discover what's new with
>>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>>> ------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> qooxdoo-devel mailing list
>>>> qooxdoo-devel@... <mailto:qooxdoo-devel@...>
>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>>  
>>>>    
>>>  
>>
>> --
>> Mit freundlichen Grüßen
>> Dietrich Streifert
>> --
>> Visionet GmbH
>> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
>> Registergericht: Handelsregister Fürth, HRB 6573
>> Geschäftsführer: Stefan Lindner
>>
>>
>>  
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>> trial. Simplify your report design, integration and deployment - and focus on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> qooxdoo-devel mailing list
>> qooxdoo-devel@...
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>  
>
> --
> Mit freundlichen Grüßen
> Dietrich Streifert
> --
> Visionet GmbH
> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
> Registergericht: Handelsregister Fürth, HRB 6573
> Geschäftsführer: Stefan Lindner
>
>
>  
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>  


--
Christian Schmidt
Software Entwickler

1&1 Internet AG - Web Technologies
Ernst-Frey-Straße 9 · DE-76135 Karlsruhe
schmidt.christian@...

Amtsgericht Montabaur / HRB 6484
Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen
Aufsichtsratsvorsitzender: Michael Scheeren


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: trunk rev. 20565 broke my applikation: does not react on mouse or key events

by Dietrich Streifert :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Chris,

well, as said before, I'm not using any blockContent, unblockContent calls at all! I'm just setting the property zIndex of the window and the atom:
Here is an excerpt from the code within the scope of the qx.ui.window.Window in order to block the window:

    var my zIndex = this.getZIndex();

    blockerWindow.setZIndex(zIndex+1);
    messageAtom.setZIndex(zIndex+2);

    blockerWindow.setVisibility("visible");
    messageAtom.setVisibility("visiible");


Hiding is more simple:

    messageAtom.setVisibility("hidden");
    blockerWindow.setVisibility("hidden");


Not included are the calculations of the position and dimensions of the blockerWindow and messageAtom which place them above the window.

So I'm not using qx blocker code at all (none that I'm aware of).

Christian Schmidt schrieb:
Hi Dietrich,

I have changed the blocker algorithm from unblock() and 
unblockContent(). Both methods now take care of the amount of calls 
(block/blockContent). It seems to me that the content blocker is not 
removed, because a unblockContent call is missing.

How do you set the zIndex for the blocker? Do you call 
blockContent(zIndex)? If you set the index with blockContent(zIndex), 
please call unblockContent() when you call setVisibility("hidden"). This 
should solve you blocking issue.

I will talk with Fabian next week, perhaps only unblock() should take 
care of the amount of block() calls.

Cheers,
Chris

Dietrich Streifert schrieb:
  
Well after disabling the "busy blocker" of my login widget (based on 
qx.ui.window.Window) the problem does not happen.

But what is going on here?

My "window is busy blocker"  is used to cover a window with a second 
window (the blocker, which is semi transparent and has no caption bar) 
and an atom which displays an animated gif and a text like "loading. 
please wait...". The atom is on top of the transparent blocker. Both 
the blocker window and the info atom are added to the application root.

So the effect should be that the user is not able to interact with any 
widget of the window but still can see what is in this window and has 
an information what is going on via the atom.

When a window goes in busy state the position and the size of the 
blocker is adapted to the window.
The zIndex of the blocker is set to the zIndex of the blocked window 
+1, the zIndex of the atom is set to the zIndex of the blocked window+2.
Both done to lay over the blocked window.
After this the blocker and the atom are made visible via 
setVisibility('visible').

When the window leaves the busy state both the blocker and the atom 
are made invisible via setVisibility('hidden').

After the first cycle of the algorithm obove is run there is no 
possiblity to reach the widget which are placed on the application root.

Does any part of this algorithm intefere with the qx blocker?

Are the zIndex calculations in any way problematic?

Any help would be great.



Dietrich Streifert schrieb:
    
I'd like to use the playground for this. Is it possible to update the 
playground to rev > 20564?

As a first step I think I'll disable my own blocking code to test if 
there is some interference with the qx blocker.

But all this will happen on monday.

Meanwhile thank you for your help.

Christian Schmidt schrieb:
      
Hi Dietrich,

oh, it seems to me that it is more complex as expected. Could you pleas 
provide a code snippet, which reproduce this issue.

Thanks,
Chris

Dietrich Streifert schrieb:
  
        
Hi Chirs,

I'm not using any qx.ui.core.Blocker at all. I'm using my own blocking 
with a blocking window derived from qx.ui.window.Window which lays 
over the background and is closed on blocking end.



Christian Schmidt schrieb:
    
          
Hi Dietrich,

do you call block() twice, but unblock() once?

Cheers,
Chris

Dietrich Streifert schrieb:
  
      
            
Hello everybody,

it seems that the change to the blocker broke my application.
The widgets which are added to the document root (a toolbar, a table 
etc) don't react anymore on mouse clicks and keyinputs as if all was 
blocked by a blocker ;-)
Windows (qx.ui.window.Window) and subwidgets of the window are accessible.

Happended with changeset 20565

A generate.py distclean and generate.py source did not help.

Reverting to rev 20564 solved the problem.

  
    
        
              
  
      
            
-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner


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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
------------------------------------------------------------------------

_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@... qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
  
    
          
  
        
-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner


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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
------------------------------------------------------------------------

_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
  
      
-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner


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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
------------------------------------------------------------------------

_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
  
    


  

-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: trunk rev. 20565 broke my applikation: does not react on mouse or key events

by Christian Schmidt-18 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Dietrich,

I have done a look at the window manager and saw that the implementation
could keep the application blocked. I fixed this on trunk with rev. 20583.

Could you please update to this reversion? Does this solve your issue?

Cheers,
Chris

Dietrich Streifert schrieb:

> Hi Chris,
>
> well, as said before, I'm not using any blockContent, unblockContent
> calls at all! I'm just setting the property zIndex of the window and
> the atom:
> Here is an excerpt from the code within the scope of the
> qx.ui.window.Window in order to block the window:
>
>     var my zIndex = this.getZIndex();
>
>     blockerWindow.setZIndex(zIndex+1);
>     messageAtom.setZIndex(zIndex+2);
>
>     blockerWindow.setVisibility("visible");
>     messageAtom.setVisibility("visiible");
>
>
> Hiding is more simple:
>
>     messageAtom.setVisibility("hidden");
>     blockerWindow.setVisibility("hidden");
>
>
> Not included are the calculations of the position and dimensions of
> the blockerWindow and messageAtom which place them above the window.
>
> So I'm not using qx blocker code at all (none that I'm aware of).
>
> Christian Schmidt schrieb:
>> Hi Dietrich,
>>
>> I have changed the blocker algorithm from unblock() and
>> unblockContent(). Both methods now take care of the amount of calls
>> (block/blockContent). It seems to me that the content blocker is not
>> removed, because a unblockContent call is missing.
>>
>> How do you set the zIndex for the blocker? Do you call
>> blockContent(zIndex)? If you set the index with blockContent(zIndex),
>> please call unblockContent() when you call setVisibility("hidden"). This
>> should solve you blocking issue.
>>
>> I will talk with Fabian next week, perhaps only unblock() should take
>> care of the amount of block() calls.
>>
>> Cheers,
>> Chris
>>
>> Dietrich Streifert schrieb:
>>  
>>> Well after disabling the "busy blocker" of my login widget (based on
>>> qx.ui.window.Window) the problem does not happen.
>>>
>>> But what is going on here?
>>>
>>> My "window is busy blocker"  is used to cover a window with a second
>>> window (the blocker, which is semi transparent and has no caption bar)
>>> and an atom which displays an animated gif and a text like "loading.
>>> please wait...". The atom is on top of the transparent blocker. Both
>>> the blocker window and the info atom are added to the application root.
>>>
>>> So the effect should be that the user is not able to interact with any
>>> widget of the window but still can see what is in this window and has
>>> an information what is going on via the atom.
>>>
>>> When a window goes in busy state the position and the size of the
>>> blocker is adapted to the window.
>>> The zIndex of the blocker is set to the zIndex of the blocked window
>>> +1, the zIndex of the atom is set to the zIndex of the blocked window+2.
>>> Both done to lay over the blocked window.
>>> After this the blocker and the atom are made visible via
>>> setVisibility('visible').
>>>
>>> When the window leaves the busy state both the blocker and the atom
>>> are made invisible via setVisibility('hidden').
>>>
>>> After the first cycle of the algorithm obove is run there is no
>>> possiblity to reach the widget which are placed on the application root.
>>>
>>> Does any part of this algorithm intefere with the qx blocker?
>>>
>>> Are the zIndex calculations in any way problematic?
>>>
>>> Any help would be great.
>>>
>>>
>>>
>>> Dietrich Streifert schrieb:
>>>    
>>>> I'd like to use the playground for this. Is it possible to update the
>>>> playground to rev > 20564?
>>>>
>>>> As a first step I think I'll disable my own blocking code to test if
>>>> there is some interference with the qx blocker.
>>>>
>>>> But all this will happen on monday.
>>>>
>>>> Meanwhile thank you for your help.
>>>>
>>>> Christian Schmidt schrieb:
>>>>      
>>>>> Hi Dietrich,
>>>>>
>>>>> oh, it seems to me that it is more complex as expected. Could you pleas
>>>>> provide a code snippet, which reproduce this issue.
>>>>>
>>>>> Thanks,
>>>>> Chris
>>>>>
>>>>> Dietrich Streifert schrieb:
>>>>>  
>>>>>        
>>>>>> Hi Chirs,
>>>>>>
>>>>>> I'm not using any qx.ui.core.Blocker at all. I'm using my own blocking
>>>>>> with a blocking window derived from qx.ui.window.Window which lays
>>>>>> over the background and is closed on blocking end.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Christian Schmidt schrieb:
>>>>>>    
>>>>>>          
>>>>>>> Hi Dietrich,
>>>>>>>
>>>>>>> do you call block() twice, but unblock() once?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Chris
>>>>>>>
>>>>>>> Dietrich Streifert schrieb:
>>>>>>>  
>>>>>>>      
>>>>>>>            
>>>>>>>> Hello everybody,
>>>>>>>>
>>>>>>>> it seems that the change to the blocker broke my application.
>>>>>>>> The widgets which are added to the document root (a toolbar, a table
>>>>>>>> etc) don't react anymore on mouse clicks and keyinputs as if all was
>>>>>>>> blocked by a blocker ;-)
>>>>>>>> Windows (qx.ui.window.Window) and subwidgets of the window are accessible.
>>>>>>>>
>>>>>>>> Happended with changeset 20565
>>>>>>>>
>>>>>>>> A generate.py distclean and generate.py source did not help.
>>>>>>>>
>>>>>>>> Reverting to rev 20564 solved the problem.
>>>>>>>>
>>>>>>>>  
>>>>>>>>    
>>>>>>>>        
>>>>>>>>              
>>>>>>>  
>>>>>>>      
>>>>>>>            
>>>>>> --
>>>>>> Mit freundlichen Grüßen
>>>>>> Dietrich Streifert
>>>>>> --
>>>>>> Visionet GmbH
>>>>>> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
>>>>>> Registergericht: Handelsregister Fürth, HRB 6573
>>>>>> Geschäftsführer: Stefan Lindner
>>>>>>
>>>>>>
>>>>>>  
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>>>>>> trial. Simplify your report design, integration and deployment - and focus on
>>>>>> what you do best, core application coding. Discover what's new with
>>>>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>> _______________________________________________
>>>>>> qooxdoo-devel mailing list
>>>>>> qooxdoo-devel@... <mailto:qooxdoo-devel@...>
>>>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>>>>  
>>>>>>    
>>>>>>          
>>>>>  
>>>>>        
>>>> --
>>>> Mit freundlichen Grüßen
>>>> Dietrich Streifert
>>>> --
>>>> Visionet GmbH
>>>> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
>>>> Registergericht: Handelsregister Fürth, HRB 6573
>>>> Geschäftsführer: Stefan Lindner
>>>>
>>>>
>>>>  
>>>> ------------------------------------------------------------------------
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>>>> trial. Simplify your report design, integration and deployment - and focus on
>>>> what you do best, core application coding. Discover what's new with
>>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>>> ------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> qooxdoo-devel mailing list
>>>> qooxdoo-devel@...
>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>>  
>>>>      
>>> --
>>> Mit freundlichen Grüßen
>>> Dietrich Streifert
>>> --
>>> Visionet GmbH
>>> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
>>> Registergericht: Handelsregister Fürth, HRB 6573
>>> Geschäftsführer: Stefan Lindner
>>>
>>>
>>>  
>>> ------------------------------------------------------------------------
>>>
>>> ------------------------------------------------------------------------------
>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>>> trial. Simplify your report design, integration and deployment - and focus on
>>> what you do best, core application coding. Discover what's new with
>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> qooxdoo-devel@...
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>  
>>>    
>>
>>
>>  
>
> --
> Mit freundlichen Grüßen
> Dietrich Streifert
> --
> Visionet GmbH
> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
> Registergericht: Handelsregister Fürth, HRB 6573
> Geschäftsführer: Stefan Lindner
>
>
>  
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>  


--
Christian Schmidt
Software Entwickler

1&1 Internet AG - Web Technologies
Ernst-Frey-Straße 9 · DE-76135 Karlsruhe
schmidt.christian@...

Amtsgericht Montabaur / HRB 6484
Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen
Aufsichtsratsvorsitzender: Michael Scheeren


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: trunk rev. 20565 broke my applikation: does not react on mouse or key events

by Dietrich Streifert :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Yep! That solved it!

Great job Chris!

What do you think about my method of window blocking? Is there another, more compliant way to do it?

Christian Schmidt schrieb:
Hi Dietrich,

I have done a look at the window manager and saw that the implementation 
could keep the application blocked. I fixed this on trunk with rev. 20583.

Could you please update to this reversion? Does this solve your issue?

Cheers,
Chris

Dietrich Streifert schrieb:
  
Hi Chris,

well, as said before, I'm not using any blockContent, unblockContent 
calls at all! I'm just setting the property zIndex of the window and 
the atom:
Here is an excerpt from the code within the scope of the 
qx.ui.window.Window in order to block the window:

    var my zIndex = this.getZIndex();

    blockerWindow.setZIndex(zIndex+1);
    messageAtom.setZIndex(zIndex+2);

    blockerWindow.setVisibility("visible");
    messageAtom.setVisibility("visiible");


Hiding is more simple:

    messageAtom.setVisibility("hidden");
    blockerWindow.setVisibility("hidden");


Not included are the calculations of the position and dimensions of 
the blockerWindow and messageAtom which place them above the window.

So I'm not using qx blocker code at all (none that I'm aware of).

Christian Schmidt schrieb:
    
Hi Dietrich,

I have changed the blocker algorithm from unblock() and 
unblockContent(). Both methods now take care of the amount of calls 
(block/blockContent). It seems to me that the content blocker is not 
removed, because a unblockContent call is missing.

How do you set the zIndex for the blocker? Do you call 
blockContent(zIndex)? If you set the index with blockContent(zIndex), 
please call unblockContent() when you call setVisibility("hidden"). This 
should solve you blocking issue.

I will talk with Fabian next week, perhaps only unblock() should take 
care of the amount of block() calls.

Cheers,
Chris

Dietrich Streifert schrieb:
  
      
Well after disabling the "busy blocker" of my login widget (based on 
qx.ui.window.Window) the problem does not happen.

But what is going on here?

My "window is busy blocker"  is used to cover a window with a second 
window (the blocker, which is semi transparent and has no caption bar) 
and an atom which displays an animated gif and a text like "loading. 
please wait...". The atom is on top of the transparent blocker. Both 
the blocker window and the info atom are added to the application root.

So the effect should be that the user is not able to interact with any 
widget of the window but still can see what is in this window and has 
an information what is going on via the atom.

When a window goes in busy state the position and the size of the 
blocker is adapted to the window.
The zIndex of the blocker is set to the zIndex of the blocked window 
+1, the zIndex of the atom is set to the zIndex of the blocked window+2.
Both done to lay over the blocked window.
After this the blocker and the atom are made visible via 
setVisibility('visible').

When the window leaves the busy state both the blocker and the atom 
are made invisible via setVisibility('hidden').

After the first cycle of the algorithm obove is run there is no 
possiblity to reach the widget which are placed on the application root.

Does any part of this algorithm intefere with the qx blocker?

Are the zIndex calculations in any way problematic?

Any help would be great.



Dietrich Streifert schrieb:
    
        
I'd like to use the playground for this. Is it possible to update the 
playground to rev > 20564?

As a first step I think I'll disable my own blocking code to test if 
there is some interference with the qx blocker.

But all this will happen on monday.

Meanwhile thank you for your help.

Christian Schmidt schrieb:
      
          
Hi Dietrich,

oh, it seems to me that it is more complex as expected. Could you pleas 
provide a code snippet, which reproduce this issue.

Thanks,
Chris

Dietrich Streifert schrieb:
  
        
            
Hi Chirs,

I'm not using any qx.ui.core.Blocker at all. I'm using my own blocking 
with a blocking window derived from qx.ui.window.Window which lays 
over the background and is closed on blocking end.



Christian Schmidt schrieb:
    
          
              
Hi Dietrich,

do you call block() twice, but unblock() once?

Cheers,
Chris

Dietrich Streifert schrieb:
  
      
            
                
Hello everybody,

it seems that the change to the blocker broke my application.
The widgets which are added to the document root (a toolbar, a table 
etc) don't react anymore on mouse clicks and keyinputs as if all was 
blocked by a blocker ;-)
Windows (qx.ui.window.Window) and subwidgets of the window are accessible.

Happended with changeset 20565

A generate.py distclean and generate.py source did not help.

Reverting to rev 20564 solved the problem.

  
    
        
              
                  
  
      
            
                
-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner


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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
------------------------------------------------------------------------

_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@... qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
  
    
          
              
  
        
            
-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner


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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
------------------------------------------------------------------------

_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
  
      
          
-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner


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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
------------------------------------------------------------------------

_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
  
    
        
  
      
-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner


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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
------------------------------------------------------------------------

_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
  
    


  

-- 
Mit freundlichen Grüßen
Dietrich Streifert
--
Visionet GmbH
Firmensitz: Am Weichselgarten 7, 91058 Erlangen
Registergericht: Handelsregister Fürth, HRB 6573
Geschäftsführer: Stefan Lindner



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: trunk rev. 20565 broke my applikation: does not react on mouse or key events

by Christian Schmidt-18 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Dietrich,

perfect, thanks.

I don't know your application code, so I don't know if there is a more
compliant way to do this. Perhaps bringToFront()[1] could also be a
possibility, but I'm not sure.

Cheers,
Chris


[1]
http://demo.qooxdoo.org/current/apiviewer/#qx.ui.window.Manager~bringToFront

Dietrich Streifert schrieb:

> Yep! That solved it!
>
> Great job Chris!
>
> What do you think about my method of window blocking? Is there
> another, more compliant way to do it?
>
> Christian Schmidt schrieb:
>> Hi Dietrich,
>>
>> I have done a look at the window manager and saw that the implementation
>> could keep the application blocked. I fixed this on trunk with rev. 20583.
>>
>> Could you please update to this reversion? Does this solve your issue?
>>
>> Cheers,
>> Chris
>>
>> Dietrich Streifert schrieb:
>>  
>>> Hi Chris,
>>>
>>> well, as said before, I'm not using any blockContent, unblockContent
>>> calls at all! I'm just setting the property zIndex of the window and
>>> the atom:
>>> Here is an excerpt from the code within the scope of the
>>> qx.ui.window.Window in order to block the window:
>>>
>>>     var my zIndex = this.getZIndex();
>>>
>>>     blockerWindow.setZIndex(zIndex+1);
>>>     messageAtom.setZIndex(zIndex+2);
>>>
>>>     blockerWindow.setVisibility("visible");
>>>     messageAtom.setVisibility("visiible");
>>>
>>>
>>> Hiding is more simple:
>>>
>>>     messageAtom.setVisibility("hidden");
>>>     blockerWindow.setVisibility("hidden");
>>>
>>>
>>> Not included are the calculations of the position and dimensions of
>>> the blockerWindow and messageAtom which place them above the window.
>>>
>>> So I'm not using qx blocker code at all (none that I'm aware of).
>>>
>>> Christian Schmidt schrieb:
>>>    
>>>> Hi Dietrich,
>>>>
>>>> I have changed the blocker algorithm from unblock() and
>>>> unblockContent(). Both methods now take care of the amount of calls
>>>> (block/blockContent). It seems to me that the content blocker is not
>>>> removed, because a unblockContent call is missing.
>>>>
>>>> How do you set the zIndex for the blocker? Do you call
>>>> blockContent(zIndex)? If you set the index with blockContent(zIndex),
>>>> please call unblockContent() when you call setVisibility("hidden"). This
>>>> should solve you blocking issue.
>>>>
>>>> I will talk with Fabian next week, perhaps only unblock() should take
>>>> care of the amount of block() calls.
>>>>
>>>> Cheers,
>>>> Chris
>>>>
>>>> Dietrich Streifert schrieb:
>>>>  
>>>>      
>>>>> Well after disabling the "busy blocker" of my login widget (based on
>>>>> qx.ui.window.Window) the problem does not happen.
>>>>>
>>>>> But what is going on here?
>>>>>
>>>>> My "window is busy blocker"  is used to cover a window with a second
>>>>> window (the blocker, which is semi transparent and has no caption bar)
>>>>> and an atom which displays an animated gif and a text like "loading.
>>>>> please wait...". The atom is on top of the transparent blocker. Both
>>>>> the blocker window and the info atom are added to the application root.
>>>>>
>>>>> So the effect should be that the user is not able to interact with any
>>>>> widget of the window but still can see what is in this window and has
>>>>> an information what is going on via the atom.
>>>>>
>>>>> When a window goes in busy state the position and the size of the
>>>>> blocker is adapted to the window.
>>>>> The zIndex of the blocker is set to the zIndex of the blocked window
>>>>> +1, the zIndex of the atom is set to the zIndex of the blocked window+2.
>>>>> Both done to lay over the blocked window.
>>>>> After this the blocker and the atom are made visible via
>>>>> setVisibility('visible').
>>>>>
>>>>> When the window leaves the busy state both the blocker and the atom
>>>>> are made invisible via setVisibility('hidden').
>>>>>
>>>>> After the first cycle of the algorithm obove is run there is no
>>>>> possiblity to reach the widget which are placed on the application root.
>>>>>
>>>>> Does any part of this algorithm intefere with the qx blocker?
>>>>>
>>>>> Are the zIndex calculations in any way problematic?
>>>>>
>>>>> Any help would be great.
>>>>>
>>>>>
>>>>>
>>>>> Dietrich Streifert schrieb:
>>>>>    
>>>>>        
>>>>>> I'd like to use the playground for this. Is it possible to update the
>>>>>> playground to rev > 20564?
>>>>>>
>>>>>> As a first step I think I'll disable my own blocking code to test if
>>>>>> there is some interference with the qx blocker.
>>>>>>
>>>>>> But all this will happen on monday.
>>>>>>
>>>>>> Meanwhile thank you for your help.
>>>>>>
>>>>>> Christian Schmidt schrieb:
>>>>>>      
>>>>>>          
>>>>>>> Hi Dietrich,
>>>>>>>
>>>>>>> oh, it seems to me that it is more complex as expected. Could you pleas
>>>>>>> provide a code snippet, which reproduce this issue.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Chris
>>>>>>>
>>>>>>> Dietrich Streifert schrieb:
>>>>>>>  
>>>>>>>        
>>>>>>>            
>>>>>>>> Hi Chirs,
>>>>>>>>
>>>>>>>> I'm not using any qx.ui.core.Blocker at all. I'm using my own blocking
>>>>>>>> with a blocking window derived from qx.ui.window.Window which lays
>>>>>>>> over the background and is closed on blocking end.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Christian Schmidt schrieb:
>>>>>>>>    
>>>>>>>>          
>>>>>>>>              
>>>>>>>>> Hi Dietrich,
>>>>>>>>>
>>>>>>>>> do you call block() twice, but unblock() once?
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Chris
>>>>>>>>>
>>>>>>>>> Dietrich Streifert schrieb:
>>>>>>>>>  
>>>>>>>>>      
>>>>>>>>>            
>>>>>>>>>                
>>>>>>>>>> Hello everybody,
>>>>>>>>>>
>>>>>>>>>> it seems that the change to the blocker broke my application.
>>>>>>>>>> The widgets which are added to the document root (a toolbar, a table
>>>>>>>>>> etc) don't react anymore on mouse clicks and keyinputs as if all was
>>>>>>>>>> blocked by a blocker ;-)
>>>>>>>>>> Windows (qx.ui.window.Window) and subwidgets of the window are accessible.
>>>>>>>>>>
>>>>>>>>>> Happended with changeset 20565
>>>>>>>>>>
>>>>>>>>>> A generate.py distclean and generate.py source did not help.
>>>>>>>>>>
>>>>>>>>>> Reverting to rev 20564 solved the problem.
>>>>>>>>>>
>>>>>>>>>>  
>>>>>>>>>>    
>>>>>>>>>>        
>>>>>>>>>>              
>>>>>>>>>>                  
>>>>>>>>>  
>>>>>>>>>      
>>>>>>>>>            
>>>>>>>>>                
>>>>>>>> --
>>>>>>>> Mit freundlichen Grüßen
>>>>>>>> Dietrich Streifert
>>>>>>>> --
>>>>>>>> Visionet GmbH
>>>>>>>> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
>>>>>>>> Registergericht: Handelsregister Fürth, HRB 6573
>>>>>>>> Geschäftsführer: Stefan Lindner
>>>>>>>>
>>>>>>>>
>>>>>>>>  
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>>>>>>>> trial. Simplify your report design, integration and deployment - and focus on
>>>>>>>> what you do best, core application coding. Discover what's new with
>>>>>>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> qooxdoo-devel mailing list
>>>>>>>> qooxdoo-devel@... <mailto:qooxdoo-devel@...>
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>>>>>>  
>>>>>>>>    
>>>>>>>>          
>>>>>>>>              
>>>>>>>  
>>>>>>>        
>>>>>>>            
>>>>>> --
>>>>>> Mit freundlichen Grüßen
>>>>>> Dietrich Streifert
>>>>>> --
>>>>>> Visionet GmbH
>>>>>> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
>>>>>> Registergericht: Handelsregister Fürth, HRB 6573
>>>>>> Geschäftsführer: Stefan Lindner
>>>>>>
>>>>>>
>>>>>>  
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>>>>>> trial. Simplify your report design, integration and deployment - and focus on
>>>>>> what you do best, core application coding. Discover what's new with
>>>>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>> _______________________________________________
>>>>>> qooxdoo-devel mailing list
>>>>>> qooxdoo-devel@...
>>>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>>>>  
>>>>>>      
>>>>>>          
>>>>> --
>>>>> Mit freundlichen Grüßen
>>>>> Dietrich Streifert
>>>>> --
>>>>> Visionet GmbH
>>>>> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
>>>>> Registergericht: Handelsregister Fürth, HRB 6573
>>>>> Geschäftsführer: Stefan Lindner
>>>>>
>>>>>
>>>>>  
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>>>>> trial. Simplify your report design, integration and deployment - and focus on
>>>>> what you do best, core application coding. Discover what's new with
>>>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> _______________________________________________
>>>>> qooxdoo-devel mailing list
>>>>> qooxdoo-devel@...
>>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>>>  
>>>>>    
>>>>>        
>>>>  
>>>>      
>>> --
>>> Mit freundlichen Grüßen
>>> Dietrich Streifert
>>> --
>>> Visionet GmbH
>>> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
>>> Registergericht: Handelsregister Fürth, HRB 6573
>>> Geschäftsführer: Stefan Lindner
>>>
>>>
>>>  
>>> ------------------------------------------------------------------------
>>>
>>> ------------------------------------------------------------------------------
>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>>> trial. Simplify your report design, integration and deployment - and focus on
>>> what you do best, core application coding. Discover what's new with
>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> qooxdoo-devel@...
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>  
>>>    
>>
>>
>>  
>
> --
> Mit freundlichen Grüßen
> Dietrich Streifert
> --
> Visionet GmbH
> Firmensitz: Am Weichselgarten 7, 91058 Erlangen
> Registergericht: Handelsregister Fürth, HRB 6573
> Geschäftsführer: Stefan Lindner
>
>
>  
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>  


--
Christian Schmidt
Software Entwickler

1&1 Internet AG - Web Technologies
Ernst-Frey-Straße 9 · DE-76135 Karlsruhe
schmidt.christian@...

Amtsgericht Montabaur / HRB 6484
Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen
Aufsichtsratsvorsitzender: Michael Scheeren


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel