World: r3wp

That's the caret. Use FOCUS/NO-SHOW, if you want keyboard access 
to a face, but don't want to display the caret.

Though I'm not sure if it can be done when there is other content 
in the face like that.

otherwise an alternative is to provide a sensor face, size 0x0, sitting 
in the corner. focus that and the caret won't appear. then control 
the main game area using the sensor face.

Will have to do that, no-show isn't working. Thanks :)

The caret is controlled by View on the C-layer, so there is not much 
else to do about it.

Ah well I'm sure it's going to be fixed in R3. R3 will make everything 
better. And coffee. Or so I've heard :)

yes, text is managed on the mezzanine level, while high performance 
parts are in the open parts now.

/no-show prevents the face from visibly being updated - if you do 
a [show FACE] later on, the effect of /no-show is negated

yes, correct.

If you do not have/need text or if you display text only thru agg 
instead of face/text, you can hide the superfluous caret in R2/View 
by setting the face's para to to an origin like -100x-100.

That allows you to FOCUS such faces without having to care about 
caret.

good tip

Works great, thanks :)

It should be enough to set the face/text to none.

That works too, thanks :) Shouldn't it be none by default then? Why 
is the default an empty string?

That works too, thanks :) Shouldn't it be none by default then? Why 
is the default an empty string?

That works too, thanks :) Shouldn't it be none by default then? Why 
is the default an empty string?

Sorry for that, AltMe was acting up

What face or style do you base the face which displays your map on?

Ah - BOX.   print mold svv/vid-styles/box/text ;== none    but it's 
FOCUS which does more than necessary. Check the souce of FOCUS. I 
patched FOCUS so it doesn't have such presumptuous side effects.

Ah alright, I checked the value of face/text after I already used 
focus on it.

Anton, nice one.

Where would this be coming from ?

    near: [if find [down alt-down] Â act]
    where: 'wake-event

where the original code is

        feel: make feel [
          engage: func [face act evt][
            if find [down alt-down] act [
              focus/no-show face/parent-face
              face/start: evt/offset
            ]
            if find [over away] act [
              face/offset: face/offset + evt/offset - face/start
              clamp face
              show face
            ]
          ]
        ]

It's from Henrik's code ...  but I can't see how something could 
modify the code !   Anyway I've trapped it ... so it's not a problem 
now.

mine? which code exactly?

it's something you wrote that allows you to pan an image

ok, the image-pan style?

yep

pan-image style

if you look at that error, there is an extra char in there. it's 
possible that you can find it in the source code and delete it.

It's not there .. that's the worry!

so something is corrupting memory

the char may be invisible. double-checked?

yes

Otherwise I'd get the error as soon as I ran the code right?

but it happens after I move the image around a bit

I'm not sure. The problem is that there is a char which you on a 
mac can accidentally type when holding down alt while pressing space. 
the you get a hard-space char (I think it is). rebol doesn't handle 
it properly always, but it doesn't prevent code from loading.

The stray char looks fairly familiar. You're probably have problems 
with cp1252- and utf8-encodings?

Ok, let me delete the space and reinsert ...

plain vanilla code ..

Oh .. it's working!

maybe there was something odd invisible??

A hard-space then, just as Henrik said.

wonder why it only errors later on ...

A hard-space, this can be encoded by UTF-8 as 0xC2 0xA0, 0xC2 is 
#"Â".

Good to know

It loads, but is probably mistaken for a word with no value? What 
was the exact error message? Word has no value or so?

i've had similar errors with PC control codes embeded in a script.

Need a little assitance with a choice button in layout. How might 
it be possible to assign a list of tables from db query to a choice 
button. The query is no problem.  But at the moment i see no way 
to use the result block in the layout definition of the choice button

I'm not sure, but try this:

my-data: ["a" "b" "c"]

view layout [choice data my-data]

Entirely untested