mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

Public bug reported:

For example, you have a group with triggers called 1, 2, and 3, all of
which are stacked as children of each other. So:

1
..2
....3

Now take 3, and drag it into 1. 3 will become a child of 1, however, 2
will be selected (while 3 should be), and the trigger name is still left
as "3" - so now if you press save, you overwrite the data in trigger 2.

I think just properly selecting the proper trigger after dnd would fix
this.

** Affects: mudlet
     Importance: Medium
         Status: Confirmed


** Tags: beta-pre-1

** Changed in: mudlet
   Importance: Undecided => Medium
       Status: New => Confirmed

** Tags added: beta-pre-1

-- 
When you drag an item onto another one, item settings aren't updated
https://bugs.launchpad.net/bugs/327036
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.

Status in Mudlet the MUD client: Confirmed

Bug description:
For example, you have a group with triggers called 1, 2, and 3, all of which are stacked as children of each other. So:

1
..2
....3

Now take 3, and drag it into 1. 3 will become a child of 1, however, 2 will be selected (while 3 should be), and the trigger name is still left as "3" - so now if you press save, you overwrite the data in trigger 2.

I think just properly selecting the proper trigger after dnd would fix this.