I agree that automatic opening and closing of the tabs could be very useful. <br><br>1. NOTE: Click and click-drag can occur in the *exact* same screen area. Just think of single-clicking vs double-clicking vs click-dragging of a desktop icon.<br>
Single click = Mouse button down --> Mouse moves less than 5 px in any direction --> Mouse button up.<br>Click-drag = Mouse button down --> Mouse moves more than 5 px in any direction --> Drag is initiated --> Mouse button up --> Drag operation is stopped.<br>
<br>This means that the entire top bar of the panel can support both single-click to open/close and click-drag to drag the panel to a new position. (No more carefully aiming for the small arrow to expand/collapse a panel. )So, the hotspots for the two operations do not have to be confined to separate areas but can co-existing in the same area as long as the mouse interaction logic supports it.<br>
<br>2. Having the application more intelligently display the relevant panels and options based on selection context is something we're all used to from context menus.<br><br>Of course, exactly what panel is correct in any given context is probably a little up to each individual user. However, identifying those moments when you keep searching for the right panel, like you have done, Jon, is a very good start. <br>
<br>"for me it is quite a problem that blender displays so much information<br>
at once. every time i want to find some settings I have to scroll,<br>
search and try to remember where the desired settings are located."<br><br>This is my exact problem as well. I'll try to pay more close attention to what panels are relevant in a given context and see if any changes like this would solve my problem.<br>
<br>With regs,<br>Jimmy Volatile<br><br><div class="gmail_quote">On Fri, Sep 18, 2009 at 6:45 PM, Dalai Felinto <span dir="ltr"><<a href="mailto:dfelinto@gmail.com" target="_blank">dfelinto@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Too much UI dance for every tab opening is way too distracting IMHO.<br>
Leave it as an alternative (not the default) can work though.<br>
<br>
Dalai Felinto<br>
<a href="http://blenderecia.orgfree.com" target="_blank">http://blenderecia.orgfree.com</a><br>
<br>
On 17/09/2009, at 19:14, Jon Sandström <<a href="mailto:sjon@student.chalmers.se" target="_blank">sjon@student.chalmers.se</a>><br>
wrote:<br>
<div><div></div><div>
> this workflow will require an improved design of the "hotspot" area in<br>
> the tab headers.<br>
> currently the triangle is used to open and close the tabs, while the<br>
> rest of the area is<br>
> used to move the tabs. since the "open/close" hotspot is the one most<br>
> frequently used,<br>
> this should have the largest area, and a new third area could be<br>
> used to<br>
> pin the tab<br>
> open (again, see mockup:<br>
> <a href="http://img156.imageshack.us/img156/5245/mockupr.jpg" target="_blank">http://img156.imageshack.us/img156/5245/mockupr.jpg</a> )<br>
><br>
> when the user opens a tab we can assume that he/she wants to see all<br>
> its<br>
> content,<br>
> and therefore blender should if necessary scroll to a position were<br>
> the<br>
> entire content<br>
> of the most recently opened tab can be viewed<br>
><br>
> conclusion:<br>
> if tabs are automatically closed, it will be easier and faster to find<br>
> desired data.<br>
> this behaviour can co-exsist with current behaviour (pinning) so i<br>
> cannot find any arguments<br>
> not to implement it<br></div></div></blockquote></div>