2011/9/8 Guilhem Bonnefille <guilhem.bonnefi...@gmail.com>: > 2011/9/8 Robert Norris <rw_nor...@hotmail.com>: >> >> A. It is slightly annoying one may specify the 'file type' twice (especially >> when it's a choice of over 150 kinds!) >> >> i.e. One goes into file selection dialog, chooses a filter, then picks a >> file. >> But then need to set the file type to be used in our Import File dialog. >> Or vice versa - set a file type but then is not used as the filter when >> actually picking a file. >> >> Obviously files can be called anything and have any file type - which we >> have to tell gpsbabel. >> >> It might be better to order the Import File dialog like this: >> 1. File Type >> 2. Filename Selection >> 3. Track/Route/Waypoint options >> >> Then on choosing the file type, this can auto set the default used for the >> file selection. > > One matter: two lists are not simmetrical as some file types does not > have file extension. > > IMHO, if we have to change part of this, we have to implement > something that preset the file type when a file is selected.
Humh... not so easy to implement. I prefer to publish this feature as is (not enought spare time for this topic). >> B. Be wary of the track/route/waypoint options not doing what you think they >> should do! >> >> I thought if I deselected the waypoint or track options and opened a gpx or >> kml file then I would *not* get that type of information. >> This does not seem to be the way GPSBabel works - especially on file >> conversions - or the behaviour is dependent on the file format used. >> >> I think track/route/waypoint options mainly apply to the serial data formats >> not the file conversions. >> >> Some options in order of difficulty: >> 1. Add GUI visible statement that they only work on some file formats (but >> which ones???) >> 2. Remove these track/route/waypoint options >> 3. Perform automatic post processing ourselves to remove the kinds of data >> the user doesn't want. > > Yes, it seems that -t/r/w options do not already work the same way for > all file type. > > For example, I use these options to convert magellan files to gpx and > gpx to magellan format. I know I need these options to "route" > gpsbabel to the right format to produce, as magellan does not mix > track, route and waypoint in the same file. It seems that the simpler (and so better) solution is to remove these options. The user can remove data later, on TRW layer. So, no need for these GUI option nor command line option. >> C. Importing files this way don't get stored into the recently opened file >> list. [It would be difficult to open them as nothing is stored about what >> type it is - it is possible an auto guess based on filename extension could >> work for some but not all files.]. >> >> I'm OK with not going into the recently opened list. > > Yes, it is currently an "import", not a file openning. Note that we can certainly register a complex GtkRecentData and supporting a new command line option to import a file with a given GPSBabel format. -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
