You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
An expandable composite located within another composite, resp. e4 view, does not get its paint function called on Mac.
This however works on Windows - please have a look at the recordings in the original bug to explain.
To Reproduce
Please have a look at the recordings in the original bug report.
Expected behavior
Both in Windows (where its correct) and on Mac, a scroll event should lead to a call of the paint method in its children.
Screenshots
Please see original bug report.
Environment:
Select the platform(s) on which the behavior is seen:
[] All OS
Windows
Linux
macOS
Additional OS info (e.g. OS version, Linux Desktop, etc)
macos big sur 11.7
JRE/JDK version
Java 17
Version since
Bug report is done using SWT 3.120.0, but a limited test show this already occuring at 3.114.0
Workaround (or) Additional context
The text was updated successfully, but these errors were encountered:
In elexis/elexis-3-core@0cf8545 we did kind of a workaround. By registering with the viewparts scrollbar to catch scroll events, and collect and dispatch them ever 250ms. This is not optimal, but it works for our application.
Describe the bug
The issue is originally described in https://bugs.eclipse.org/bugs/show_bug.cgi?id=580825
An expandable composite located within another composite, resp. e4 view, does not get its paint function called on Mac.
This however works on Windows - please have a look at the recordings in the original bug to explain.
To Reproduce
Please have a look at the recordings in the original bug report.
Expected behavior
Both in Windows (where its correct) and on Mac, a scroll event should lead to a call of the paint method in its children.
Screenshots
Please see original bug report.
Environment:
Additional OS info (e.g. OS version, Linux Desktop, etc)
macos big sur 11.7
JRE/JDK version
Java 17
Version since
Bug report is done using SWT 3.120.0, but a limited test show this already occuring at 3.114.0
Workaround (or) Additional context
The text was updated successfully, but these errors were encountered: