Font size zooming and PDF (Split pane)

Scrivener Scrivener for macOS
1

Hello,

I’m living in Scrivener (and it’s a good place to reside) and I’ve been using it long enough to spot a few oddities. Tried searching for this one, but couldn’t spot any duplicates.

I’ve found an odd behaviour where Cmd + or Cmd - will and won’t increase and decrease the font size of a selection in the editor when a PDF file is present in the second pane.

To reproduce:

  1. Split your panes.

  2. Normal Scenario:
    Load one or two text items into the panes. Select a word. Cmd + increases the selection’s font size by 1px, Cmd - decreases the selection’s font size by 1px. This behaviour is expected and consistent with TextEdit. (I use it quite frequently.)

  3. Bug scenario:
    Load one text item and one PDF into the panes.

3a. With the PDF active Cmd + and Cmd - zoom the entire PDF. (Expected behaviour)

3b. With the text document active. Select a word. Cmd + and Cmd - still zoom the PDF in the inactive pane. Cmd + and Cmd - can’t be coerced into increasing or decreasing the font size of the selection.

  1. Replace the PDF with a text document. Normal scenario resumes.

This may happen with other types of non text content, but I’ve not tested widely. Jpeg images do not cause the same Cmd + and Cmd - anomaly.

My config:

Scrivener version: 2.0.5.5 (9981)

OS X Version: 10.6.8

Model Name: MacBook Pro
Model Identifier: MacBookPro5,5
Processor Name: Intel Core 2 Duo
Processor Speed: 2.53 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 3 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
Boot ROM Version: MBP55.00AC.B03

2

Hi,

This is a known issue, I’m afraid, and unfortunately it’s out of my hands. I use the standard PDFView from Apple’s PDFKit to display PDF files, and this view somehow intercepts the cmd + and cmd - keyboard shortcuts regardless of whether it is first responder. There’s nothing in Scrivener doing this, it’s just a quirk of PDFKit, and this particular aspect is a black box.

Thanks and all the best,
Keith

3

Ok. Thanks for the swift reply.

If I get a minute I’ll see about an Apple bug report.