Bug 417600 - SWT GC does not draw when particular transformations are in use.
Summary: SWT GC does not draw when particular transformations are in use.
Status: RESOLVED INVALID
Alias: None
Product: GEF
Classification: Tools
Component: GEF FX (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: gef-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 253670
Blocks:
  Show dependency tree
 
Reported: 2013-09-19 10:38 EDT by Matthias Wienand CLA
Modified: 2014-08-11 16:29 EDT (History)
1 user (show)

See Also:


Attachments
SWT snippet demonstrating the incorrect behavior. (2.13 KB, text/x-java)
2013-09-19 10:38 EDT, Matthias Wienand CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Wienand CLA 2013-09-19 10:38:16 EDT
Created attachment 235632 [details]
SWT snippet demonstrating the incorrect behavior.

The SWT GC (ostensibly) does not perform drawing operations when particular transformations are in-use, even if the setLineAttributes() workaround is used. The attached snippet demonstrates the incorrect behavior.

For example, the following transformation matrix leads to invisibility of drawings:

    tx.setElements(
        (float) 0.527691627751155, (float) 0.527691627751155,
        (float) -0.527691627751155, (float) 0.527691627751155,
        (float) 15.375719146431834, (float) 247.60611440956703
    );

Whereas this transformation matrix works just fine:

    tx.setElements(
        (float) 0.527691627751155, (float) 0.527691627751155,
        (float) -0.52, (float) 0.527691627751155,
        (float) 15.375719146431834, (float) 247.60611440956703
    );

The only difference (a quite small difference!) between both transformation matrices is found in the first cell of the second row.

This SWT bug is known for a long time. Nonetheless, I want to document it here so that we can find a better workaround (maybe) or at least users can find it more easily.
Comment 1 Alexander Nyßen CLA 2014-08-11 16:28:34 EDT
As we have changed the scope of the SwtFX component, this is no longer an issue. Resolving as INVALID.
Comment 2 Alexander Nyßen CLA 2014-08-11 16:29:19 EDT
Change component to FX, as SwtFX is succeeded by FX.UI.