Shift / Click - Is this by design, an omission or a bug in Search Panel and Factbook?

Donovan R. Palmer
Donovan R. Palmer Member, MVP Posts: 2,768
edited 3:36PM in English Forum

So, I took on some new study work this week and developed some of my layouts and workflows. One thing I noticed is that the function of shift/click behaves differently in different parts of the programme.

My use case is that I am quickly sifting through resources to pull together for further investigation. 

So, if I am in one of the Guides, I might find something that interests me, so I 'shift-click' on the link, and a floating window appears with the resource. Visually, this brings it to the foreground and makes it easier for me to scan. I will dock the tab to my workspace using the keyboard shortcut if I want to keep it. If I want to move on, I will close the floating using the keyboard shortcut (or the mouse in either case). I can use this to move through many resources quickly as I scan and speed-read.

The trouble is, when I am in the Search Panel, if I click command shift on a link, the resource is opened as a dock tab. This is the default behaviour if I just click. I don’t use Factbook much in this workflow, but testing it yielded the same behaviour.

Is there an absence of ‘shift-click’ in the Search Panel and Factbook by design, or is there an omission or regression?  It would be nice if this were a universal behaviour throughout the software.

Tagged:

Comments

  • Donovan R. Palmer
    Donovan R. Palmer Member, MVP Posts: 2,768

    So, I took on some new study work this week and developed some of my layouts and workflows. One thing I noticed is that the function of shift/click behaves differently in different parts of the programme.

    My use case is that I am quickly sifting through resources to pull together for further investigation. 

    So, if I am in one of the Guides, I might find something that interests me, so I 'shift-click' on the link, and a floating window appears with the resource. Visually, this brings it to the foreground and makes it easier for me to scan. I will dock the tab to my workspace using the keyboard shortcut if I want to keep it. If I want to move on, I will close the floating using the keyboard shortcut (or the mouse in either case). I can use this to move through many resources quickly as I scan and speed-read.

    The trouble is, when I am in the Search Panel, if I click command shift on a link, the resource is opened as a dock tab. This is the default behaviour if I just click. I don’t use Factbook much in this workflow, but testing it yielded the same behaviour.

    Is there an absence of ‘shift-click’ in the Search Panel and Factbook by design, or is there an omission or regression?  It would be nice if this were a universal behaviour throughout the software.

  • Donovan R. Palmer
    Donovan R. Palmer Member, MVP Posts: 2,768

    So, I took on some new study work this week and developed some of my layouts and workflows. One thing I noticed is that the function of shift/click behaves differently in different parts of the programme.

    My use case is that I am quickly sifting through resources to pull together for further investigation. 

    So, if I am in one of the Guides, I might find something that interests me, so I 'shift-click' on the link, and a floating window appears with the resource. Visually, this brings it to the foreground and makes it easier for me to scan. I will dock the tab to my workspace using the keyboard shortcut if I want to keep it. If I want to move on, I will close the floating using the keyboard shortcut (or the mouse in either case). I can use this to move through many resources quickly as I scan and speed-read.

    The trouble is, when I am in the Search Panel, if I click command shift on a link, the resource is opened as a dock tab. This is the default behaviour if I just click. I don’t use Factbook much in this workflow, but testing it yielded the same behaviour.

    Is there an absence of ‘shift-click’ in the Search Panel and Factbook by design, or is there an omission or regression?  It would be nice if this were a universal behaviour throughout the software.