Displaying 5 results from an estimated 5 matches for "do_getgraphicsevents".
Did you mean:
do_getgraphicsevent
2016 Sep 18
0
getGraphicsEvent() and setTimeLimit() bug and compatibility patch.
Hey all.
Setting a time limit with setTimeLimit(), and then using
getGraphicsEvent(), will cause graphics event handling for the current
device to break on timeout, until the device is destroyed and recreated.
The problem lies in do_getGraphicsEvent() checking the value of
dd->gettingEvent and concluding it's being called recursively
(ironically this same test fails to detect actual
2016 Sep 17
2
Handlers in setGraphicsEventHandlers() can recursively call getGraphicsEvent(). Intended behavior?
...y set to TRUE. Which would
suggest recursively calling it is very much not intended to be possible.
To me, setting gettingEvent to FALSE seems like an easy mistake to make
if you temporarily interpret gettingEvent to mean that event(s) are
allowed to still come in. But the actual interpretation in
do_getGraphicsEvents() is the opposite, as it's interpreted as an
indicator of whether or not an event is currently being processed.
I've removed the gettingEvent altering lines from both doMouseEvent()
and doKeybd() to no ill effect, and doing so disabled the ability to
call getGraphicsEvent() from inside one...
2016 Sep 21
1
Handlers in setGraphicsEventHandlers() can recursively call getGraphicsEvent(). Intended behavior?
...ly calling it is very much not intended to be possible.
>>
>> To me, setting gettingEvent to FALSE seems like an easy mistake to make
>> if you temporarily interpret gettingEvent to mean that event(s) are
>> allowed to still come in. But the actual interpretation in
>> do_getGraphicsEvents() is the opposite, as it's interpreted as an
>> indicator of whether or not an event is currently being processed.
>>
>> I've removed the gettingEvent altering lines from both doMouseEvent()
>> and doKeybd() to no ill effect, and doing so disabled the ability to
>...
2016 Sep 21
0
Handlers in setGraphicsEventHandlers() can recursively call getGraphicsEvent(). Intended behavior?
...t; suggest recursively calling it is very much not intended to be possible.
>
> To me, setting gettingEvent to FALSE seems like an easy mistake to make
> if you temporarily interpret gettingEvent to mean that event(s) are
> allowed to still come in. But the actual interpretation in
> do_getGraphicsEvents() is the opposite, as it's interpreted as an
> indicator of whether or not an event is currently being processed.
>
> I've removed the gettingEvent altering lines from both doMouseEvent()
> and doKeybd() to no ill effect, and doing so disabled the ability to
> call getGraphic...
2016 Sep 16
1
getGraphicsEvent() questions, minor feature/tweak request, and patch(es).
Hey all, new R user and first timer here.
I've been using getGraphicsEvent() on an X11-Xlib device in a kind of
interactive loop, and would like to be able to stop it from printing
newlines in the console when I don't actually want to print a prompt.
Even an empty "" value still causes a newline right now.
To not break any code that depends on this behavior, I figured getting