World: r3wp

When designing GUI elements: Devil is in the details ;)

That's why people love markup languages

eh ? they do ?

Quick question, how do you force a resize event?

use the mouse?

Is there any other way?

Do you to inject a resize event into View's event handler?

Isn't a resize event without a resize just a repaint?

Not sure what you mean, either:

  view lay: layout [btn "Resize" [lay/size: 400x400 show lay]]

or

  my-evt: make event! [type: 'resize]
  system/view/wake-event my-evt  ;-- doesn't work, another way?

or


  do-on-resize: func [f e][if e/type = 'resize [alert "Resize!!!"] 
  e]
  insert-event-func :do-on-resize
  view lay: layout [btn "Resize" [lay/size: 400x400 show lay]]

are there good articles on memory conservation anywhere? I noticed 
that some times memory usage for LIST-VIEW skyrockets, especially 
when using TO-IMAGE on list columns to generate bitmaps. that is 
not good.

Yes, to-image always produces a new image. There's no way to render 
into an existing image, as far as I know. (Would like that.)

how do you bind layout words to an object easily? I want to set faces 
to variables which are supposed to be local to the context of my 
Tester program. I realize this is really the old "dynamic variable 
list in an object problem" all over again (I run into this very often 
it seems), but was wondering if LAYOUT specifically allowed some 
tricks...

see Avoiding Variable Collisions in http://www.rebol.com/docs/view-guide.html#section-13, 
I guess that is what you are asking for

I was afraid that is what I needed to do :-(

what is wrong with that approach?

because I have quite a lot of variables

(I can suggest improvements)

aha, you do not want to "duplicate" declarations?

well the thing is how variables are initialized when doing an object. 
I've discussed this before, but it would be nice to keep the list 
shown at the top of that example in the docs as a dynamic list. this 
prevents me from having to maintain that list and the layout words 
when doing changes. I guess I need to approach how to make the object 
block differently.

I am wildly trying to guess what you want, although you are not making 
it easy for me :-). Let's see my CFOR function as an example:

well, I may just be going about this backwards

>> cfor [i: 1] [i <= 3] [i: i + 1] [print i]
1
2
3
== 4
>> i
** Script Error: i has no value
** Near: i
>>

is this pattern what you want to be able to do?

well, that's a local variable alright, but this is for an object. 
I think I have a different solution though, so I think you should 
wait with wasting more time on it.

this is for an object
 - it does not matter at all

you just need to know what you want

I know what I want :-) I just need to find out a solid way to solve 
the problem permanently

the solution already exists, see http://www.fm.tul.cz/~ladislav/rebol/contexts.html#section-22
or http://www.fm.tul.cz/~ladislav/rebol/cfor.r

(and http://www.fm.tul.cz/~ladislav/rebol/set-words.r)

ok, how do you then do that for an object?

the way I see it, I need to create the object block with layout blocks 
first. then analyze those layout blocks for set words and finally 
create a new block with the set words set to none and append the 
object block afterwards

how do I do it for an object? - the http://www.fm.tul.cz/~ladislav/rebol/contexts.html#section-20
does it for an object when simulating how an object is created

CFOR function does it for a block, LFUNC does it for a function, 
it is quite easy actually

am I correct that set-words is not recursive?

nevermind, made it recursive myself :-)

I wanted to stay compatible with the way how objects work, that is 
why I didn't make it recursive, but it is easy to change

Lad, when you shadow a variable how do you access the top level one? 
In the CFOR example i showdows any system i.

http://www.colellachiara.com/soft/libs/utility.r

look at the vid-context function

I am using e.g. use [a] [print system/words/a]

Anyone remember a way to change the appearance of the caret ?

Anton, I'll bet you mean something other than "system/view/caret: 
 some-txt"

Yes, not the position of the caret, I mean the thickness of the text 
insertion point, otherwise known as the caret.

But I've moved on to another puzzle:

>> view layout [base-text "hello" with [focus self]]
** Script Error: Invalid graphics face object
** Where: focus
** Near: show face

view layout [field field "hello" with [focus self]]   ; OK

Anyone know what parameters are expected by local-file-request ?

You can see local-request-file used in request-file.

Yes, that's where i saw it.

I remember fiddling with it ages ago but I can't remember anything 
now.. :)