Hi Ingmar,
funnily enough I didn't come across this issue up until I rebuilt MITK
several times (for different reasons) - and only in the last of these
builds this problem appeared.
Are you building with Qt5? If yes, I solved this issue by modifying
QmitkRenderWindowMenu. Apparently there was some bug with showing/hiding
it in Mac or Win environments and instead setWindowOpacity was used.
When I removed all || defined(_WIN32) this bug
http://bugs.mitk.org/show_bug.cgi?id=12130 comes back, but the
flickering is gone.
Basically it would also be nice to have that bug still fixed. The
problem there is that when a widget of type Qt::Tool is shown, the
raise() method is called which leads to the whole window (probably
propagated through parent-child relationship) is raised. To overcome
this, I used a different approach - initialize the widget with parent
set to NULL and saving the parent widget in a separate variable for
positioning. To avoid mem leak, connecting destroyed() signal of parent
object to deleteLater() slot of the menu object helps :)
You can find the patch in the new comment to the bug
http://bugs.mitk.org/show_bug.cgi?id=12130.
Rostislav.
On 19/12/2014 11:57, Ingmar Wegner wrote:
Hi Users-List,
I am working on migrating to v2014.10.0.
I discovered a flickering in the render widgets of the mitkWorkbench
when exiting a widget.
To reproduce: In MitkWokbench load a surface into the DataStorage.
With the mouse circle over the inner corners of the 4 widgets view.
When the mouse exits the area of one widget the background of the
widget changes temporarily to white and thus causes a flickering.
I verified the bug in a superbuild of the release and in the installer
from the mitk.org homepage. It occurs in both.
But in the current truck (19.12.) the flickering is fixed, so I don't
consider it to be a local driver problem on my machine.
Did anybody else observe this bug?
I could not find a corresponding bug report since the release. Has it
been fixed with modifications of the overlay classes or so?
I would either like to pick the bug fix for an "extended 2014.10.0
release" (https://github.com/iwegner/MITK/tree/v2014.10.0_extended) or
change to a later moment within the trunk that also contains QT5 support.
Is there a recommended commit for such a checkout?
Happy holidays to everyone,
Ingmar
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
