-Dprism.dirtyopts

[Richard Bair]

Also worth noting is that prism.dirtyops is not API -- it really only existed to help people analyze whether graphical glitches with it turned on would disappear when turned off -- ironic that it is failing in the opposite manner :-). 

There is really only one other reason I know of to use this flag, and that is the overhead of computing dirty ops is significant in your app and unnecessary. If that is the case we ought to analyze the use case to see if we can lower the cost of dirty ops, or provide a public API for disabling it.

On Feb 26, 2013, at 7:14 AM, Martin Sladecek <martin.sladecek at oracle.com> wrote:

> A major optimization has been done recently in dirty region area (http://javafx-jira.kenai.com/browse/RT-16006) which affects all Parent objects that have some effect on them. You can try to remove effects from some/all Parent (Group/Region) objects and see if it gets better.
> 
> Hope it helps you to narrow down the problem to some simple test-case. Otherwise, try to find some reproducible scenario in your application. In any case, don't forget to file this into JIRA ;-)
> 
> Thanks,
> -Martin
> 
> On 26.2.2013 14:56, Pedro Duque Vieira wrote:
>> Hi,
>> 
>> If I run my app without this flag:"-Dprism.dirtyopts=false" a lot of
>> graphical glitches start to appear. This problem seems to be getting worse
>> from version to version.
>> 
>> I don't know what causes this problem, so I have no way of submitting a
>> small test case to showcase this issue, the best I can do is provide my app
>> for testing and help out by answering any question the javafx team may have.
>> 
>> Cheers,
>