Um, so what? If I assign an abbreviation to an Artist, clear the first pane, and then try to use that abbreviation to bring up the Artist again, it doesn't work. Why would it be important to make sure that some non-funcationality is not lost?
As far as actually writing the code to add such a feature, you are, of course, entirely right to encourage someone who cares and has the ability to go ahead and do so. I'm simply discussing the logic such code would want to follow. :) On Friday, January 18, 2013 10:08:16 AM UTC-5, Rob McBroom wrote: > > On Jan 17, 2013, at 5:06 PM, Jon Stovell <[email protected] <javascript:>> > wrote: > > If the object is in the catalogue, assign the abbreviation; else if the > object is a file or folder, prompt the user to add it to the catalogue and > (if that was successful) assign the abbreviation; else gently inform the > user that the action failed and exit. > > > That would prevent you from assigning abbreviations to things like > Artists, Albums and anything else that isn’t directly in the catalog. What > would be better is > > * Blindly assign the abbreviation. (current behavior) > * If the item isn’t in the catalog, but *could be*, offer to add an > entry for it. > > I look forward to a pull > request<https://gun.io/blog/how-to-github-fork-branch-and-pull-request/> from > someone who thinks this is important. ;-) > > -- > Rob McBroom > <http://www.skurfer.com/> > > -- You received this message because you are subscribed to the Google Groups "Quicksilver" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/blacktree-quicksilver?hl=en.
