| Summary: | Once a Sash is moved to certain limit, it cannot be moved anymore | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Albert <albert.pikus> |
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | laurent.redor, lshanmug, skovatch |
| Version: | 4.1 | Keywords: | triaged |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | stalebug | ||
|
Description
Albert
Is this Cocoa or Carbon? If it's Cocoa we'll have a look -- Carbon is not being updated for 3.7. This issue affects SWT cocoa 3.6. The problem seems to be that the sash's NSView is getting buried behind the other Composites in the SashForm. When the Sash is resized the relayout is putting the Composites above the Sash. I'll hold on to this and see what I can do; there's a comment in Sash that we should use sendMouseEvent, which makes sense because we're relying on mouseDragged, and that won't be called unless the view is top-most. Bug triaged, visit https://wiki.eclipse.org/SWT/Devel/Triage for more information. 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. |