XYplorer Beta Club
Moving between projects, I use many tabsets. I have configured the header line of the program to display the names of the tabsets in use, but moving to a new project, forgetting to do "save as" before starting to modify the content, and then doing Save, obviously ruins the previous tabset.
If the "Save" button under the Tabsets menu could just ask for confirmation before overwriting, it would be great.
Other than that: great product.
Tab sets too easy to mess up
-
admin
- Site Admin
- Posts: 60602
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Tab sets too easy to mess up
I don't use tabsets myself, and IMO somebody who actually uses them should comment this...
FAQ | XY News RSS | XY Twitter
Re: Tab sets too easy to mess up
I've occasionally run into similar rough edges here.
One thing I've been curious about but have not tested is whether XY obeys the read only attribute, and if this could be used to protect tab sets.
To be honest, I don't feel like the current tab sets feature matches the manner I want to use them but I have not been able to take the time (or been willing) to document the differences and make constructive criticisms.
One thing I've been curious about but have not tested is whether XY obeys the read only attribute, and if this could be used to protect tab sets.
To be honest, I don't feel like the current tab sets feature matches the manner I want to use them but I have not been able to take the time (or been willing) to document the differences and make constructive criticisms.