Was there any progress on allowing default entries to be editable? It's a blocker for the Chrome plugin to support multiple profiles - Trouble with Multiple Chrome Users (Profiles) · Issue #16 · quicksilver/GoogleChrome-qsplugin <https://github.com/quicksilver/GoogleChrome-qsplugin/issues/16>
Thanks, dave On Wednesday, May 1, 2013 at 7:56:45 AM UTC-7, Rob McBroom wrote: > > On May 1, 2013, at 10:32 AM, Patrick Robertson <[email protected] > <javascript:>> wrote: > > I completely agree. I recently looked at making it more obvious for users > on how to create a copy (to adjust the settings) but allowing modification > of the presets would be an even better step. I can't quite remember right > now, but perhaps this is difficult with the current architecture and hence > can't be implemented easily... but perhaps not. I'll look at it > > > I was thinking the same thing. I can’t think of a reason for the > restriction off the top of my head. I know the Catalog.plist at the moment > stores your custom entries in detail, but for the presets, it just lists > the ID. I don’t see why it couldn’t just list them all in detail. It works > for triggers. The only problem I can think of is that these things don’t go > away if the supporting plug-in is removed. > > -- > Rob McBroom > <http://www.skurfer.com/> > > -- You received this message because you are subscribed to the Google Groups "Quicksilver" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/blacktree-quicksilver. For more options, visit https://groups.google.com/d/optout.
