[Bf-committers] Join Screens OGL Bug

Matthew H. Plough mplough at Princeton.EDU
Thu Sep 22 22:43:15 CEST 2005


I'm not sure that the arrow makes things more intuitive.  All we need  
is something that is intuitive after the first time someone uses it  
-- the arrow looks gaudy and a tad unprofessional to me.

How does this implementation sound?

Click on the screen area edge to join to bring up the split/join menu  
-- same as currently.  Then, darken all screen regions (dynamically)  
except the one where the mouse pointer is located.  If I wanted the  
left region, I'd click anywhere inside it; if I wanted the right  
region, I'd click there instead.

No animation is necessary.  The required click accuracy is so low  
(generally the regions will be hundreds of pixels high and wide) that  
the user shouldn't need any kind of visual confirmation of what's  
happening.

The cost of an "extra mouse click" is far lower than being stunned  
and frustrated for a few seconds when you accidentally bring up the  
split/join menu from the wrong side of the window edge.  You'd then  
spend a few more clicks and keypresses trying to get the screen  
region the way you want it.  To me this is a common problem and is  
very frustrating.

Matt

On Sep 22, 2005, at 15:20 PM, Jakub Steiner wrote:

> On Thu, 2005-09-22 at 20:25 +0200, Ton Roosendaal wrote:
>
>> Hi,
>>
>> It's an interesting method, and nice gfx, but I really doubt this is
>> what we need... for example the graphic appears counter-intuitive on
>> the "wrong" side. The extra click also is a minus point.
>>
>
> Hi folks,
>
> I just tested this and it works rather nicely. Unlike the previous
> behavior where the user gets absolutely no visual feedback on what is
> going to happen, this is a step in the right direction. Additionally I
> suggest the merge happened fluently, using a short animation (say  
> 0.5s).
> That way you get a better idea what view you're getting. A nanosecond
> blit has you wondering if that's really the view you wanted.
>
> Overlaying a close button on the focused frame window may be a more
> elegant solution, but I don't consider the arrow counter-intuitive
> myself.
>
> But I have a funny incident about window behavior. It didn't happen  
> once
> that I have subconsciously used the window manager close shortcut when
> trying to close the floating 'N' blender window. If more
> window-manager-like functionality gets added, maybe the confirmation
> dialog should be brought up in cases like these.
>
> cheers
>
> -- 
> Jakub Steiner <jimmac at novell.com>
> Novell, Inc.
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
>



More information about the Bf-committers mailing list