I was actually planning on setting LM_CLICK to an integer value and then in gtkint.pp it woulds say:

case MESSAGE of
LM_CLICK : Begin
...

                        end;

etc.

I didn't come up with generic names for LM_CLICK or anything. I used LM_CHECKRESIZE etc. even though it's a bit GTK specific. We can change them later if we wish.
By assigning them a nuber, we are forced in GTKINT.PP to assign signal a string value based on that number, BUT this allows us to do this

Procedure DoClick(var msg); message LM_CLICK;

and because that's an INTEGER value we can call Dispatch instead of DISPATCHSTR . At least I think we can. That will help us remain more multiplatform because dispatchstr is what SHOULD be called......

Shane

What I meant was Dispatch is what should be called, not DispatchStr. Dispatch is used in the Window environment already so if we can use it, it seems reasonable.

Shane

Shane Miller wrote

What I meant was Dispatch is what should be called, not DispatchStr.

I knew what you meant. :-)

Dispatch is used in the Window environment already so if we can use it, it seems reasonable.

As it does to me. I haven't tried using Dispatch but I will toss together a test program to see if it works just as well as DispatchStr.

That is another good idea for the multi-API thing. This way a different file with the correct string for the API be it gtk or qt can be set for LM_CLICK and then we don't need to do the switching thing you indicated before.

Where are you at with the code. I'd like to look at it and help some more tonight but I don't want to play with code that you have already done a alot of work on. Are you at a point where you can send me a cut of the code? If so just send it to the ftp site and others can get it as well.

You can't use string constants becuase then you need recompiling of the whole application when you want an other toolkit. Using integers is a fast (a lot less string compares) alternative. You need to write for every toolkit a conversion routine:

function getmessageid(s:string):integer;
begin
  walk through a table and return the correspondenting id
end;

the table can then be sorted so a binary search maybe with some hashing can be used.

The compiler also uses such trick for all needed tokens which are futher handled like enumerated in the compiler.

Peter