World: r3wp

Actually, when it's in-style, you do not have to take care of box 
model - that's problem only with universal solution.

does it currently fallback to a simple frame, if no highlight option 
is available?

I'm still just talking about visual representation of focus, nothing 
else. Catching focus should definitely be done on system level, I 
agree.

does it currently fallback to a simple frame

 - It should, but border seems problematic somehow. I'm working on 
 the gob mask, you were talking about, it's just not finished yet.

Simple frame: OK.

Catching focus, yes, we agree.


Visual: I still think the visual representation could be done automatically. 
The ancient Deluxe Paint III on my old Amiga could do the same with 
brushes, in that it would draw a single-pixel wide line around the 
bitmap. Do that a few times with fading colors and you have the look. 
If they could do that 20 years ago on a simple 68k machine, we surely 
can do the same today in REBOL3, if we have the clickmask and perform 
a simple blur on it.

Ah, ok I understand the mechanism you've got in mind. But implementing 
this would take more time than I spent implementing focus in-styles. 
But this would be nice to have, I agree.

a small glitch with style browser - I do mouse over of preview tab, 
it crashes. In console I do unview none, but consecutive start of 
style browser fails. Ditto when I try to re-do r3-gui.r3

mouse wheel scrolling works only upon the scroller of list. It should 
imo work even when upon the list itself ....

Mouse over on tab-button opens tooltip with preview that's done using 
to image! I saw some problem ssolie had here some time sooner and 
to image! was in the error description. I wonder if you've got latest 
R3, I had preview disabled in previous versions because to image! 
was causing crashes.

mouse wheel scrolling works only upon the scroller of list
 - bug, I'll fix it.

This is what I get for mouse-over upon the preview tab - it displays 
the preview and crashes with:

** Script error: tooltip: needs a value

** Where: either if function! all do-style either if either do-event 
do-event ei

ther -apply- wake-up loop -apply- wait do-events catch either either 
-apply- do
** Near: either arg [
    buttons: compound-face? face
    tab-box: c...

Pekr, if you've got some time to help, please, have a look at keyboard 
nav and post any problem you find to me personally to not polute 
this channel. This will help very much.

ok

Dunno if it would be good concept (it might be confusing for user), 
but some time ago I was thinking about nested tab system. What I 
mean is - most of tabbing systems do work in a flat way. It is kind 
of primitive. But - sometimes you might want to use the same navigational 
keys for more complex styles, typically subpanels, grids.


What we recently got (and can be seen with e.g. style browser) is, 
that e.g. tab panel can be tabbed. Then arrow keys do switch between 
tabs. What I had in mind was to be able to press enter, to nest the 
tabbing, so that you "enter" the subpanel, and esc to escape back 
to the upper level (this part might be tricky for users, not sure 
about it - they might feel being locked inside of some style).

Any ideas?

Recently we use tab  key .... maybe it is good enough, I don't know 
- first tab tabs to the subpanel, next tab tabs to its first element. 
When at least subpanel tabbably position, next tab moves to next 
style ...

btw - will there be added visual representation to field tabbing 
too? It feels a bit inconsistent the way it is ....

Also - I noticed that with field button, arrow down-up moves to the 
first/last position - it does not work like this in Windows. What 
it does (in opposition to current R3 GUI) is it hilights the whole 
text ...

ctrl-tab should be implemented in low-level for moving between tabs 
...

Henrik: view [button] works just fine

Henrik: just the style-browser.r3 script doesn't seem to work for 
me

ssolie, there must be some style causing the error.

Does:

make image! 10x10 work?

ssolie: the problemyou have is that OS_GOB_To_Image() is not implemented 
in A109...You need A110 to get that functionality working.

ssolie: well, the OS_GOB_To_Image() is even not yet in 'official' 
A110. I can provide you the changes so you can merge it to your A109 
if you want.

Henrik: yes, make image! 10x10 works fine

Cyphre: I'm willing to give it a try.. it is becoming some kind of 
patched up monster so I hope Carl passes over the official A110 soon 
;-)

Hmm - just downloaded 2.100.110.3.1 and get this upon load-gui:

Hmm - just downloaded 2.100.110.3.1 and get this upon load-gui:

Hmm - just downloaded 2.100.110.3.1 and get this upon load-gui:

Hmm - just downloaded 2.100.110.3.1 and get this upon load-gui:

Hmm - just downloaded 2.100.110.3.1 and get this upon load-gui:

Hmm - just downloaded 2.100.110.3.1 and get this upon load-gui:

GUI version 0.2.1 snip ...size-text has no value ... snip

load-gui references Carl's old GUI but you need to manually load 
Henrik's Gui

ah - and how?

download http://94.145.78.91/files/r3/gui/r3-gui.r3
do %r3-gui.r3

thanks!

you're welcome :)

We should make this a FAQ

download the file as directed, when doing it:

>> do %/c/r3/gui/r3-gui.r3
Script: "Untitled" Version: none Date: none
** access error: cannot open: shape reason: "module not found"

This looks like you are using the /Core version no? Where did you 
download the 2.100.110.3.1?

You'll need a "/View" build of A110, such as:
http://94.145.78.91/files/r3/gui/r3.exe
http://94.145.78.91/files/r3/gui/r3lib.dll

Mine is of the same version as Kai's. I hope the core and view versions 
do not share the same version number.

Thanks again!

Henrik, so far there is no difference in the 'about' output when 
you build r3/Core or r3/View exe. Even system/product is always set 
to 'core . Something that needs to be solved by beta.

ok, mine shows a window when using View, so I suppose it's the View 
version.

Henrik: I have style-browser.r3 running on Amiga now. It tends to 
stop running a lot with script errors... how complete is this app?

ssolie, styles like pane, table-* and doc are not yet fixed. Other 
styles shouldn't produce any errors, afaik. If you find some problems 
from other than mentioned styles, please, send me the errors privately 
to keep the noise low here.

ssolie, since it tests styles, the app should be complete, but may 
occasionally encounter styles that are unfinished. the program should 
be used, every time r3-gui.r3 is updated.

Isn't R3 GUI in CureCode?