I have no code handy, but I had good results firing the "execute" event
on buttons. Maybe you should try this.
T.
Ken MacDonald wrote:
I'm beginning to think that there is no way to do this in qooxdoo:
create a widget
add a listener to that widget for an event, e.g. "mouseup"
somehow trigger
Gene Amtower wrote:
Ken,
Did you ever figure this out yesterday? From trying to find the
answer in the manual, I think some additional knowledge and examples
is needed in the section on events - it's rather concise to the point
of not being helpful. Some examples in the manual would be he
Thanks, Derrell,
Related to this thread on browser event security, as well as other
threads on file download security, where a user response to a security
dialog reloads the entire RIA page, I have created enhancement Bug 3282,
requesting a new method (or methods) to poll and preset browser securi
stener("mouseup", myMouseupHandler);
//invoke mouseup handler programmatically
myMouseupHandler();
Regards,
Andreas
Von: Ken MacDonald [mailto:drken...@gmail.com]
Gesendet: Donnerstag, 24. Dezember 2009 22:01
An: qooxdoo-devel@lists.sourceforge.net
Betreff: Re: [qooxdoo-devel] artifici
On Mon, Dec 28, 2009 at 09:25, Gene Amtower wrote:
> Derrell,
>
> I agree that we should embrace this security measure - it protects us from
> the "other" developers.
>
> However, this touches on another post some months ago, where the IE
> security bar blocked an action and then reloaded the en
Derrell,
I agree that we should embrace this security measure - it protects us
from the "other" developers.
However, this touches on another post some months ago, where the IE
security bar blocked an action and then reloaded the entire page when
the user verified the action. In a normal webpage
On Mon, Dec 28, 2009 at 08:27, Ken MacDonald wrote:
> Hi Andreas,
> Thanks for the snippet. Unfortunately, IE can tell whether the event
> handler was just 'called' or whether it was fired. See the difference in
> IE8, making sure that your popup blocker is enabled:
>
This sounds like a "good th
rammaticallymyMouseupHandler();
> Regards,Andreas
> Von: Ken MacDonald [mailto:drken...@gmail.com] Gesendet: Donnerstag, 24.
> Dezember 2009 22:01An: qooxdoo-de...@lists.sourceforge.netbetreff: Re:
> [qooxdoo-devel] artificially getting to a listener
> Hi Gene,Still a mystery. I
>alert("event fired by user!");
> }
> else {
>alert("handler invoked programmatically!");
> }
> }
> button1.addListener("mouseup", myMouseupHandler);
>
> //invoke mouseup handler programmatically
> myMouseupHandler();
>
> Regards,
&
ert("handler invoked programmatically!");
> }
> }
> button1.addListener("mouseup", myMouseupHandler);
>
> //invoke mouseup handler programmatically
> myMouseupHandler();
>
> Regards,
> Andreas
>
> Von: Ken MacDonald [mailto:drken...@gmail
om]
Gesendet: Donnerstag, 24. Dezember 2009 22:01
An: qooxdoo-devel@lists.sourceforge.net
Betreff: Re: [qooxdoo-devel] artificially getting to a listener
Hi Gene,
Still a mystery. I did find an interesting site with a wealth of general info
about the differences between FF and IE in event ha
Hi Gene,
Still a mystery. I did find an interesting site with a wealth of general
info about the differences between FF and IE in event handling, and they
have a javascript package called "Unified Event Model" which attempts some
workarounds to make IE event handling much more Firefox-like, which i
Ken,
Did you ever figure this out yesterday? From trying to find the answer
in the manual, I think some additional knowledge and examples is needed
in the section on events - it's rather concise to the point of not being
helpful. Some examples in the manual would be helpful, as always. On
the o
Thanks Gene,
That gets rid of one bunch of errors. The event's init() method doesn't
document what the array should contain, or if it's even necessary, as it has
a null default - the fireEvent() doesn't toss errors now, but still doesn't
appear to work. the listener for the 'mouseup' event is s
Ken,
Been messing around with this trying to help you sort it out, and in
this case I think you need a third parameter in
qx.eventRegistration.fireEvent() of qx.event.type.Mouse, as the default
third parameter is qx.event.type.Event, per the API.
However, at that point you'll get another error be
Hoping that would do it, but I have been trying to get fireEvent() or
dispatchEvent(), or fireNonBubblingEvent() ... and a dozen other things ...
to work for a couple of weeks now; either they are broken or I'm not
invoking them correctly. Does anyone know how to get fireEvent() to work for
a 'mous
fireEvent?
Cheers,
Fritz
--
Fritz Zaucker
Oetiker+Partner AG
Aarweg 15
CH-4600 Olten
+41 62 755 9903
On 23.12.2009, at 21:51, Ken MacDonald wrote:
> I'm beginning to think that there is no way to do this in qooxdoo:
>
> create a widget
> add a listener to that widget for an event, e.g. "mouseu
I'm beginning to think that there is no way to do this in qooxdoo:
create a widget
add a listener to that widget for an event, e.g. "mouseup"
somehow trigger that listener programmatically instead of physically
clicking the widget with the mouse
var button1 = new qx.ui.form.Button("First Button",
18 matches
Mail list logo
