World: r3wp

I think what you have in your situation, with objects built from 
XML, is different than mine. I take advantage of being able to use 
blocks in my structure which allows me to insert my additional associated 
info. With your object hierarchy, it's problematic to add your own 
extra fields for state because the XML, of course, might already 
have those field names as part of its data, so there's possibility 
for collision there.

However, (as I see in my notes,) I was strongly considering for my 
purposes a structure like this:
		file-structure: [
			%OHS/ [
				%adir/ [
				]
				%afile
			]
		]
		associated-file-info: [
			%OHS/ make object! [...]
			%OHS/adir/ make object! [...]
			%OHS/afile make object! [...]
		]

(with duplication of all the paths as a negative consequence), but 
this idea could work better with XML objects.

Anton, have you studied what POP-DETECT in SYSTEM/VIEW/WAKE-EVENT 
is about? The function for it exists in SYSTEM/VIEW/POP-FACE/FEEL. 
To me it looks like a workaround to get DETECT to work in INFORMs.

Maybe I've had too little coffee, but I can't figure out why no text 
is displayed here:

view center-face make face [text: "test"]

but 'size-text returns 22x15

the top level face is the window face. text is for the window title.

ah, that's right. I wonder then if that's what is causing problems 
with SIZE-TEXT for a specific face I'm making. SIZE-TEXT consistently 
returns pixel sizes that only fit if the font size is around 10 or 
11.

where exactly are iterated faces evaluated? is that internal in view?

AFAIK, it's internal in View.

Thanks

When reading through the View Reference, it's not clear what happens, 
when you return an integer from the iteration function. I can see 
the iteration function is run again with that value as input, but 
I can't tell where it's run. I had hoped to redraw single lines in 
a list with a simple mouse over, but I guess you need to do something 
unknown to provoke the redraw.
Using SHOW in the function causes an infinite loop.

The answer to all these kinds of questions/problems with iterated 
pane functions, I, and beforehand others like Romano and Gabriele, 
discovered, after much investigation, is not to use a pane function 
at all, but instead, make real faces in your window and manage them 
yourself. It turns out to be simpler and easier to code, and with 
events, it is more powerful, reliable and has fewer limitations etc.

So... the pane function may be interesting to investigate, but you 
may also just waste a lot of your time.

Anton, yeah, I might drop it, although I figured out a solution to 
that problem there are many other problems. However right now I'm 
investigating SHOW-POPUP and HIDE-POPUP, trying to see if I can control 
many popups for a menu system.

trying to figure out now when exactly it is that View displays a 
button for the window in the task bar and when it doesn't.

I purchased the Rebol-Command and am trying to integrate it with 
my existing work.  The 'Local' folder is pointing to 'c:\documents 
and settings\blah\blah....   My old version was pointing to c:\rebol\local 
 thats where I want it to point.  Is there a way to force it there? 
 TIA

Analyse:
Put this in your  user.r  file:

	print ["system/options/home:" mold system/options/home]

A probable fix for you (insert into user.r):

	system/options/home: %/c/rebol/

Thank you.  After a rest and some more digging I found a few ways 
to fix.  The most obvious - which I overlooked - was a prompt during 
the installation.   I like everything in one root folder.  Much easier 
to sync between home/work/laptop etc.  Just to be extra safe, I added 
the code you proposed.  Thanks again.

Actually, I only set system/options/home in my user.r because I'm 
on linux which doesn't have a registry.

On Windows, you can find the registry key which sets system/options/home 
by searching for "rebol" in the registry. (I don't remember what 
it is exactly, but it's easy to find.)

Finally found it.  For anyone else that would like to know where 
this key is located:  It  is HKEY_CURRENT_USER / SOFTWARE / REBOL 
/ VIEW / SANDBOX   There are two keys 'Home' and 'Sandbox'  I found 
for now the best setting for my environment is to set them both to 
C:\rebol\bin

I think that forces everything to run out of the bin and lower directories. 
 The 'home' key I believe tells rebol where to find the 'desktop' 
parameters.

Is there an easy way of how to resize an image? I tried:

i1: load %my-img.png
i2: make image! 82x63 i1

but the image is black :-)

DRAW or use effect [fit] in view

Untested, but should work :

i1: load %my-img.png
i2: make image! 82x63
draw i2 [image i1 0x0 82x63]

thanks, will test ...

Pekr, if you use DRAW to resize it, the result will be anti-aliased, 
just using view and it won't.

works, thanks. I just wanted to test, how does REBOL resize. It is 
the same catastrophe as IE. Kudoz to FF ...

Geomol - how do I do it using View?

i2: to-image layout [image i1 82x63 effect [fit]]

DRAW allows upward bilinear filtering, but not downward. VIEW simply 
uses nearest neighbor.

What I need is smaller PNG, because SharePoint just sends original 
image to browser, instructing it to resize. IE is pretty much ugly, 
FF is OK. I tried in xnView, my friend in IrfanView, no matter what 
we do, we can't save so that it preserves transparent color ...

Forget using REBOL for that, if you want to preserve quality.

I'm not sure, if view preserves transparent!?

I think, you can preseve transparent by making a separate image from 
the alpha channel, resizing rgb and alpha separately and combine 
them in the end to a final image.

(If it's a problem otherwize.)

How much work is involved in getting linux view to work on the ARM 
processor?


I see core running on ARM, Dec-Alfa, Sparc etc and even linux view 
runs on X86 and PPC.


Does the graphics side of view need to deal with teh processor or 
does the OS its riding on take care of that part?


I see some cheap UMPC's with touch screens that I would love to put 
my app on but they are ARM base and run CE or Linux....

It it just a matter of a recompile for that processor and OS?

Does anyone know how to set the selected rows programatically within 
a text-list?

>> main: layout [tl: text-list data ["line 1" "line 2" "line 3"]]
>> insert tl/picked "line 2"
>> view main

I look in the style and not the documentation, when finding out these 
things. Like:
>> ? tl
Then I notice picked.

Geomol, thanks. It must be some weird user error because I thought 
I tried that and it didn't work. Thanks.

Next question (sorry). I need to make a requestor a little more sophisticated 
than the default ones. I already have a main window opened. I need 
to open this requestor on top but wait for user input. I've fooled 
around with do-events and show-popup but not getting the needed behavior.

try inform...its modal

You can create basically any type of layout you need and it stays 
on top until user reacts to it...

Use hide-popup to close inform window

Perfect. Thanks.

My only beef with inform is that It is not so easy to impliment a 
window without border or title bar...I'm sure its possible but I 
have not looked into it too deep...

That's true. Congratulations on your FDNY project. and speaking of 
window titles, Nick A wrote a nice script for changing titles in 
a windows environment: http://www.rebol.org/view-script.r?script=title-bar.r
(unless you really like having "Rebol" in the title bar.

just discovered a nasty bug in view event handling...  anyone found 
a way to solve the following:


if you remove a face from a layout within the action of that face, 
its "away" engage feel gets stuck until you click on something... 


everytime you hover over something else, its away function is called 
even though its not even displayed in the view anymore!

I suppose one would ask in the away function about visibility, but 
I guess that doesn't stop the away function from being run.

exactly.

I remember something like that. When you click down, the View system 
has to remember which face you clicked down on. In my DO-EVENT simulation, 
I called this face the "down-face". It remembers this face so that 
it can send subsequent "drag" (away/over) events to it, until the 
up event. Obviously it takes no account of whether the down-face 
is still in the layout or not. Pity, isn't it?