# R for Windows will not send your bug report automatically.
# Please copy the bug report (after finishing it) to
# your favorite email program and send it to
#
# [EMAIL PROTECTED]
#
##
> help.search("normal probability plot")
No help files
A bug has been fixed that basically broke the use of setIs() to define
explicit inheritance with coerce= and replace= methods.
For inherited methods to work in this case, the argument(s) need to be
coerced by as() to the defined class in the signature. This was not
being done, meaning that an
Hi Michael,
Michael Lawrence wrote:
>>> For processing events, RGtk2 has moved away from using the old tcl_do
hack
>>> and now synchronizes on the Windows event loop. In Rgui.exe this works
>>> fine
>>> (well mostly), but in Rterm.exe, users report the following warning from
>>> GLib: "main loop a
On Thu, Sep 18, 2008 at 6:28 AM, Duncan Murdoch <[EMAIL PROTECTED]>wrote:
> On 18/09/2008 8:59 AM, Michael Lawrence wrote:
>
>> For processing events, RGtk2 has moved away from using the old tcl_do hack
>> and now synchronizes on the Windows event loop. In Rgui.exe this works
>> fine
>> (well most
On 18/09/2008 8:59 AM, Michael Lawrence wrote:
For processing events, RGtk2 has moved away from using the old tcl_do hack
and now synchronizes on the Windows event loop. In Rgui.exe this works fine
(well mostly), but in Rterm.exe, users report the following warning from
GLib: "main loop already a
For processing events, RGtk2 has moved away from using the old tcl_do hack
and now synchronizes on the Windows event loop. In Rgui.exe this works fine
(well mostly), but in Rterm.exe, users report the following warning from
GLib: "main loop already active in another thread". The most obvious way
th
