11-07-2006 10:35 AM
11-07-2006 10:42 AM
11-08-2006 11:45 AM
I've never played around with Picture controls much, so I didn't realize (until now) that it consisted only of instructions for building an image rather than a buffered copy of the image itself. So I am guessing that the rendering into a raster image is happening in the UI thread? There doesn't seem to be any way to programatically render the instructions contained in the Picture wire itself. I'm guessing you could have achieved the same by using Picture to Pixmap and then Draw Flattened Pixmap to convert the raster image back to a Picture? I'm not sure if that would have had a bigger performance hit than turning off asynchronous display, however.
Darren wrote:So in my case, I was drawing different components of a Picture Control, with the "Erase First" option deselected...this means that new images are drawn "over" old images, and the old images remain in the Picture Control. Well, if two draws happened in quick succession (which was possible since I was keying off of Mouse Move events to do some of my drawing), sometimes, the first draw would never happen, due to the Asynchronous Display behavior. As a result, portions of my picture that needed to be there from the first draw would never appear.
11-10-2006 05:59 PM
@Aristos Queue wrote:
This was reported to R&D (# 43699OJ1) for further investigation.
11-10-2006 06:12 PM
11-10-2006 06:57 PM
@Aristos Queue wrote:
The plan is that when a bug fix or upgrade is released that the public
forums of DevZone and LAVA will be searched for the key phrase (which
is why I have such exact wording). We'll check those CAR numbers and
post to the forums that the CAR has been fixed. This is all supposed to
be automated if possible.
This is something new that we're trying for the first time to try to
improve the feedback to customers. We'll see how it goes next release.
11-11-2006 11:21 AM