Andrey showed me a similar issue where he couldn't drag and drop a volume into a transform using his mac book pro.

If you are close to the lower boundary of the blue, when clicking it works. If you are close to the center of the blue bar it does not work. This requires too fine a control.
BTW: the adapting box around the tree is too tight. It would be good to have half a line of empty space between the bottom of the tree and the box. Again to much precision needed in the current setup.

Fixed in r17755:
http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=17755

It was failing the first time the volume was dropped, but was working the second time.

Half a row height under the tree is fixed in r17756:
http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=17756

The three selections for displaying information in the data module are confusing.

Unfortunately on my mac build dragging the volume into the transform causes both of them to disappear from the Data tree(!). This is on mac lion with qt 4.7.3 and svn 17990.

On my linux build all works as expected.

is this 100% reproducible ?
Do you do the following ?
load 1 volumes
open the data module
create new transform
drag the volume under the transform

Yes, exactly, that's the procedure and the errant behavior happens 100% of the time.

It looks like the nodes get marked as 'hidden' for some reason. If I switch to the Transforms module the transform is initially selected, but if I try to reselect it the module disables and I can't reselect. Also in the slice controllers it is not possible to pick the None volume option...

Confirmed it still happens on r17997 on mac osx lion.

Still happens on mac (not linux) as of November 22 - happens on the release build.

Fixed in r18754:
http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=18754

Indeed, it was a Mac only issue, its internal implementation of Drag&Drops is different from Windows/Linux in a way it calls processEvents on the application within the drop.
It had the side effect of calling onItemChanged() too early. We now use a timer (delay could be decreased if needed).

This is still an issue -- I have the same problem now at RSNA Slicer booth. Julien: stop by to see a demo :)

Julien saw this today - he agrees it is a bug :)

But it may be something internal to Qt-on-mac itself and may be hard to fix...

What is the status of this issue? This is very inconvenient.

If this cannot be resolved, how about we modify the interface and add something like "Parent transform" combo box in the volumes module?

This will be ugly, but better than having to open the python console to each time I need to put something under a transform.

Agreed - it would be good to have a second method for this.

I would think that the lower portion of the Data module could have a node combo box for parent transform that would be enabled whenever a transformable node s selected in the tree. This might also help users 'discover' functionality like being able to transform annotations, which is otherwise a kind of hidden feature.

IMHO the natural home of an interface associating a transform with an element of the mrml tree would be the transforms module.

We would need to think about how to handle nested transforms as well.

How about Selecting a transform from a tree presentation brings up a pop up which gives you a two column listing of all the elements that can be transformed. One column is "under the transform", the other is "not under the transform". Hit apply or cancel to finish.

I like the idea of adding transformable nodes to the current transform in the Transforms module.
How about a new field "Transformed:" that lists all the nodes under a transform. When the list gets focus, a panel containing the list of untransformed nodes opens on the side of the list.
<< and >> buttons are also in the panel to move the nodes from one list to the other.

First implementation in r19121

Very nice!