Well, it's not obvious, I think... In particular, in my daily using of the program, I always clicked <Save> thinking it's "flushing" all changes to the device, and I clicked <Eject> "just in case". So, I had many chances to loose the data (which wasn't happen just because of some luck).
I think <Save> button should make sure nothing will lost (i don't know how; to close all descriptors and to open them again, for example), if I close the gtkpod or eject ipod via Device manager after the Saving. Otherwise, it's useless: why on earth should I click it, if there is more sure way to keep changes applied recommended: Eject. And I still think that Eject should really eject the player as device, just like iTunes does. (with preliminary syncing of the changes, off cause). May be this behavior: 1) "Save" function -- makes sure all data synced to iPod; 2) "Eject" function -- ejects the device . - Clicking <Save> and then Eject -- ejects the player silently; - Clicking <Eject>, without <Saving> -- asks if the changes should be synced or not, or should it cancel ejecting. - Clicking Save and then closing gtkpod -- close with no warnings; changes should stay in iPod after it's ejected via Device notifier or CLI; - Closing gtkpod without Saving -- ask if the changes should be synced or not, or should it cancel closing. Something like that. What you think? -- Gtkpod's built-in Eject function doesn't work https://bugs.launchpad.net/bugs/519167 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
