World: r3wp

maybe it can be done by measuring the offset instead of relying on 
AWAY

apparently not directly...

making it possible to see where an OVER or AWAY came from would make 
this a whole lot easier.

Are you sure you need subfaces ? Is the text really essential as 
a separate face ? You might avoid all this confusion with feels by 
using a single face, which can show both an image and text natively, 
or use the draw dialect.

text is required to be centered. this is not possible to do with 
draw accurately.

(I suspect you are aiming for a simple specification using existing 
VID styles icon and text. Is that true?)

Yes it is. It's fiddly though.

I've tried and found it to be too hard to be worth the trouble. It 
depends on the font and the size of the font.

Calculating the size of the text is the most fiddly part. But I can 
help there.

I won't be using DRAW.

I've just been doing that whilst making a tab-bar the last couple 
of days.

Yes, I don't think you need draw for this. What's the link again 
to your tool-bar demo ?

see announce

I've redone some feel code so it responds much better now, but there 
are still problems. this is a different problem now with being unable 
to use the 'over function to determine whether the mouse is over 
the icon frame or not while the left mouse button is pressed.

so if you are clicking on top of the icon frame and move the mouse 
away, you can't cancel a click.

Mmm.. just quickly, looks to me like you don't need subfaces... but 
dinner time..

highlighting requires two different effects, one for each face. also 
there are differences when showing icons and text, or only one of 
each.

Ok, so you need subfaces for those effects.

oh well... perhaps DRAW is the right way forward to draw the image 
and then bottom align the text. maybe then it really can be done 
in one face.

can't you use font/valign: 'bottom ?

yeah that seems to work

I think this is something that's worth taking up for VID+

Ah yes, definitely. I found the system quite confusing when trying 
to achieve certain things.

It's silly that feel/over is blocked when the left mouse button is 
being held down. this prevents me from detecting the face edge properly.

After intensive study, you can start to see it has its own twisted 
logic, but it can definitely be improved.

Yes, you have to use engage.

engage and over together.

the problem with engage is that it blocks when another face is overlapping 
it. the same problem, just in the opposite direction.

yep :) welcome to madness :)

I've almost made it working now, except that exiting from the icon-frame 
is not detected, when the mouse is held down. I don't know how to 
deal with that. I can easily "exit" to the subface....

The question I tried to answer for a long time was "how do I know 
if the mouse is in this rectangle or not ?"

hmm.. that would mean the main toolbar might need a feel as well. 
this is getting messy.

engage should get away and up events.

Ah yes.. but it's the engage of the subface... yes...

it gets the away event, but too many times. I try to block that by 
asking which face I'm over, using feel/over, but feel/over doesn't 
work exactly when I need it to.

I'll try something with engage instead of over.

don't worry, just filter it using a state flag.

(if you get too many events)

I am using one already, but the state flag can't be changed with 
over where I need it to change :-)

After fiddling with event-flow-diagram.r, I recommend icon-frame 
detect to check the offset for inside/outsideness. It can also check 
if event/type = 'down [mouse-down?: true]      mouse-down? can be 
set false by engage functions when they detect 'up event.

I think I got it now

cool, sleepies...

woo! it works now

:)

no! the same bug is back

I'm quitting... it works a tiny bit better than before, but it's 
still odd. Don't wiggle the mouse too much while pressing the button 
:-)

Changed it to a combination of detect and engage. I think it's working 
now (crossing all my limbs, fingers and toes)

eyes?

no, that hurts too much

DId not read the thread, only the problem. The trick is to put a 
transparent face over all the others, 'sensor in vid. Then you dont 
get  clicks in your faces, but all is nicely captured by the sensor.