Bug 543485 - SWT.MAX and SWT.RESIZE not working in Mac Mojave
Summary: SWT.MAX and SWT.RESIZE not working in Mac Mojave
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.10   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2019-01-16 00:10 EST by Aakash Mishra CLA
Modified: 2021-05-31 12:27 EDT (History)
2 users (show)

See Also:

Attachments
Screenshots of the application (337.31 KB, application/zip)
2019-01-16 00:10 EST, Aakash Mishra CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Aakash Mishra CLA 2019-01-16 00:10:18 EST 
Created attachment 277163 [details]
Screenshots of the application

Hi Team,
In MacOs Mojave with SWT 4.10M3 the below piece of code which was working fine until High Sierra is not working -

public AbstractDialog(Shell parentShell) 
{
  super(parentShell);
  setShellStyle(SWT.MAX | SWT.MIN | SWT.CLOSE | SWT.RESIZE);
}

This the main Dialog class inherited by all our JFace Dialogs in the application.
SWT.MAX and SWT.RESIZE is unable to adjust the positions of widgets when the screen is maximized/resized and all widgets are misaligned.
Is there any alternative to handle positions of widgets when the screen is resized apart from the one mentioned? 
Attached screenshots depicting the issue.

Thanks,
Aakash
Comment 1 Lakshmi P Shanmugam CLA 2019-03-12 04:55:02 EDT 
Can you pls provide a test-case or snippet to reproduce the problem?
Comment 2 Lakshmi P Shanmugam CLA 2019-06-10 02:21:02 EDT 
(In reply to Lakshmi Shanmugam from comment #1)
> Can you pls provide a test-case or snippet to reproduce the problem?

ping!
Comment 3 Eclipse Genie CLA 2021-05-31 12:27:14 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.