World: r3wp

I'm not sure my setup was that simple (it's gone now).

I tested on this code:
insert-event-func f: func [f e][print [e/type e/offset] e]
view layout [box red]
remove-event-func :f

With the above code on Linux I see this:

move 77x78 ; Final move of mouse to a stop, then I wait a short time...
down 77x78 ; <- I click.
up 77x78 ; <- I release, and I wait...
move 77x79 ; I begin moving mouse again.

(That's using View 2.7.6.4.2)

Yes, so it looks windows is adding the 'move event after I release 
the button....seems like no big issue tome though.

If I remember correctly, Windows also inserts a 'move event before 
the 'down, doesn't it?

I don't see that behaviour on my system..only one additional 'move 
after 'up

Ok, probably my poor memory of it then.

but in both cases it shouldn't be a problem IMO. Those events just 
goes thru your handler without any real action and doesn't look like 
a performance hit at all.

By the way, the "no" real handling of rate in window detect  that 
Maxim let me understand why I was unable to slow down the "Splascreen" 
demo as it use the window feel, not a face feel.

...that Maxim point of ...

is there any known way to make rebol spontaneously quit? I've run 
into a case where it just quits, when I focus a field in the VID 
Extension Kit, but I have no clue what does it, although I can reproduce 
it every time.

under OSX a segfault is produced.

using the variable name 'Q  ...  honestly, it's happened to me.

nope, this one really just quits. I've reassigned Q, QUIT, UNVIEW, 
everything.

I remember I have seen that in some recursion/stack overflow cases 
but just guessing here.

some AGG blocks crash ... are you using AGG?

no AGG

are you using a popup?

Cyphre, it's possible there is some recursion problem.

Maxim, no a VIEW window

very strange. especially on a focus event.

this is one case of this 'feature':
a: does [if error? try [a][a]]

are you using 'WAIT [ ] manually somewhere?

maxim, not that I know of.

Cyphre, ok nice to know.

did you check ram use?

less than 10 megs. it happens very quickly.

Henrik, I bet you are calling FOCUS recursively or something like 
that.

it's possible

a print object statement can also cause the interpreter to bust its 
stack.

I think I figured it out... I have created a pane of faces manually 
where one is focused. Then I decide to remove that pane and build 
a new one, and then focus a new face in that new pane. But my focus 
calls unfocus first and wants to perform a focal-face on a face that 
doesn't belong anywhere => crash.

wants to perform a SHOW on a focal-face

Shouldn't this be catched by the GC?

IMO Looks more like a View(text related) bug.

well, the face that SHOW is trying to show remains in memory, possibly 
with a reference to a parent-face that no longer exists. what exactly 
makes SHOW go boom, I'm not sure.

fix is done by unfocusing before destroying the pane. interesting 
bug.

There is a strange auto-complete (tab key) problem on View 2.7.7 
console,
connection: context [a: 1 b: 2]
test: context [a: 1 b: 2]
when you type conn then press tab key it writes just "connected?"
but its ok for test. no auto complete for "usage" function also.

I've found another tab-complete problem where an error is produced. 
Only seen it when running large apps though.

After loading RebGUI tab-complete gives error for undefined values 
also.

Endo, I see the error in View 2.7.6.4.2 as well.
>> connection: 1
then I type "connect" and press tab --> "connected?"

there's a built-in function "connected?" which lexicographically 
sorts before "connection", so it's completed first

That's the bug. It's supposed to stop the completion after the last 
letter common to all the possibilities.

And Rebol does that - try it with "con" and hit tab twice.  The bug 
is omitting user-defined words..

possibly only does defined while in the console

nope, it seems only *some* words starting with 'CON  are omited. 
  'CONTENT is also ignored in auto-complete... very strange

Clean console?
>> ? content
No information on content (word has no value)

possibly related to binding order on app startup... the words 'connect 
and 'Content are already defined in system/words when you boot up 
REBOL, but they are unset!

the auto-completion doesn't bring up values which are unset!


but its strange that defining them doesn't tell the auto-completion 
to use their "current" value, especially since we are operating in 
the global context.

It's not the fact that it's a user-defined word. It must be something 
else. It looks to me like it's because the word 'Connection (with 
capital 'C') already exists in system/words on startup. Defining 
'connection in the global context doesn't change the capitalisation 
on the existing symbol. So I think the completion function is case-sensitive 
Try in the console:
>> Abacus: 1
>> abalone: 2
>> aba
and press Tab Tab.

hey I think you got it.