Hi,
On Sun, Sep 26, 2010 at 1:46 PM, Thomas Friedrichsmeier
thomas.friedrichsme...@ruhr-uni-bochum.de wrote:
Thus, I am rather reluctant to do this. I would assume that duplicate column
names are a rare exception, and so we can afford not to support them 100%. Do
you think they are important
Hi,
On Thursday 23 September 2010, Stefan Rödiger wrote:
It should be mostly, but not entirely safe to edit such objects. If you
edit a cell in one of the duplicate columns, all columns with the same
name will be affected in the backend. However, in the editor, this will
not become
Am Dienstag 21 September 2010, 16:52:04 schrieb Thomas Friedrichsmeier:
Hi,
On Sunday 19 September 2010, Prasenjit Kapat wrote:
As a caution to the user: Should a warning be displayed when the data
editor encounters multiple columns with same name? Noting that, the
data itself is not
Hi,
On Thu, Sep 16, 2010 at 2:44 PM, Thomas Friedrichsmeier
thomas.friedrichsme...@ruhr-uni-bochum.de wrote:
Hi,
On Thursday 16 September 2010, Stefan Rödiger wrote:
BTW, as you might consent the lines attached in my example are not a good
example how to work with R (size and arrangement of
On Thu, Sep 16, 2010 at 8:22 AM, Stefan Rödiger
stefan_roedi...@gmx.de wrote:
Hi,
I have two files attached. First is called procedure.txt with the
description how to preduce the potential bug. And there is also the gdb
message. I was able to reproduce the crash of RKWard multiple times by
Am Donnerstag 16 September 2010, 17:14:49 schrieb Prasenjit Kapat:
On Thu, Sep 16, 2010 at 8:22 AM, Stefan Rödiger
stefan_roedi...@gmx.de wrote:
Hi,
I have two files attached. First is called procedure.txt with the
description how to preduce the potential bug. And there is also the
Hi,
On Thursday 16 September 2010, Stefan Rödiger wrote:
BTW, as you might consent the lines attached in my example are not a good
example how to work with R (size and arrangement of data ...). Thus it was
really interesting for me to see what happens ... .
I think the crucial thing in your
