World: r3wp

It enforces a minimum size window but only after you first resize 
it

it seems to be a broken exe. a new one should be distributed.

It's one I compiled myself

Also size must be a pair?  It complains if I just use an integer

Are these docs still valid? http://www.rebol.com/r3/docs/gui/guide.html

probably not for groups and panels

buttons don't change material/gradient, when pressed?

graham's code - apart from the initial window size, being collapsed, 
it also behaves strangerly resize size - the button keeps tight to 
bottom-left corner, when resizing ...

Pekr, material is early test. Just seeing if it works.

and the resizing? do we need to set some size of the screen?

There should not be any issues there.

Am I doing anything wrong? Why the button moves down = "is attached" 
to the bottom left corner?

 view [title "test" button "OK" do [print "ok"]]

try removing the title

Trying removing the title does not fix the problem, no? :-) I put 
the title there on purpose, to show the behaviour :-)

OK, when removing Title .... then my next question is - the window 
size is so small, that the button is not visible, unless I resize 
for the first time. But - Graham already reported that ....

btw - is there some easy way to list the widgets/styles available?

next possible issue - when I maximize the window - it moves up to 
the upper left corner, but then it stretches so that the window does 
surround only the button ... it should not be like that imo? But 
it depends, of course ...

there is a method to restrict the window size. perhaps it is a bit 
too aggressive, but the option is needed in some cases.

words-of guie/styles

The GUI is highly non-functional, we imo need to wait few more releases 
...

I get some leakage in the fields - strange chars .... IIRC someone 
already pointed out the issue, anc Cyphre suggested some solution 
- can't remember now ...

In clean R3 A105 session, I do following to get following image:

do %r3-gui.r3
view [field] ; resize needed to see anything ...

result:
http://www.xidys.com/pekr/rebol/a105-field-strange-chars.jpg

Any idea?

bug

'check works ... but 'radio shows some strange shape ... is that 
all due to incomplete material system definitions e.g.?

In that field, if you press backspace, do you get a crash?

only 3 styles are written for material system so far

And plese - tell me if you are interested in such hints, as it might 
get you nervous :-) We like pre-releases, but so far my feeling is 
- Gabs VID3 was able to show us Image Lab demo - resizing IIRC, drag 
and drop, alpha channels, changing mouse pointer ... then came the 
VID3.4 from Carl, it felt lightweight, but did 70% of Gabs VID? And 
now we are seing some XY percent of functionality of Carl's VID :-) 
I just hope it' still just work-in-progress, but I really wonder 
if stuff like validation is important now, in a state where there 
is very few usefull styles?

Henrik - dunno what you mean by crash - but no, R3 console does not 
crash, but I get rebol level crash:

handler added
** Script error: cannot use pick on none! value

** Where: second all resize-text-face remove-text-face switch either 
do-text-key

 if actor all do-style until either do-event do-event either applier 
 wake-up loo
p applier wait do-events if view

** Near: second get-facet face 'viewport-size tgob/size/x: face/facet...

>>

(that was caused by pressing the back-space in a field widget ....

Petr, as said: We release our stuff, it's early work and it's not 
of much use yet. But we still do it.

... but maybe I should use some precompiled R3 executable, to aviod 
possible wrong settings of my enviroment? But  - I have not found 
any in the link posted here ...

Pekr, it's ok, keep posting bugs.

As long as we don't explicitly state: Please give it a try and provide 
us feedback on A, B and C things might not work at all. you can give 
feedback but don't expect that we always care about it.

Cyphre says the bug is due to a missing box model. Will be fixed 
soon.

This is all in high flux at the moment.

ok, whatever the box model means in new gui :-)

Robert - this is OK with me. In the past, I worked with Cyphre, Romano, 
to do personal testing ... lot's of errors and misconceptions caught 
on my side. In such early phase, I might cause a flood, so if you 
want, I might stop for few more releases ...

It is just there is not much to test, if there is only 'check working 
so far for me :-)

I simply tried to go via http://www.rebol.com/r3/docs/gui/guide.html
, and to test those examples ...

so - if anyone wants - Cyphre, Rebolek, I can test privately in early 
phase, and report privately too, to not cause much of the flood here 
.... or I can simply shut-up for a while :-)

You can? ;-)

It depends ... upon what you want :-) If you want misconceptions 
or bugs reported, and you are releasing in early stage of development, 
you have to take the consequences. The same goes for us - everybody 
wants early releases, but then we complain, that released stuff is 
not of much use :-)

and the solution to this problem is... ? :)

there is no solution :-)

A106, text-test3.r - when I position caret to the last position:


** Script error: caret-to-offset does not allow word! for its position 
argument

** Where: print switch handler while applier wake-up loop applier 
wait do-events
 if view catch either either applier do
** Near: print [
    "otc:" mold otc: offset-to-caret gobt event/offs...

btw - is there any reason, why 'move events are generated, even if 
there is no mouse movement? Referring to text-tes3.r for example 
...

With a107 (that I build with the MS compiler), go.r3 seems to run 
quickly when launched, but slows down dramatically after just a little 
bit of mouse movement. If I stop moving, the speed resumes after 
a little while. I don't remember seeing this in older builds. Has 
something changed wrt event processing?

Works for me.

Are we tracking R3GUI errors anywhere??

Try this 

 view  [ button "" ]