Re: [rkward-devel] Some usability suggestions

2009-09-11 Thread Germán Márquez Mejía
Hi, El Vie 11 Sep 2009 09:55:44 Thomas Friedrichsmeier escribió: > if you're interested: The "real" issue is in rbackend/rthread.cpp, function > checkNotifyOutputTouched(). We detect modifications simply by comparing the > timestamp, but that is only accurate to one second (on most systems). So, >

Re: [rkward-devel] Some usability suggestions

2009-09-11 Thread Thomas Friedrichsmeier
Hi, On Thursday 10 September 2009, Germán Márquez Mejía wrote: > El Mié 09 Sep 2009 06:30:22 Thomas Friedrichsmeier escribió: > > Good catch. The "real" issue is that the whole mechanism of detecting new > > output is somewhat broken. But this is a neat solution for the most > > important symptom.

Re: [rkward-devel] Some usability suggestions

2009-09-10 Thread Prasenjit Kapat
2009/9/10 Germán Márquez Mejía : > El Jue 10 Sep 2009 11:52:10 Prasenjit Kapat escribió: >> No objections! May be a checkbox in Settings ("near" the lines of >> code) whether to show/hide the code by default. > > There is such a checkbox. The modification would be to uncheck it by default. Ah, my

Re: [rkward-devel] Some usability suggestions

2009-09-10 Thread Germán Márquez Mejía
El Jue 10 Sep 2009 11:52:10 Prasenjit Kapat escribió: > No objections! May be a checkbox in Settings ("near" the lines of > code) whether to show/hide the code by default. There is such a checkbox. The modification would be to uncheck it by default. Regards, -- Mancho -

Re: [rkward-devel] Some usability suggestions

2009-09-10 Thread Prasenjit Kapat
On Wed, Sep 9, 2009 at 7:30 AM, Thomas Friedrichsmeier wrote: >> 2. The second suggestion is not to show the code by default. This is more >> personal taste, but I prefer clicking to see the code when I really want >> to. Besides, the default height of the code widget (40 pixels) looks so >> narro

Re: [rkward-devel] Some usability suggestions

2009-09-10 Thread Germán Márquez Mejía
Hi, El Mié 09 Sep 2009 06:30:22 Thomas Friedrichsmeier escribió: > Still, in *some* situations I find it useful to keep the dialog open. E.g. > when running a test with a bunch of objects one after another. So instead > of closing the dialog unconditionally, I've added a checkbox "Auto close" > (c

Re: [rkward-devel] Some usability suggestions

2009-09-09 Thread Thomas Friedrichsmeier
Hi, On Wednesday 09 September 2009, Germán Márquez Mejía wrote: > 1. Given that we now have a useful "Run again" link in the HTML output, I > wondered whether the plugin window remaining open after clicking OK is > still necessary since there's no more risk of losing your settings (as long > as yo