Bug 417901

Description Alex Clayton 2013-09-24 07:36:45 EDT

Created attachment 235746 [details]
Example Code to replicate/demonstrate the bug

Overview:

Running an SWT application on MAC OS X (Mountain Lion 10.8.5 (12F37))

I create an empty Text widget and set its font using the setFont() method. Then a worker/background thread calls Display.asynExec to append text to the Text widget via the append method.  The text appended does NOT have the selected font applied to it.

If however I set the font in the call to Display.asyncExec then the text does have the font applied.

Steps to reproduce:

1) Create a new SWT Text Widget.

...
output = new Text(
            shell,
            SWT.WRAP
              | SWT.MULTI
              | SWT.BORDER
              | SWT.H_SCROLL
              | SWT.V_SCROLL);
        GridData gridData =
          new GridData(SWT.FILL,SWT.FILL,true,true);
        output.setLayoutData(gridData);
        font = JFaceResources.getFont(JFaceResources.TEXT_FONT);
        output.setFont(font);
...

2) In a Worker/Background thread call Display.asyncUpdate to append to text

... (in worker/backgournd thread)
display.asyncExec(new Runnable() { 
                @Override
                public void run() {
                   if (output != null && !output.isDisposed()) {
                       // Commented Out 
                       // font = JFaceResources.getFont(JFaceResources.TEXT_FONT);
                       // output.setFont(font);
                       output.append(outputString); 
                   }  
                }
...

3) The text added to 'output' will not have the selected Font applied to it

4) If the commented out code is uncommented then the font is applied to all the text.

Actual Results:

The appended text does not have the font applied.

Expected Results:

The appended text should have the font applied.

Build Date & Hardware:

Build 2013-09-24 Mac OS X 10.8.5 (12F37)
SWT Version 4.3.32

Additional Builds and Platforms:

I've not seen this happen on other OSes.  Tested code on Fedora did not
see problem replicated there.

Additional Information:

Included example code to replicate the error, and screen shots showing output as attachments.