Text mode bug with ⇧⌥→

[1.61803]

It doesn't select text and logs in Console

May 15 17:58:08 Quicksilver[206]: (

0   CoreFoundation                      0x00007fff94c1db06 __exceptionPreprocess + 198

1   libobjc.A.dylib                     0x00007fff8ff633f0 objc_exception_throw + 43

2   CoreFoundation                      0x00007fff94c1d948 +[NSException raise:format:arguments:] + 104

3   Foundation                          0x00007fff8fc00c82 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 189

4   AppKit                              0x00007fff8d8a4745 -[NSEvent isARepeat] + 178

5   QSInterface                         0x0000000100172160 -[QSResultController updateSelectionInfo] + 277

Can anyone reproduce it?

[Rob McBroom]

I can’t. The selection happens as expected. What’s weird is that the error comes from QSResultController, which shouldn’t be active when in text mode. Which interface are you using?

-- 
Rob McBroom
<http://www.skurfer.com/>

[1.61803]

On Thursday, May 16, 2013 4:14:39 PM UTC+2, Rob McBroom wrote:

I can’t. The selection happens as expected. What’s weird is that the error comes from QSResultController, which shouldn’t be active when in text mode. Which interface are you using?

I use Cube interface, but it also happens in default Bezel. QS b4000, OS X 10.8.3 here.

[1.61803]

I realized I have a trigger with hotkey ⇧⌥→ for Quicksilver Selection ⇥ Show Menu Items that should only run when the selection is an application, right?

[Rob McBroom]

On May 16, 2013, at 3:04 PM, 1.61803 <iam...@gmail.com> wrote:

I realized I have a trigger with hotkey ⇧⌥→ for Quicksilver Selection ⇥ Show Menu Items that should only run when the selection is an application, right?

It’ll only work when the selection is an application, but it will run whenever you press the key combination.

When doing things via the normal interface, Quicksilver will check the type of thing in the first pane and only show the appropriate actions for it, but once a trigger is set up, you can run it any time whether it makes sense or not. This is the same principle behind the warning I gave in this second footnote.

In this case, you might want to tell that trigger not to be active in Quicksilver, or you can do this globally for all triggers by turning on “Disable Trigger HotKeys when Quicksilver is focused” in the Extras prefs.

[1.61803]

On Friday, May 17, 2013 3:52:02 PM UTC+2, Rob McBroom wrote:

In this case, you might want to tell that trigger not to be active in Quicksilver, or you can do this globally for all triggers by turning on “Disable Trigger HotKeys when Quicksilver is focused” in the Extras prefs.

I actually enabled it only in QS to right arrow in an application's menu items.

Does QS's code base as is allow to prepend some object checking for triggers? Just curious.

[Rob McBroom]

On May 17, 2013, at 10:40 AM, 1.61803 <iam...@gmail.com> wrote:

> I actually enabled it only in QS to right arrow in an application's menu items.

Oh, duh! Quicksilver Selection. Most people set that up with “Current Application”, which is what I was thinking of. In that case, I think you just have to choose between the trigger, or being able to select by word in text entry mode.

> Does QS's code base as is allow to prepend some object checking for triggers? Just curious.

Not globally. It would probably annoy users since I’m guessing there are some hacks that wouldn’t be possible.

Each individual action can decide what to do with unexpected types of objects. Very few explicitly check types, but they usually act on the data associated with a particular type, so if that type is missing, nothing happens.