The ability to share flags between projects/gedcoms is great (something I was doing manually until very very recently ... i.e. tonight!).
But it would make the sharing of flags simpler if FH provided a dialogue that permitted multiple flags to be set to 'shared' in one go, rather than having to go into each flag, and then a further dialogue, individually.
Also, the [drop-down] list of flags should show the status of the each flag in the list; at present to query whether a flag is shared or not one has to go into each flag individually, then into another dialogue ...
Rather tedious.[bounce]
http://www.fhug.org.uk/wishlist/wldispl ... lwlref=459
ID:4499
* Improve Flag-sharing dialogue
-
GladToBeGrey
- Famous
- Posts: 115
- Joined: 26 Oct 2004 09:16
- Family Historian: V7
- Location: Dorset, UK
Improve Flag-sharing dialogue
A good example of how a multiple checkboxes can be changed with one click is Hotmail (there are other web based email systems available).
The system that hotmail and other use could also be used in FH for the layout of the flags. Just replace emails with flags.
The system that hotmail and other use could also be used in FH for the layout of the flags. Just replace emails with flags.
-
GladToBeGrey
- Famous
- Posts: 115
- Joined: 26 Oct 2004 09:16
- Family Historian: V7
- Location: Dorset, UK
Improve Flag-sharing dialogue
Having played with the dialogue a bit further I'd also like to see the ability to define new shared flags in this dialogue.
That would be very useful, for example, when setting up a new FH environment; one could then predefine all the standard shared flags in one dialogue even before any FH data had been recorded.
I could do this before (and still could now, I suppose) by manually editing flags.fha .... or copying flags.fha from an environment that had previously been established. But that rather takes me back to where I started.
That would be very useful, for example, when setting up a new FH environment; one could then predefine all the standard shared flags in one dialogue even before any FH data had been recorded.
I could do this before (and still could now, I suppose) by manually editing flags.fha .... or copying flags.fha from an environment that had previously been established. But that rather takes me back to where I started.