World: r3wp

...and Graham seems to prefer /CONTENT if I understood it well

It's a draw, so make both available. Mayby not in this situation, 
even if more than one option can be good in many cases.

No, I've changed to /contents :)

I don't think I really voted, but I would go with 'contents as well. 
'Content seems to close to the meaning of set-face in my current 
mindset.

aha, after correcting and adding Gregg:

/CONTENT:/CONTENS = 4:6

(sorry for the typo)

It's a draw, so make both available
 - although possible in this case, it prevents unification

is it possible to find a different word?

Would it work to make update-face/contents the default, so removing 
that refinement, and add a /resize refinement for that case?

Assuming I understand the current use correctly for resizing.

aha, counterproposal:


- make the current UPDATE-FACE/CONTENTS behaviour the default, and 
for the other variant use something like UPDATE-FACE/SIZE (looks 
better than /RESIZE) to me. The trouble is, that the exception is 
the UPDATE-FACE/CONTENTS variant, since it can be used only for hpanels, 
vpanels, hgroups, vgroups, etc., while the default behaviour can 
be used for all faces.

Actually, the behaviour of UPDATE-FACE/CONTENTS called e.g. for a 
vpanel is equivalent to the behaviour of UPDATE-FACE called for a 
face contained in the same vpanel.

Is the behaviour recursive, in the sense the if a vpanel includes 
some hpanels the faces inside the hpanels are also updated?

The behaviour is recursive in that if I call UPDATE-FACE, then all 
parent panels up to the main window are updated.

(i.e. the other way than you guessed)

So if I have a vpanel which contains two hpanels and call UPDATE-FACE/CONTENT(S) 
will the contents of the hpanels be re-sized?

I was going to suggest a couple of alternatives but it is hard to 
find something that fits in with the VIEW/VID/GUI metaphors.

Two notes:

- update is not resize, but can provoke a resize as well

- if I call UPDATE-FACE/CONTENTS on a hpanel, then the hpanel is 
updated (row and column sizes are recalculated, the total panel size 
is recalculated), but the panels contained are not

As opposed to that, when I call UPDATE-FACE on the same hpanel, the 
row and column sizes are not recalculated, since there is no reason 
for that

Thanks for the explanation. You could consider:

 UPDATE-FACE/RECURSIVE (or R) which is common with cl utilities but 
 most un-REBOL like
	UPDATE-FACE/ALL - based on LOAD and SAVE metaphor
	UPDATE-FACE/CHILDREN

I'm not sure if the parent/child metaphor is appropriate in REBOL3 
GUI.

UPDATE-FACE/RECURSIVE
- this is a misunderstanding, as I said.


- UPDATE-FACE if always recursive, i.e. the it updates all the parents 
as well.
- UPDATE-FACE does not "recurse to children"

UPDATE-FACE/CHILDREN
 - a misunderstanding again, see above

UPDATE-FACE/ALL
 - a misunderstanding as well

I'm afraid that I'm a little lost - You said that UPDATE-FACE/CONTENTS 
called e.g. for a vpanel is equivalent to the behaviour of UPDATE-FACE 
for a face contained in the same vpanel.


To me the faces contained in vpanel can be considered children of 
the vpanel.

Yes, but that does not mean any children recursion, that is a parent 
recursion.

UPDATE-FACE recurses to parents.

Parent recursion means, that when I start with you, I continue with 
your parents, grandparents, etc. As opposed to that, when I do a 
child recursion, when I start with you, I continue with your children, 
grandchildren,...

That I understand. But I don't understand why you think UPDATE-FACE/CHILDREN 
would imply child recursion. For me, UPDATE-FACE/DESCENDANTS would 
imply child recursion.

aha, I was misled by the word. Now the question is, whether it will 
not confuse other people as well.

I'm confused. :-)


I agree that /SIZE is a better name, and now see the problem with 
it.


What does the docstring say for the function? That is, can we approach 
it from the documentation side and see if the functionality is clear.

I intendedly did not want to be too much function-specific, since 
the "CONTENTS issue" is present in other function/refinement names 
as well.

and, you got me, it currently does not have a docstring (maybe it 
is too low-level, but I will definitely write something)

Personally, I think that ANCESTORS, PARENT, CHILDREN  and DESCENDANTS 
are very useful words for precisely defining relative positions in 
a heirarchy.


They do not seem to sit well with the REBOL though as firstly they 
are comparative long (and many rebollers appear to worry about having 
to type one or two extra characters) and secondly they don't really 
fit in with the existing VIEW/VID/REBOL3 GUI metaphors (which are 
more facial - FACE, GOB etc.)

Any new release around the corner? This friday perhaps?

Yes, we plan to make new release this Friday. We'll post at least 
update info in case the release date is postponed from some reason.

update info: the new R3GUI release has been postponed to Monday (we 
want to solve few remaining issues to deliver more stable version) 
so stay tuned..

update: we are still working on last changes for this release...should 
be released tommorow.

Cyphre - detailed log is not updated as announced,the last items 
are dated 18.3.?

nice to see,that even View core gets updated.Thank you very much 
for improving keyboard handler!

Posted change log privately to Pekr.

ok, thanks ...

it'll be up on the site, once Robert gets around to it. I just didn't 
want to spam this group with a list.

report towards panel #32 - make the window so large, that on Y axis 
(vertical), the scroller is 100%. Then try to move the scroller (or 
press its arrow). The panel jumps in a strange way?

the same goes for horizontal axis. So the easiest way to reproduce 
it is to just maximize the window ...

It's known problem.

ok

Pekr, one thing you can check for me: Run all-styles.r3 and look 
at the FIELD style: When swiping (holding down the left button and 
dragging from left to right to mark up text) very slowly, start at 
the left 'F', the text is marked up ok, until reaching the last letter. 
Then the marking disappears momentarily and comes back when passing 
by the last letter. Can you replicate this?

I just got crash, when clicking into the field, R3 vanished.I will 
try with new session.

Henrik, other than that, marking the text is really buggy. Here's 
few things RMA needs to look into:


- go to the area, type enough text, sot  that it scrolls, and then:

        - when you are at the bottom of the area, just press shift + up arrow, 
        to hilite the text - only one line is hilited -  the alghoritm is 
        buggy

        - go to the top. Try the reverse - shift + down arrow - it hilites 
        the text correctly, unless you hit bottom, then it starts to hilite 
        from the beginning, and cycles forever. It should just stop at the 
        bottom


- the most troublesome behaviour though is, that when you move out 
from the bounds of the style, it stops hilighting. Simply an event 
flow is bad here. We should treat it like pop-up menus - receiving 
events even if outside of the window, while in mouse-down mode. That 
is absolutly needed, or the experience is highly uncomfortable - 
just try to hilite the field - once your mose goes away, it stops 
the hilite. That might be the reason why you think it is slow ...