World: r3wp

Since I've never seen this in the area face I presume it's fixable.

able to reproduce the boundary issues

 No, and I use area everywhere in my apps. Never come across this 
 problem before. What's the sequence of actions? i.e. it's gotta be 
 more complex than, "just type until it happens". I suspect you've 
 hit a nasty interplay between arrow/slider scrolling and caret positioning. 
 Fixable if I know how to reproduce it.

 the fact that Konfabulator-like dialect that uses View to its full 
 potential is another issue.


did you look at (short on time, cause everyone else was late ;-) 
 elixir devcon session ?


that just what it is...  100% AGG gui engine... with full AGG element 
based interaction and per stroke feel.

Max .. none of us saw the screen ... the broadcast videos appeared 
to concentrate on the rear of things!

AGG + Autofocus = Extra aliasing

AGG without a dialect? Might as well code in assembly, or openGL

Ashley, I can't reliably reproduce this boundary issue.  How about 
putting in a check for when the caret moves to the next line after 
<enter>, to ensure it is not on the same line, and then writing this 
to the rebgui.log ?

Is there a way to make a horizontal scroll bar on a table?  Or maybe 
to make a text-list or area have the horizontal scroll bar?  It may 
be to use the slider widget, but documentation is a bit scarce.

Also, how do I set effects/radius: 0 for group-boxes?

graham... darn... should be putting time on elixir and liquid next 
week *I think*  but with all the things going on in my life right 
now I can't be sure.

TimW - there is very robust grid style, done by Cyphre, under contract. 
It is just there were some API changes, so the grid was never further 
adapted ....

effects/radius: 0 for group-boxes?
 ... effects/radius is global. It is currently used by:

	group-box
	panel
	tab-panel
	tooltip

and can be set as follows:

	ctx-rebgui/effects/radius: 0

Is there a way to make a horizontal scroll bar on a table?

 No, nor with text-list or area. Same issue with tab-panel. This is 
 quite deliberate and you may wish to refer to my comments from 10th 
 March this year headed, "A word on my design philosophy, ...", to 
 see why. ;)

what's the magic incantation to have a widget hidden by default in 
the layout?

display "" [field false]

Thanks .. I managed to work it out :)

The chat widget .. can we get it so that text is selectable?

and links active?

This is more of a general question on gui design... but should one 
keep all buttons on screen, or, provide buttons as required?

I'm of the "don't tell me about it unless I can do it camp" here. 
Nothing worse than hunting through a complex menu to work out what 
I can and can't do. 80% of what I want to do or see should be no 
more than one click away IMHO.

re: chat widget. I'm waiting on R3's rich text enhancements before 
I do much more with this widget.

I agree with Ashley, that user should be provied with valid option 
in particular context. But I don't agree with dynamically rearranging 
menus, or hiding buttons. It is imo confusing. That is why we should 
have ability to disable/enable some elements, but not to hide them 
....

I too would prefer to have visibly disabled buttons on screen .. 
but have to go with removing/adding buttons for the moment.

maybe we could hack in disable/enable functions? I did some, and 
Anton (or Volker) fixed it to work even with keyboard. The solution 
was to put transparent face with some effect into front of "disabled" 
element ...

table: We have extended TABLE to allow horizontal scrolling. You 
specify the number of visible columns and the rest can be scrolled.

it should be part of the widget

how about just adding a disable flag to the button and put a disable 
check in the engage event?

I wonder why noone picks-up on cool grid element :-) Pity API changed, 
so it does not probably work ....

but that doesn't change the visuals ...

Graham - it should, but as an interim solution I welcomed even such 
hack. I refuse to visually remove buttons, according to some conditions. 
That sounds scary, when once there is button, next time there is 
not button at certain position :-)

ghosting out the buttons etcs

well, if buttons are not functional in certain states ..

perhaps better to remove them both visually and functionally?

Well, I am going to try it both ways and see what the users say

Graham - http://www.rebol.org/cgi-bin/cgiwrap/rebol/view-script.r?script=disable-face.r


i have not thought about RebGUI integration yet, not sure it is applicable 
...

Maybe Ashley could have quick look into it? It could be functions 
of RebGUI. But I agree that in fact it should be done in consistent 
way = adding such handlers to each style, so not sure Ashley would 
accept such "hack" into RebGUI ....

When you click in to a text area, the caret always appears at the 
end of the text.  Possible to have the caret to appear at the mouse 
pointer?

Otherwise have to double click

its in 'focus,
  if not caret [caret: tail face/text]
somethig with 'offset-to-caret. anyone? ;)

oops, its rebgui. may be diffferent there.

display "" [ p1: panel 20x20 green data [] false do [ show p1]] do-events

Why does this not show the panel ?

It looks like 'show does not work inside a 'do block

if the widget was hidden

This works showing text in a visible widget .. 


display "" [ p1: panel 20x20 green data [] false return f1: field 
do [ show p1 set-text f1 "panel should be the
re!" ]] do-events

Neither the field or box will display


display "" [ p1: box 20x20 green data [] false return f1: field false 
do [show [ p1 f1 ]]] do-events

Trick is to remember that the do block is evaluated prior to the 
display being shown, so you just have to use:

	display "" [
		p: panel green data [] false
		f: field false
		do [p/show?: f/show?: true]
	]
	do-events

Thanks

but isn't the layout constructed first otherwise the variable names 
would not be available?

Yes, but doing a show or hide prior to view doesn't work.

Ok.

in lists and tables, scroll bars appear dynamicallly

Is it feasible to do the same for area widget?