World: r3wp

Looks nicer and polished. The only note to UI from my side - button 
gradient - makes white text badly readable ... but other than that 
it looks good. Nice addition with row-coloring for table and text-list 
- such small detail and it looks much more pleasant ...

Yeah, my major insight over the last year concerning UI design is 
that it's not a question of "great graphics" but simple attention 
to numerous small details ... get the details right and the whole 
lot comes together.

I agree .. it's all about the detail

display "" [button [display/dialog "" [field]]] do-events ;; nothing 
pops up when clicking the button, why? only me?

Try using a window title ...instead of ""

Maybe tree widget could benefit from row coloring too? Would look 
consistent with table and text-list.

nothing pops up when clicking the button, why?

 ... the display function exits if it hits a duplicate window title 
 (before calling layout) ... this means you don't have to worry about 
 the user hitting a button that calls a display multiple times and 
 getting multiple (near identical) windows popping up!

tree widget could benefit from row coloring too?

 ... it will, once I've rewritten it to use the same face-iterator 
 func that table and text-list use (which means it'll get all the 
 extra goodies like auto-slider support as well!

.... sounds cool!

I remember that a previous tour had the tree inside a scroll panel 
and as you expanded the tree, sliders appeared in the scrollpanel. 
 Sometimes you can now display all elements of a tree without that 
functionality.

Build 208
- Fixed unfocus bug
- Fixed table focus bug
- Enhanced request-verify (auto-calc label widths)
- Reworked tree to use face-iterator
- Reworked request-dir

Note the reworked tree widget only has one option [only], and currently 
defaults to expanded mode with no leading graphics. It accepts input 
in either nested block or file/path notation. Selected items are 
now fully qualified by default. Due to it's use of face-iterator, 
it no longer has practical data limits (previous version created 
a face for each item).

Face iterator - a native R2 View thing?

How can I collapse nodes in new Tree? Tree without graphically distinguished 
nodes looks strange :-)

Now I do seem to understand, what still feels kind of wrong with 
scroller:


- normally, scroller has arrows. One arrow press scrolls data upon 
some number of items

- in regards to above, when you click anywhere else on the scroller, 
it should not jump directly under the mouse pointer, but only once 
again it should move by defined amount of data


... and it is not the case with our scroller. I should note that 
the "wrong feel" is just of a cosmetic nature, nothing annoying ...

Graham and Ashley - thanks for window title hint, so simple...


The other big problem I'm still having is crash when tabbing. It 
worked with 204 and  before. I doesn't work with 205 - 208 .

>>display "" [panel data [field]]   ;; click on field and press <TAB> 
button - bingo!?

Group-box and scroll-panel seem to have the same problem.

Uploaded some more focus bug fixes ... should solve these issues.

Thanks Ashley.

Two more little bugs, not in a hurry:-

>>display "" [button [display/dialog "Tab me" [field field]]] do-events 
 ;; not movement

>>display "" [button [display/dialog "pop" [field field]]] do-events 
 ;; panel not resizing

no resizing unless you add the resizing #WHXY etc

I'm sorry, I copied wrong code.

>>display "" [panel #H data [field #H]] do-events ;; panel doesn't 
resize at all

>>display "" [group-box #W "" data [field #W]] do-events  ;; group-box 
resizes and looks like panel, why both?

Disregard >why both?< part. There are more attributes with group-box, 
I just found.

Build 209
- Fixed #LV span options for
	- button
	- group-box
	- panel
	- pill
- Fixed tab-panel tabbing
- Removed redundant scroll-panel from request-dir
- Reworked on-resize handling for most widgets
- Removed #O span option (made redundant by on-resize)
- Renamed span-size to span-init
- Improved popup handling (drop-list, menu, etc)


Note that this build has [temporarily] broken dialog modality (you 
can click outside of a dialog) and tab-panel action blocks.

Menus - good first step, but menu should not close upon mouse-away 
... it should close upon ESC, or click-away ...

Slight problem with hilighting in Toolbar widget ... try randomly 
moving away from icon, sometimes it stays hilighted, so you can get 
multiple icon hilighted ...

The over effect is mild too, and without Tooltip, I would not probably 
use toolbar in my app ...

Build 210
- Fixed dialog modality bug
- Fixed tab-panel actions
- Enhanced radio-group (auto-size label widths)

- Added back #R and #O span directives to handle imbedded reverse 
widgets

- Moved window-feel out of display func and share across all displays

The #R and #O directives handle this case:

display "Test" [
	panel #L data [
		field #L
		reverse
		button #R "Cancel"
		button #O "OK"
	]
	return
	bar 75
]

Pekr, above issues noted. Tooltips are being added back to toolbar 
[only] as they were in the early builds. I'm also looking at ways 
of reducing memory usage (sharing more objects in layout and pre-building 
certain common font usage cases (e.g. align: 'center)).

Ashley - you're da man! All good stuff :-)

I can see edge object for tree - can it hold an image? The way it 
is done in tour.r tree widget does not look like tree :-)

You're on the right track. I'm trying to get an image in there without 
creating another face. The 3 places you can have an image in an existing 
face are: image, effect and edge. The first image I want to get in 
there is a folder icon so request-dir looks a bit better! ;)

I always have little problem with tabbing over fields.

>> [field [if bad-input [do-something set-focus face] field] ;;; 
 triggering by <TAB> gives  focus to wrong field

Should I use on-key instead of default event block with check for 
#"^M"?

Should field behavior to be changed to be like button - action triggered 
only by <Enter>, <TAB> only moves focus - or should it stay as it 
is, Ashley?

http://www.dobeash.com/RebGUI/user-guide.html#section-4.1.4... note 
the action-on-* behaviors

Thanks a lot Ashley. It worked for me with on-key, but proper way 
is always better. Ta again.

Build 211
- Moved base objects from ctx-rebgui to system/view
- Removed all dependencies on View/VID mezz code
- Rewrote and added show-popup & hide-popup functions
- Removed style widget
- Inlined popup logic
- Converted internal images from base 16 to base 64
- Cursor keys now work in choose (drop-list, edit-list & menu)
- pad option in layout enhanced to accept pair! (pixels)
- Added tooltips to tool-bar
- Added request-edit
- Improved resize logic
- Fixed request-dir (resize bug)
- Fixed slider (resize bugs)

Removed style widget - so no more VID?

Not that I miss it, just a question :-)

btw - memory consomption still above 12 megs for tour.r ... but I 
find it OK ....

- lists - still the same bug ...

- tooltips - nice, but mouse pointer almost everytime covers first 
letter of tooltip itself ... maybe a bit of spacing/shifting would 
help ...

Ashley, I am using build 210 (I'll update shortly), but wow, I love 
this little library. No compromises, fault intolerant, and best of 
all, ZERO learning curve.


Would it be an idea to add some systray functions to RebGUI for Windows?

Gabriele has written some systray stuff ...

Not sure it was Gabriele - Cyphre did something upon contract for 
me, and I released it 2 years ago? :-) IIRC Cheyenne uses it too 
...

Seems something here, http://rebol.wik.is/Code_Samples/Systray.r

I can send you win32 API based version ...

Oh yeah ... that's the stuff I took from Gabriele's script.

Ashley, I get this when I encap the latest rebgui.r 

** Script Error: Cannot use path on none! value
** Where: load-stock
** Near: if not image: find system/view/vid/image-stock
** Press enter to quit...

Maarten: Thanks. The Systray.r file Steeve linked to above is pretty 
self-contained (and explanetory), so I don't see much value in duplicating 
it in RebGUI (apart from the fact it is Windows specific, which is 
why I've left native requestors out as well).


Graham: The only SDK file that RebGUI now requires is gfx-colors.r 
(plus prot.r if you need protocol support). load-stock is one of 
the many View funcs loaded when you include view.r.

Build 212
- set-title enhanced to search for parent
- fixed request-edit title bug
- removed append-widget
- removed set-values
- updated get-values
- improved tool-bar tooltip spacing

Going to test tour.r :-) btw - when do you plan to fix pop-ups (menu) 
mouse-over disappearance?