[APBeta] List columns "Set to Default"

[Jeff Young]

Paul --

I'd be inclined to go with (b).  For plans that have different sets of user-defined columns, I expect I'd have different column definition templates as well.  So tying a particular template to a particular set of user-defined columns seems fine.

-- Jeff.


> -----Original Message-----
> From: apbeta-bounces at lists.astroplanner.net [mailto:apbeta-bounces at lists.astroplanner.net] On Behalf Of
> Paul Rodman
> Sent: Thursday, July 02, 2009 4:07 PM
> To: AstroPlanner Beta Testers
> Subject: [APBeta] List columns "Set to Default"
> 
> I have now managed to get this feature working (being able to save a
> list column layout as a "template" and automatically applying it to
> new plans, or optionally to existing plans)*. However, this does not
> include any user-defined fields. These will be ignored (i.e. disabled
> until enabled via Edit->List Columns...).
> 
> I am pondering what to do about any user-fields in the "template" that
> are not present in the plan that the template is to act on:
> 
> a. Just ignore them (the current situation).
> b. Automatically create those user fields in the plan if they don't
> exist.
> c. Do (b) but ask the user each time.
> 
> How do you feel about this? (assuming you have any idea what I'm
> rambling on about here).
> 
> Paul R.
> 
> * and in doing so I have fixed some bugs with editing list columns.
> 
> _______________________________________________
> APBeta mailing list
> APBeta at lists.astroplanner.net
> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net