Hi,
On Friday 06 August 2010, Stefan Rödiger wrote:
> Scenario II: Object is open for editing ("my.data") in fresh started
> RKWard 1. Create objects
> 2. Invoke the plugin
> 3. confirm to remove and do so
> 4. Push "accidentally" "no" when asked "Das Objekt 'meine.daten' wurde vom
> Workspace en
hi,
am Donnerstag 05 August 2010 (09:21) schrieb Thomas Friedrichsmeier:
> well, I am somewhat curious as to the use-case for this.
funny, i've just used it myself to fix the inconsistent Wald test results
(some got NaNs, others sane numbers) in the IRT plugin ;-) i've discussed this
issue with
Am Donnerstag 05 August 2010, 09:21:15 schrieb Thomas Friedrichsmeier:
> Hi,
>
Hi
> On Wednesday 04 August 2010, Stefan Rödiger wrote:
> > Thanks, that (remove a toplevel object) was what I did and it lead to
> > occasional crashes of RKWard (well at least all objects were removed ;)
> > ). That'
Hi,
On Wednesday 04 August 2010, Stefan Rödiger wrote:
> Thanks, that (remove a toplevel object) was what I did and it lead to
> occasional crashes of RKWard (well at least all objects were removed ;) ).
> That's why assumed to do something "harmful" and "not intended by the
> developer". I'll kee
Am Mittwoch 04 August 2010, 21:54:23 schrieb Thomas Friedrichsmeier:
> Hi,
>
> On Wednesday 04 August 2010, Stefan Rödiger wrote:
> > how do I escape local (from a plugin) in order to remove objects from
> > .GlobalEnv?
>
> simply by using .GlobalEnv ;-).
sounds like a good idea, ;)
> To remove
Hi,
On Wednesday 04 August 2010, Stefan Rödiger wrote:
> how do I escape local (from a plugin) in order to remove objects from
> .GlobalEnv?
simply by using .GlobalEnv ;-). To remove a member of a list / data.frame in
.GlobalEnv:
.GlobalEnv$my.list[["object"]] <- NULL
To remove a topleve
Hi,
how do I escape local (from a plugin) in order to remove objects from
.GlobalEnv? I know this might be a harmful thing to do and was intended to be
pavemented in plugins (to be precise overwriting of objects with the same
names should be prevented).
Regards
Stefan
-
