Closed GoogleCodeExporter closed 9 years ago
Original comment by mjc1...@gmail.com
on 2 Apr 2009 at 3:45
To clarify...
Renaming concepts does rename additional concepts in the database.
The problem is that it does not rename additional concepts in the current open
transcript which have not yet been saved.
Also, when returning from the concept manager, we do not refresh the transcript
page
- so any changes to concept names are not immediately seen (workaround is to
reload).
I suggest the following:
1. When the user goes to either the concept or category manager, insist they
save the
transcript (assuming there are unsaved changes
2. When returning from the manager, reload the transcript.
Is this acceptable?
Original comment by mjc1...@gmail.com
on 6 Apr 2009 at 3:32
Fixed in r
Before going to Concept/CategoryManager (via Admin menu), the user is now
prompted
what to do with unsaved changes. After coming out of the manager the session is
reloaded.
This is for safety even though normally a refresh of the view would be enough.
Here are the scenarios:
Category Mgr:
1a) Add: no problem - no need to even refresh the view after closing the manager
1b) Edit: need to refresh the transcript (changes to cat name and concepts,
potentiallt)
1c) Remove: possible that a category is deleted but is still referenced by the
current unsaved session
Concept Mgr:
2a) Add: potentially a problem if an unsaved additional concept normalizes to
same name
2b) Edit: need to refresh transcript after dialog closes
2c) Remove: need to refresh. But also if the concept removed is also an
additional
concept (not yet saved to db) then this concept will reappear when session is
saved.
To make things simple, we just insist the user saves the session before
continuing to
the manager. Closing the manager forces a reload of the session. This is a
little
overkill but OK.
When the user accesses the Category Manager via the Markup Properties Pane, the
remove is disabled. Coming out of this pane refreshes the whole transcript pane.
1. The user deletes a category which has just been assigned to the unsaved
session
2.
Original comment by mjc1...@gmail.com
on 7 Apr 2009 at 5:46
Original comment by mjc1...@gmail.com
on 7 Apr 2009 at 5:50
Original issue reported on code.google.com by
swami.ke...@gmail.com
on 22 Mar 2009 at 3:19