I will add it. I was sent a patch and it must have created that file and I mustn't have added it. Sorry, my fault, I'll see if that's the case...

------------------------------------------------------------ Shane Miller

Home page : http://www.lakefield.net/~smiller

Auto-IP Publisher : http://www.lakefield.net/~smiller/autoip

Advanced Clipboard : http://www.lakefield.net/~smiller/advclipboard

Lazarus : http://www.pcpros.net/~vbman
----------------------------------------------------------

I had the same problem. The only way I could get it to compile, so I could work, was to comment out all the listbox interface definition and the include.

I also noticed two new units, gtklistsl.inc and gtklistslh.inc. What are these? They are done completely different than all the rest of the components (they are a GTK specific listbox). Was that done for a reason? Or is it just some work code?

Michael, do you need us all to change our components to work with the new SendMessage layout?

Also, we should probably rename the stdcontrols unit to stdctrls so it matches Delphi. Just one more easy thing we can do to provide more compatibility. Don't you think? I can do it if everyone agrees.

Curtis

----------------------------------
Curtis White
Curtis White
http://www.teleport.com/~osiriz/
----------------------------------

What is the story with customlistbox.inc? I have made some major changes to the SendMessage layout to combine everything into just one routine called from just one location. However I can get past this .inc file to test my code before committing. When can we expect it to be placed into CVS?

Curtis White wrote

I had the same problem. The only way I could get it to compile, so I could work, was to comment out all the listbox interface definition and the include.

I did the same thing as a temporary measure.

Yeah I saw that myself. I didn't get a change to look at it yet to see what it is doing. I will as I move the gtk stuff to a separate directory.

Michael, do you need us all to change our components to work with the new SendMessage layout?

The change is simple. I have incorporated a change in all the code (except notebook just didn't get to it yet). All of the InterfaceObject.IntSendMessage and ..2 and ..3 calls have been boiled down into one call

function SendMessage(themessage : integer, Self : TObject, data :
pointer) : integer;

This is a global function placed in controls.pp. Since just about every unit uses this unit this should always be available. So as long as you just placed uses controls in your unit you can call the above procedure. This means that controls.pp should be the ONLY unit that will need to reference the interfaces unit. I want to get this separation so it will be easier for me to redo the current layout and move the gtkint stuff down into a subdirectory.

The SendMessages is just a combination of IntSendMessage2 and IntSendMessage3. It returns an integer value. If you are written NEW code that needs to send a message place it in the IntSendMessage3 method in gtkobjects.inc. I have moved most of the IntSendMessage2 messages over to IntSendMessage3 but check over the next day or so if you need to call something that you know was originally in IntSendMessage2. I might be about a day before I get it all cleaned up and moved over.

So to answer your question, no you don't have to change your components I have already done so or am doing so.

Also, we should probably rename the stdcontrols unit to stdctrls so it matches Delphi. Just one more easy thing we can do to provide more compatibility. Don't you think? I can do it if everyone agrees.

Might not be a bad idea but let's not touch that one for now. Give it a few days for alot of these changes to settle down.

JFYI....

I did manage to get a production server up running a search engine called htdig. It seems that htdig has been around for some time. It was a extrememly easy to install package and does one outstanding job of indexing web content. The indexing tool is made to work against web server content spread across multiple domains. I just gave it our internal web servers and our external hosted web sites and it indexed the whole deal in 3 minutes. It has a web interface almost identical to infoseek complete with hit ranking.

Nice product if you ever need a web search engine and very quick to get up and running.

And yes of course it just runs on linux. I can honestly say we at work are turning into a serious Linux Shop. The bosses are amazed at the stability, speed and flexibility of these linux boxes.

Cliff

Cliff

Curtis White wrote

Do you think we should make the data parameter a "var"? The reason I ask is what if we need it to pass back some info? Or can it pass back info anyway because it is a Pointer?

If it is a pointer, then there should be no problem passing data back if the pointed to structure is known. If you make it a Var, then it would be possible to change the pointer, and that could be dangerous.

Jeff.

Do you think we should make the data parameter a "var"? The reason I ask is what if we need it to pass back some info? Or can it pass back info anyway because it is a Pointer?

Curtis

Oh, yea, that would be very bad.

Curtis

Curtis White wrote

Do you think we should make the data parameter a "var"? The reason I ask is what if we need it to pass back some info? Or can it pass back info anyway because it is a Pointer?

It already sends back an integer so you can send back simple stuff in that manner. However as you point out the data variable is a pointer to a record or block of memory that you are passing to the interface routines. It would be very easy to just allocate some fields in the record to be filled out by the interface routines so upon return you could optain the results from your record/message block.