Fab!  Thank you. Shame I'm not at home to check it all out until Monday. 
Wait... please immediately port QS for iOS devices!

Sent from MiPhone.
Please excuse brevity or tpyos.

On 28 Jan 2012, at 11:02, Patrick <[email protected]> wrote:

> Thanks everyone for giving us feedback on this, and not letting me
> forget (Guy!)
> 
> I have worked out a fix for the Shelf Module, and will move it over to
> the Clipboard module today as well.
> Expect some new plugins soon.
> 
> Thanks!
> 
> On Jan 27, 12:32 pm, Patrick Robertson <[email protected]>
> wrote:
>> This was to do with an updated shelf plugin that we've released, not with
>> Quicksilver itself. I made an attempt at fixing this in the updated shelf
>> plugin, and thought I had, but I guess not.
>> 
>> I've had a closer look at this and I think I know exactly what you mean by
>> the 'bug', so I'll take another stab at fixing it.
>> 
>> On 27 January 2012 11:05, Guy Manchester <[email protected]> wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> I notice since updating to the β64 pre-release that this behaviour is now
>>> reflected in the Shelf as well as the Clipboard.
>> 
>>> :(
>> 
>>> On 22 Jan 2012, at 14:08, danewb wrote:
>> 
>>>> Simply create a trigger using "Show Clipboard" and "Run" in the second
>>>> pane. Add a keyboard shortcut. Next time you reboot simply use the
>>>> keyboard shortcut to show the clipboard history. After that, you'll
>>>> have your slide-out again.
>> 
>>>> On Jan 11, 3:57 pm, DeanDMX <[email protected]> wrote:
>>>>> Count me in with DrFred and others. Docked to the side was how I used
>>>>> the clipboard window, and now miss having it be there on launch.
>> 
>>>>> On Nov 25 2011, 9:53 pm, DrFred <[email protected]> wrote:
>> 
>>>>>>> I removed some code that made the window stay visible if it was
>>> visible
>>>>>>> when QS quit last time.
>> 
>>>>>> Add me to the list of those who used, and appreciated, the "mouse
>>>>>> pointer against a screen edge" to bring out the clipboard window. Not
>>>>>> that a CMD-L is all that difficult to invoke, but I'd be all for the
>>>>>> functionality being returned if it can be done without breaking
>>>>>> something else. FW.

Reply via email to