World: r3wp

OSX is Mach-O.

Ah... so there's the rub.

Ever try an elf-to-mach-o converter?

Nope.

But I only know of one, in any case.

And that'd still need a Mach-O linker.

(Agner's "objconv" is the one I once stumbled across: http://www.agner.org/optimize/)

I'm not seeing my Dev_Event device's RDC_QUIT vector being called 
when I exit r3 with a 'q' from the command line. I do see the RDC_INIT 
vector being called.

hmm, i don't think any of the RDC_QUIT vectors are called, iirc

what are you going to use for the event device? some amiga-ism?

yes, setting up a timer at the moment

the current event device uses some windows-ism

yes

i have a dirty hack somewhere for linuxisms :)

using libevent

and integrated into the network device

the Dev_Event device has a #ifdef TO_WIN32 on it

took me a while to figure out why no events were happening... heh 
:)

do you have select(2) on amiga?

if RDC_QUIT isn't working should I file a bug report?

i think so, yes. even if it is not a bug, it'll help clarify when 
the quit callbacks are actually supposed to be called.

yes, there is select() available

I didn't think I would need it for handling gui events

won't help you much with windowing, i guess

amiga is much more like windows in that respect

you have a message loop :) ?

yes, very much like the windows one

Wait(), GetMsg(), etc.

will make porting much easier

btw.. how do I add line feeds in altme?  so everything isn't a new 
line

you click the small "pencil icon", and then send messages with ctrl-s

you can also use

(the "pencil" toggles multi-line mode)

line 1
line 2

thanks :)

do you have a window opening for the window gob already :) ?

yes I do.. just need to handle some events now so I can make it quit 
as well

very nice :)

one small step at a time

nice!

Andreas, I got this in OSX when compiling your test files:
http://cyphre.mysteria.cz/tests/osx-exports.txt

(
gcc version 4.0.0 (Apple Computer, Inc. build 5026)
Apple Computer, Inc. version cctools-590.obj~12
)

Ah, so about the same as mine.

I found this line in the host-kit when handling the closing of a 
window:

Close_Window(gob);	// Needs to be removed - should be done by REBOL 
event handling

My question is how do I do this the right way?


I think I need to do an RL_Event(EVT_CLOSE) and then somehow wait 
for REBOL to notify me. How will REBOL notify me it is ready to perform 
EVT_CLOSE?

Would CTRL-C map to the EVT_INTERRUPT event?
I'm asking because when I do this:
>> wait system/view/event-port


R3 never returns and I cannot interrupt it. I'd like to fix this 
is possible.

Esc key is supposed to interrupt it, isn't it?

Steve, on window close issue, we need to decide.


The issue is this: when use hits a close button (or causes OS-side 
close event), do we close the window at the host layer, or do we 
send an event, allowing the higher layer to pre-empt the close.

=user

Arguments can be made both ways.


The win32 code currently sends EVT_CLOSE, but also calls Close_Window().

Steve, a few comments on script interrupt...


Yes, currently, we use CTRL-C. But, it's purpose must be better defined, 
because there are really 2 types of interrupts that we want to process.