Community
Participate
Working Groups
Trying to grab a screenshot of a MAC application (bug 44176), we hit a snag with Text widgets which dont paint to the GC. The problem seems to be that Text widgets are painting directly to the screen even when asked to paint to a GC, specifically in Text's api: ------------------------------------------- void drawWidget (int control, int damageRgn, int visibleRgn, int theEvent) { OS.TXNDraw (txnObject, 0); super.drawWidget (control, damageRgn, visibleRgn, theEvent); } ------------------------------------------- Looking at the API of OS.TXNDraw() on Apple's website at http://developer.apple.com/documentation/Carbon/Reference/Multilingual_Text_Engine/mlte_refchap/chapter_1.2_section_19.html#//apple_ref/doc/uid/TP30000069-DontLinkChapterID_2-F12521 It says that specifying NULL or 0 in the second argument paints to the screen instead of the buffer. Was wondering if this was what was causing the text to not paint. An illustration of the problem can be found here: https://bugs.eclipse.org/bugs/attachment.cgi?id=26475 The code used to capture the image: -------------------------------------------- protected Image getImageOfControl(Control control){ Image image = new Image(control.getDisplay(), control.getBounds()); GC gc = new GC(control); gc.copyArea(image, 0, 0); gc.dispose(); return image; } --------------------------------------------
In the unending tide of Mac requests to get a VE up and running (so, amongst other reasons, I can actually work on, review, or even *gasp* look at the projects I assign to my developers)... Can somebody take a look at this? One by one, the community can help kick the problems that prevent VE from running well on the mac out of the way. This is the last remaining hurdle that prevents the *big* blocker of a running SWT/VE on the mac, as far as I can see. Eyeballs on this would be really appreciated. One would do. Even a squint. ;)
We took a quick look at trying to get the TXNObject to draw into the right port and it drew garbage on the screen. We are currently looking at moving to HIView and using the text control, rather than the TXNObject.
This is fixed by changes required for bug#41467.