Yes - agreed. Don't yet know how the module can get signals from the toolbar (except by a fragile hack...) But will think about it.

Sorry about the duplicate, looking at the issue names I could not found an obvious instance of this one.

No problem - just wanted to add the link for future reference.

I took another look and I think we can do this by having the module connect to the actionLoadDICOM from the qSlicerAppMainWindow and then raise the browser in response.

Revision http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21777 fixes this issue. The DICOM browser now appears on clicking the DCM buttoneven if the DICOM module is active.
Thank you, Steve!

I discovered a minor problem. When I click on a new patient/study/series in the table, the DICOM browser window jumps back to a default position.

Hi Csaba - good catch - can you try again with r21782? If that's not the fix I may need more info to reproduce. -Steve

I'd say this is all set - Csaba, can you close if you agree?

Unfortunately I still have the same issue on Windows (with r21782). It's as simple to reproduce as to open the DICOM browser, drag it away a bit, then clicking the DCM button again.
If there is anything I can try or do, please let me know!

I saw the fixes in rev21782, so I updated and tried rev21787. Unfortunately the DICOM browser still jumps to the default position.

Hi Csaba -

I can't seem to replicate this on either windows or mac - tried my local build and the windows download. Can you try again and let me know if it still happens for you?

Here's what I tried:

• enter dicom module, browser shows
• move the browser
• click the DCM button on tool bar, no change
• exit dicom module and click tool bar DCM button again and browser comes back to where it was

Do you see something different?

Hi Csaba -

Do you still see the moving behavior of the dicom browswer you mentioned in the note?

-Steve

Yes, it still jumps under Windows 7 64 bit using revision 21839.

If I do the same steps as you did, then on step 3 (click the DCM button) it always jumps back to the position where it was when exiting the DICOM browser the last time. Trying to clarify:

• Open DICOM module, the browser appears on position A
• Move the browser to position B
• Click DCM button, the browser jumps back to position A
• Move the browser to position C
• Change to a different module (e.g. Models)
• Click DCM button, the browser jumps to position C
• Move the browser to position D
• Click DCM button, the browser jumps back to position C !

Ah - I see the difference. I wasn't closing it in between.

Today I reverted to the last revision that worked perfectly on windows (21787 on March 9), and I don't have this jumping issue with this version.

Steve, please wait with this issue until the Slicer build is fixed on Windows, so that I can try it with an actually working non-hacked one. It is possible that it is actually all good now.

Today I tried with the latest version on Windows, and it works as expected.

Thank you, Steve for the fix (and your patience :) )!

http://svn.slicer.org/Slicer4/trunk@21777

Closing resolved issues that have not been updated in more than 3 months