World: r3wp

The source code for area is here:

	http://trac.geekisp.com/rebgui/browser/widgets/area.r?format=raw

feel free to propose a solution.

ah ah

you got me

there are several ways

we should first define an api

an interface

how to add, remove  drawable items

or define a dialect for this purpose

the issue is not to create synchronisation but to have a good interface

the syncronisation part is trivial, i''ve done it in "easy drawer" 
script

Updating my script to latest rebgui .. have to do show-color: :set-color 
etc as too much code to change.

what's the equivalent of 'set-sizes  now?

and 'set-fonts ?

And where is this error from ?

make object! [
    code: 300
    type: 'script
    id: 'no-value
    arg1: :on-focus
    arg2: none
    arg3: none
    near: [focus-action: :on-focus 
        unfocus-action: :on-unfocus 
        init:
    ]
    where: 'init
]

ctx-rebgui/widgets/rebind is what you're looking for. Note that if 
you're using request-ui then this does it for you. Basically each 
widget now knows how to refresh itself when relevenat colors, sizes, 
relevant or effects are set/changed.

Error looks like it comes from old drop-list code.

I ask the user to choose the text size etc at startup ...

ctx-rebgui/sizes/font: new-size
ctx-rebgui/widgets/rebind
reshow-main-display (if relevant)

Ok, I see rebind.

I am using your drop-list code .. no changes.

I see 'process-keystrokes has now gone.

I was adding function key handlers there .. 

eg. f1 [ f1-handler ] f2 [ f2-handler ]

...

Does your app specify an on-focus trigger anywhere? If so, which 
widget?

no ...

don't use any on-focus triggers

process-keystrokes has been inlined into the display function. This 
fixes those errors where typing while the focus is on a button placed 
the characters into the previous field/area with focus.

Ok, so I can add my function key handlers there then.

Have you thought of adding them to rebgui ?

afterall, they are on the keyboard !

Are these global in nature or specific to a display?

mine are global .. and are just redefined by the user at startup.

e.g.

	display/F9 "Test" [...] [print "I pressed F9 on this display]

AT what point do you get the focus error? On app startup or tab navigation?

don't understand

Does the focus error occur before anything is displayed?

on app startup

I have one password entry screen, then a status window, and then 
before the main window pops up, I get this error.

password screen closes, status window appears, and then the error

Can you grep your source code for "focus-action: :on-focus" ... that 
line doesn't exist in the standard SVN source. Using any custom widgets?

drop-tree ?

yes, its in drop-tree

Is that a critical widget for you?

No, I am removing it now.

It was nice to have but no critical

chart, 
drop-tree, 
grid & 
input-grid need a bit of work to get 
them working again with Beta 2.

Ok.

What do you think then of adding global function key handlers?

Not a bad idea. How do you specify them (i.e. if not via a display 
refinement then where/how)?

It would make it easier for me each time I have to merge my sources 
with yours ;-)

well, I just have these functions f1-handler: does []