Merge/Delete Dialog

[KenF]

The new
 Added option to load additional GPX/TCX files into “Merge/Delete Downloaded
  Tracks dialog.  Defaults to “Archive” or “History” dir, depending on GPS
feature will be very useful. In fact I already took advantage of it to recover some data from an "archive" file.

But the l-o-n-g  list of track segments that now appears reminds me of a detail that I have always found a bit frustrating. After using the "merge selected" function, the "selected" track defaults to the first track in the list. It would be oh-so-much-nicer if the newly created track remained "selected" after the  merge operation.

KF 

[ScottMorris]

Agree 100%.  That annoys me, especially now with the archive function.

[ScottMorris]

Beta 3.961 out with this change.  I'm already loving it!

[KenF]

Beta 3.961 out with this change.  I'm already loving it!

Thanks!
Now let me add a related request on the issue of "selected file."

If a file is selected by right clicking from the "loaded file" window and then "Analysis" is chosen from the resulting "right-click" menu, the selected file becomes the default as shown in the "file for analysis" box.  This makes perfect sense.

If, however, a file is already selected in the  "loaded file" window and  "Analysis" is chosen on the top menu bar, the default in the "file for analysis" box becomes the first file shown in the "loaded files" window rather than the selected file. This is not consistent with the behavior described above and often has me "selecting" a file, clicking analysis on the top menu and then having to reselect the file.   

Could you make them behave the same way? (please?)

KF
 
 

[ScottMorris]

I'd never thought about that.  Seems reasonable enough, though multiple files can be selected, in which case it should... just have the first one selected come up?

[KenF]

I'd never thought about that.  Seems reasonable enough, though multiple files can be selected, in which case it should... just have the first one selected come up?

That's what I would like to see. Or simply default to the "selected" file if there is only one. 
Simply because I have found myself, more than once, "analyzing" a file I had not intended because I thought I had already "selected" the one I wanted. Since this is only an issue of determining the "default" selection I expect that this will not impede "selection" of a file from the "analysis" menu.

KF     


     

[KenF]

If a file is selected by right clicking from the "loaded file" window and then "Analysis" is chosen from the resulting "right-click" menu, the selected file becomes the default as shown in the "file for analysis" box.  This makes perfect sense.

If, however, a file is already selected in the  "loaded file" window and  "Analysis" is chosen on the top menu bar, the default in the "file for analysis" box becomes the first file shown in the "loaded files" window rather than the selected file. This is not consistent with the behavior described above and often has me "selecting" a file, clicking analysis on the top menu and then having to reselect the file.   

Could you make them behave the same way? (please?)

This continues to drive me absolutely batty.
It has to do with order of operations. If I have already selected a file, it should be simple to then select what I want to do with it. Conversely, if I decide and select a particular "analysis" that I want to perform,  I should then be able to choose the file. 
A huge frustration lies in selecting a file, then selecting an "analysis," only to find that the file must then be selected AGAIN.

KenF

[ScottMorris]

Right, I see your point.  For now, right click on the file, then do Analysis and choose the one you want.  That'll make sure it is selected right off.

Thanks for the feedback.

[KenF]

Right, I see your point.  For now, right click on the file, ...

Yes, my point was essentially that while there may be A way of accomplishing a task, the IDEAL user interface does not place the burden on the user of knowing the "secret handshake" method and instead operates so it is more "intuitive," to that user.
But you knew that.
And I have done enough programming where I am the sole "user" to realize that, despite being simple in concept, implementing every feature is not without it problems.
KenF