Bug #2420
Ext: Analec, clarify the annotation property value validation
Status: | New | Start date: | 06/26/2018 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% |
|
Category: | Annotation | Spent time: | - | |
Target version: | TXM Annotation URS 4.0 |
Description
The current property value edition scenario is not well defined: some values may not be saved in some context.
Solution 1¶
Document exactly 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
add: "Apply/Appliquer" button -> do ENTER for all fields
add: "Cancel/Annuler" button -> restore the unit values in fields
show : the "*" dirty state in view title if the values are not yet applied
Solution 2¶
create a new scenario with other property value validation rules.
List and document the UI rules that apply the new property 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
History
#1 Updated by Matthieu Decorde almost 5 years ago
- Subject changed from Ext:Analec, clarify the annotation property value validation to Ext: Analec, clarify the annotation property value validation
- Description updated (diff)
#2 Updated by Matthieu Decorde almost 5 years ago
- Description updated (diff)
#3 Updated by Serge Heiden almost 5 years ago
- Description updated (diff)