Scrolling bug?

[ngazidja]

I'm the proud owner of a new MacBook Pro (no, 10.5.8, a few days too early...) and have installed a new download of pro 1.3 (so it's clean, at least in theory) and find that when I click in the scroll bar between the locator "blob" and the bottom arrow, the screen rapidly scrolls down (as expected) but when I place it above the locator either nothing happens or ... it scrolls DOWN again! (I haven't yet worked out whether there's something that determines whether it moves or not.)

A bug? Or am I using my Mac upside down...?

Iain.

[martin]

Hi Iain- this is a problem we've not seen before and definitely can't reproduce. Does it continue to be an issue for you? If so, can you please submit a feedback report using the menu Help > Send Feedback after the problem occurs? Thanks.

[ngazidja]

Got it again, although not quite so extreme. A different document, when I click and hold below the "gumdrop", the text rapidly scrolls down t the arrow, but when I click and hold _above_ the gumdrop, it doesn't move. Ok, that's a slight improvement, but still a bug, no? It doesn't happen in all my Nisus documents, but I have a couple here in which it does.

Iain.

[ngazidja]

I just thought I'd mention that I'm still having this problem (in NWP 2.0.2 now), occasionally and apparently arbitrarily. I'm experimenting on an open file, sometimes it's fine, sometimes when I click and hold the text scrolls in the opposite direction. There seems to be no logic to it, I've done nothing to the document, I'm just scrolling up and down, now it works, now it doesn't...

[martin]

Hi again Iain- I'm sorry you've had to live with this annoyance on/off for several years! It sounds like it's too inconsistent to reproduce reliably, which is a pity, as that's the best way to ensure we can fix a problem. If you do ever discover any patterns or triggers, that would help immensely.

All the same, would you be able to send in a feedback report (using the Help menu) after the problem happens again? If you could send a copy of your document and a screenshot with the report that would help, so I can try and muck around in your document and somehow trigger the problem. Thanks!