The Windows.pp file should be used in both Linux and Windows.  If not, then

1) I need to put a {$IFDEF} in before the uses clause to remove the windows unit
2) How are yuou going to call some of these procedures when you are using windows? Remember, you DON'T have the delphi windows.pas file UNLESS you are writing your Apps under Delphi!

The Windows.pp file has to be made for both environmewnts and has tro contain a {$IFDEF LINUX} or {$IFDEF WIN32} or something to that effect.

Shane

>> Florian Klaempfl 10/26/99 07:29AM >>>

But don't name it windows.pp! This will lead to conflicts with existing the windows.pp. What about a simple lclbase.pp?

_________________________________________________________________ To unsubscribe: mail with
"unsubscribe" as the Subject
archives at http://www.miraclec.com/list_archives/lazarus

Shane Miller wrote

In the MWEDIT source, they call some WINAPI calls like GETKEYSTATE and

STRINGOFCHAR.

Where should I put these? MWEDIT expects them in a windows.pas (or .pp)

file but I would assume that once we write them, we would allow Linux users to use them so I could put them in a linux.pp file, but them mwedit doesn't find them.

Any simple way around this? Should I just write it twice, once in the

windows.pp file and once in the linux.pp file because you would assume that if they are using windows.pp they WOULDN'T be using Linux.pp

Nah, I dont think this is the way. I t should be just one file. This way you introduce platform specific files. Maybe we can see it as an (OS)windows file in stead odf an (MS)windows file ?

Marc

In the MWEDIT source, they call some WINAPI calls like GETKEYSTATE and STRINGOFCHAR.

Where should I put these? MWEDIT expects them in a windows.pas (or .pp) file but I would assume that once we write them, we would allow Linux users to use them so I could put them in a linux.pp file, but them mwedit doesn't find them.

Any simple way around this? Should I just write it twice, once in the windows.pp file and once in the linux.pp file because you would assume that if they are using windows.pp they WOULDN'T be using Linux.pp

Shane

But windows.pp already exists for Windows. Thus you must make a replacement file for linux only, and it should be compatible with the existing win32 windows.pp

So any lazarus app compiles both on windows and linux, with a minimal overhead... Although I think that on the level of lazarus (LCL) there should NEVER be a dependence on Windows or Linux. Just GTK/Qt/win32 for the low-level gui calls and sysutils or low-level classes for all other stuff.

Michael.

I actually just about have Win32 working now with the stuff that we have. I was having a problem or two last night with the event stuff but I belive I should have that working tonight. Jeff has to pass a dart tonight so I will continue to refine that this evening and pass that off. He can then take what I gave him and run with it or do something different("up to him")..

We are going to need winproc for both this and the QT engine. Soon as I pass some clean code to Jeff I am going to go back into Linux and finish the QT engine.

This will give everyone Linux GTK, Linux QT, Win GTK, Win Native, Win QT ("not free")..

What more could you ask for?. Don't answer that ;)...

Cliff

But don't name it windows.pp! This will lead to conflicts with existing the windows.pp. What about a simple lclbase.pp?

Don't like this idea.

>>> Michael Van Canneyt 10/26/99 08:41AM >>> But windows.pp already exists for Windows. Thus you must make a

replacement >file for linux only, and it should be compatible with the existing win32 >windows.pp

Yes, the file exists, but why can't we use it for MSWindows as wal as Linux ?

So any lazarus app compiles both on windows and linux, with a minimal

overhead...

Although I think that on the level of lazarus (LCL) there should NEVER be a dependence on Windows or Linux. Just GTK/Qt/win32 for the low-level gui calls and sysutils or low-level classes for all other stuff.

So..... one file

Marc

Never create a file with the same name as a unit in the RTL/FCL it'll only create a lot of confusion.

just name the file soemthing like: 'lclwin' and 'lcllinux' if you really need such files.

Peter

Oh, I didn't know Windows.pp existed already....

I guess the best way around this then is to create a Linux.pp file and add a

{$IFDEF LINUX}
uses blah blah, blah;
{$ELSE}
ues blah,windows,blah;
{$ENDIF}

Shane

>> Michael Van Canneyt 10/26/99 08:41AM >>>

But windows.pp already exists for Windows. Thus you must make a replacement file for linux only, and it should be compatible with the existing win32 windows.pp

So any lazarus app compiles both on windows and linux, with a minimal overhead... Although I think that on the level of lazarus (LCL) there should NEVER be a dependence on Windows or Linux. Just GTK/Qt/win32 for the low-level gui calls and sysutils or low-level classes for all other stuff.

Michael.