World: r3wp

Right Anton, but I am perjured myself later, saying (the problem 
may exist in other styles). :)

Ashley, sorry, I'm working from the RM-Asset version. :-)

a way around it, would be to do a "soft show": all [face/show? show 
face]. this can be installed in feel/hot in the vid-feel.r file, 
if you have access to the VID sources.


also using size 0 would not work in the VID Extension Kit when resizing.

Is there a way to get anti-aliased fonts in an area?

only by using DRAW and that is quite difficult. (just ask shadwof) 
better to wait for R3 for this.

I need to detect capslock and alt-key events.  Does anyone know if 
this can be done?

I think not ... more about events:

http://www.rebol.com/how-to/feel.html
http://www.rebol.com/docs/view-face-events.html

What about R3?

Not sure low level code changed in that regard ... I will try to 
ask Cyphre. We imo definitely need to add support for combinations 
like ctrl + tab, etc.

It's unrealistic to expect people to do without alt-keys. They're 
used in practically all programs as hotkey components. With respect, 
there should be a way to do this.

Rebol opens a system port, that is to say a port with scheme 'system, 
but when I look in system/schemes there is no system scheme.

Why doesn't rebol detect alt or capslock?

I think some keys were excluded, because of cross-platform issues. 
I do remember arguing about it with Holger in the past. We have to 
change it. Some keys might not be so trivial to get to REBOL, but 
we should try ...

Cross platform compatibility. Not all platforms have/use ALT and 
CAPSLOCK keys. Which was more importend way back when REBOL ran on 
40+ platform.

(oh, Petr beat me)

View never run on more than a few IIRC - Windows, Linux, initally 
maybe BSD, Amiga ...

What do you think? Should Rebol detect capslock and alt-down?

I hope rebol will eventually be ported to the android operating system. 
Phones have different keyboards. Will that be an issue?

Yes, for apps where OS/platform consistency is more importend than 
cross platform compatibility, there is a need for things like thing.

*like thing = like this

I hope not. I can't see any problem some platfrom not supporting 
e.g. Alt, or Windows key .... it is imo fully upon programmer to 
handle. But not having those key-presses propagated to REBOL is, 
well - stupid ...

Is there anything that I can do?

Could I theoretically make my own 'system scheme with BIOS calls 
and load it instead of the default one?

In R3 there's system/schemes/system, do you think that could be changed 
to do this?

system/schemes/system: make object! [
    name: 'system
    title: "System Port"
    spec: none
    info: none
    actor: make native! [[port!]]
    awake: make function! [[
        sport "System port (State block holds events)"
        ports "Port list (Copy of block passed to WAIT)"
        /local event port waked
    ][
        waked: sport/data
        loop 8 [
            if not event: take sport/state [break]
            port: event/port
            if wake-up port event [
                if not find waked port [append waked port]
            ]
        ]
        if not block? ports [return none]
        forall ports [
            if find waked first ports [return true]
        ]
        false
    ]]
    init: make function! [[port][
        port/data: copy []
    ]]
]

Is the R3 Host Kit available?

IIRC, some people have it for testing purpose, if you ask for it 
on "R3 - chat", perhaps you'll get it

Nicolas, unfortunately due the system-port bug in R2 it is possibe 
to detect ALT etc. keys only in the Rebol console window.

Cyphre - and as for R3? btw - what does it have to do with the system 
port? Are all keyboard events captured via a system port, or just 
only special keys?

Yes, all system events are captured by system port first. IIRC in 
R3 there is currently no way how to capture non-rebol-defined events 
but in R2 this is possible though only from the console.
I believe the event port capabilities in R3 will be enhanced.

I'm trying to extract info from faces in a panel but I can't get 
it...


I can see the objects! with mypanel/pane but what is the rest of 
the path to get to say a buttons "data:" field?

that would be for example mypanel/pane/1/data if the button is the 
first element.

I tried that but 'm getting an invalid path...

I'm trying to step through them with a foreach statement...i've done 
it with scroll panels but can't figure it out for a simple panel/pane

the pane can also be an object. in that case the path would be mypanel/pane/pane/1/data

still error1


** Script Error: copy expected value argument of type: series port 
bitset
** Where: expand-specs
** Near: specs: copy specs
foreach var

where are you putting this foreach statement? this looks like a dialect 
error.

can you post the code?

The above error was from this probe : probe cal_panel/pane/pane/1/data


Here is a segment of the generated code that I pass through LAYOUT 
before i attach to panel :

[origin 0x0 space 0x0 styles cal_styles across return box 81x81 192.192.192 
with [

edge/size: 1x1] [data: compose [28-Mar-2010]] effect [draw [pen yellow 
text 25x5 "

10-15" pen blue text 25x18 "25-5" font italic-font pen black 40x50 
text "28"]] [pr

int face/data] box 81x81 192.192.192 with [edge/size: 1x1] [data: 
compose [29-Mar-

2010]] effect [draw [pen yellow text 25x5 "13-18" pen blue text 25x18 
"3-8" font i
talic-font pen black 40x50 text "29"]] [print face/data]

the above code is in a block called matrix_panel
then attached to cal_panel with :

cal_panel/pane: layout/tight matrix_panel

where do you call foreach?

just after : cal_panel/pane: layout/tight matrix_panel

with [edge/size: 1x1] [data: compose [28-Mar-2010]]

-->  with [edge/size: 1x1 data: compose [28-Mar-2010]]

Does that work?

bingo ...thanks guys...weird though as I only added the edge a moment 
ago..

Awesome. You're the first guy I've helped.

I can now go to bed...thanks double

View question ... http://synapse-ehr.com/forums/showthread.php?46-mouse-over-events

don't worry ... I debugged it for him.