Marina Zhurakhinskaya 454ca09575 Make individual dash panes reactive instead of making the dash Group actor reactive ... The width of a Group actor ends up including the width of its hidden children, so we were getting a reactive object as wide as the details pane that was blocking the clicks to the workspaces underneath it even when the details pane was actually hidden. Not making the dash Group actor reactive solves this problem. However, we have to make individual parts of the dash reactive instead so that the clicks are not passed to the transparent actor underneath them. That transparent actor is used for dismissing the additional panes when the user clicks over the workspaces area.		2009-06-30 19:45:56 -04:00
..
misc	Use a separate icon image as a drag actor instead of using the clone of the icon	2009-06-30 16:42:00 -04:00
ui	Make individual dash panes reactive instead of making the dash Group actor reactive	2009-06-30 19:45:56 -04:00
Makefile.am	Split appDisplay and docDisplay into "model" and "view" parts	2009-06-16 18:50:42 -04:00