Ticket #1015 (closed defect: worksforme)
Using the mouse's scroll wheel on the script area crashes on OS X
| Reported by: | precurejunkie | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.1.9 |
| Component: | Interface | Version: | devel |
| Severity: | block | Keywords: | |
| Cc: | Platform: | OS X | |
| Sub Component: |
Description (last modified by nielsm) (diff)
steps to reproduce:
- Move mouse over the script area at the bottom of the window.
- Move the scroll wheel on the mouse.
- Crash.
Can reproduce every time, whether or not there is anything there to scroll through.
Dragging the scrollbar works fine, however.
Attachments
-
aegisub-crashlog.txt
(84.4 KB) -
added by precurejunkie 2 years ago.
- crash log
Change History
Changed 2 years ago by precurejunkie
-
attachment
aegisub-crashlog.txt
added
comment:4 Changed 2 years ago by nielsm
- Description modified (diff)
- Milestone set to 2.1.8
We need to confirm whether this happens on 2.1.8 on Mac.
comment:5 Changed 2 years ago by verm
- Status changed from new to closed
- Resolution set to invalid
- Milestone 2.1.8 deleted
Doesn't happen anymore.
comment:6 Changed 2 years ago by precurejunkie
still happens in aegisub-Darwin-x86_64-kokoro-386-r3901, not sure if you care since that's not 2.1.8.
comment:7 Changed 2 years ago by nielsm
When you scroll, where is the keyboard focus?
Do you have audio open?
Do you have video open?
comment:8 Changed 2 years ago by precurejunkie
When I tested this just now, I launched the app, did not load anything, just moved the mouse pointer overtop of the script area, and moved the scrollwheel. So wherever the keyboard focus defaults to when you launch the app.
But I've previously run into it with scripts loaded and with the focus in both the edit box above and in the script area (on OS X, the scroll wheel affects the scroll region the mouse is pointing at, not the one with focus)
comment:9 Changed 2 years ago by verm
- Status changed from closed to reopened
- Resolution invalid deleted
I tried again it still works, setting to milestone:2.2.0 thanks for letting us know.
comment:10 Changed 2 years ago by precurejunkie
This still happens in the release version of 2.1.8.
comment:11 Changed 16 months ago by Rarok
In 2.1.8 using MacOs X intel 10.6 happens
comment:12 Changed 16 months ago by verm
- Component changed from General to Interface
- Severity changed from minor to block
- Milestone set to 2.1.9
Scheduling this to be looked at before 2.1.9 thank you for the report(s)
comment:13 Changed 4 months ago by nielsm
- Status changed from reopened to closed
- Resolution set to worksforme
This seems to have resolved itself somehow. Can't reproduce it any longer.
crash log