Re: [qooxdoo-devel] Asynchronous behavior

[Daniel W. <dan...@1u...>]

Hi Peter,

you can force a queue flush by calling

qx.ui.core.queue.Manager.flush()


Regards,
Daniel

On 25.08.2014 09:13, Peter Dekkers wrote:
> When developing a widget, I found out that I have to wait for the appear
> event before I can access the underlying dom elements. When I try to
> access this element before that, it is not yet defined. So my code looks
> like this:
> 
> this.addListenerOnce("appear", () => {
>             var container = this.getContentElement().getDomElement();
>             .... do something ...
> }
> 
> Hoever in my code after I instantiate the widget, I have some logic that
> relies on  "... do something...." and I prefer not to make that async also.
>  
> Is there anyway to force this to be "synchronous behavior". So a
> synchronous call where afterwards I can call
> "this.getContentElement().getDomElement()" and get the corresponding
> HTML element back.
> 
> I imagines there is some queueing mechanism, that causes this async
> behavior. So perhaps some command that processes this queue (like a
> forced rendering) ? 
> 
> TIA!
> 
> -- Peter
> 
> 
> ------------------------------------------------------------------------------
> Slashdot TV.  
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> 
> 
> 
> _______________________________________________
> qooxdoo-devel mailing list
> qoo...@li...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>