Dave Page a écrit :
On Tue, Jun 17, 2008 at 8:59 AM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
That can be
potentially dangerous if the user has another property dialogue for a
sibling object open though (actually that's an issue now iirc - this
would just make it far more likely to occur).
On Tue, Jun 17, 2008 at 8:59 AM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
>> That can be
>> potentially dangerous if the user has another property dialogue for a
>> sibling object open though (actually that's an issue now iirc - this
>> would just make it far more likely to occur).
>>
>
> What
Dave Page a écrit :
On Mon, Jun 16, 2008 at 11:07 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
OK, this works on my local branch but I still have one issue with it: if the
user change the name of a newly created object in the SQL text field, the
treeview will display the name available in th
On Mon, Jun 16, 2008 at 11:07 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
>
> OK, this works on my local branch but I still have one issue with it: if the
> user change the name of a newly created object in the SQL text field, the
> treeview will display the name available in the name field, n
