Bug #2420
Mis à jour par Matthieu Decorde il y a plus de 7 ans
The current property value edition scenario is not well defined: some values may not be saved in some context.
h3. Solution 1
Document exactly e the current scenario.
doc: hit "ENTER" to apply the new value to the current unit/schema property.
doc? hit "TAB" to apply and move to the next field
h3. Solution 2
create a new scenario with other property value validation rules.
List and document the UI rules that apply the new property value: value :
* units navigation:
** the current unit is unselected (see the method that unselect a unit when a new selection is done)
** another unit is selected
*** via click in edition
*** via navigation (first, previous, next, last)
*** via search (first, previous, next, last)
* properties view events
** ENTER key pressed
** * TAB key pressed
** the property view is closed
* TXM events
** window is closed -> end of annotation
** TXM is closed -> end of annotation
h3. Solution 1
Document exactly e the current scenario.
doc: hit "ENTER" to apply the new value to the current unit/schema property.
doc? hit "TAB" to apply and move to the next field
h3. Solution 2
create a new scenario with other property value validation rules.
List and document the UI rules that apply the new property value: value :
* units navigation:
** the current unit is unselected (see the method that unselect a unit when a new selection is done)
** another unit is selected
*** via click in edition
*** via navigation (first, previous, next, last)
*** via search (first, previous, next, last)
* properties view events
** ENTER key pressed
** * TAB key pressed
** the property view is closed
* TXM events
** window is closed -> end of annotation
** TXM is closed -> end of annotation