[PATCH] various nodeAtPoint() fixes

Germain Garand germain at ebooksfrance.com
Thu Jul 18 01:31:41 BST 2002


Le Jeudi 18 Juillet 2002 00:55, Germain Garand a écrit :
> Thanks ! It was a bit rough around the edges (did not take into account the
> case where you have borders only on some edges) so I perfected it today...
>  Updated version attached !

Now I have a small remorse -I think it would be better to be more subtle:

- my old patch said : the box is transparent but has a border, don't go any 
further, it's both the inner and the visual node.

- the new patch says : the box is transparent but is has a border on some 
edges, or around all edges. Let's select it as visual Node if the cursor is 
above a border, but let's go deeper if we are above the transparent part.

In fact, those two approaches are quite different. The first one is a 
"plexiglas" model : you can see through a well defined frame, but you can't 
click through because it's solid. The second is an "aerial frame" model : the 
minute you can fully see something through a frame, you can click it.

I would find more seducing an intermediate approach, that is : 
-if there are two or more borders on a transparent box, the frame is well 
defined, it is felt as a box (optic effect) : don't go further. 
-but If there is only one border, it doesn't really define a box, so try to go 
deeper if we aren't above the border.

What do you think ?

G.

-




More information about the kfm-devel mailing list