Shane Miller wrote

I added code for TBitBtn. To look at it, compile lazarus and run it. A OK button appears. Simply select Project BUILD and PROJECT RUN to switch between propertys of the button. Run changes the type of button it is and BUILD changes the layout.

After PROJECT-->RUN , and pressing the button it ends in a segmentation fault.

BTW I understand your transparent drawing, but loading a transparent pixmap won't help here :-(
You can check this by changing '. c #D5D6D5', into '. c None', in the defaultbitbtnimages.inc.

Marc

I added code for TBitBtn. To look at it, compile lazarus and run it. A OK button appears. Simply select Project BUILD and PROJECT RUN to switch between propertys of the button. Run changes the type of button it is and BUILD changes the layout.

I have a bit to code yet, like setting the modalresult and such but it seems to work pretty well at this point. I am storing the check, X, and the door images in the include file defaultbitbtnimages.inc. I didn't know where to put them for now and I didn't want to have to LOAD them from disk.

Shane

Marc Weustink wrote

At 14:25 30-03-2000 -0600, Shane Miller wrote: >I have moved all the gtk files into the lcl/gtk directory and all the >win32 files into the win32 directory

BTW, wouldn't lcl/interfaces/gtk and lcl/interfaces/win32 be a better location ?

Marc

I suggest to do that shortly after we have tackled this one. (A day or so)

Marc

Excellent idea. Can you or Marc figure out where to put eveything please. I am leaving for Kentucky tomorrow to go on a golfing vacation. I will be back on Wednesday.

Shane

>> 03/30/00 03:29PM >>>

Shane Miller wrote

I really wanted this to get done prior to us getting more people involved. Marc, when you fix the make files, move everything to Interfaces/gtk and win32. I am fine with that.

Why don't we separate the .inc's and .pp's while we are at it? This will help in some aspects when the code in the .inc's might be windows specific. By linking against the correct .inc directory we then don't need to use #ifdefs. You know the way that the FCL is set up.

We might as well get everything setup correctly right now.

I did implement drag/drop via gtk and it worked fine. I guess I wanted to experiment with keeping it all inside the LCL so each widget set didn't need to support drag and drop because we were handling it internaly. I agree it would be easier to just add the gtk_signal_connet calls when the controls are created and go with that......

As a matter of fact look at the creation of the csedit control. I have the drag and drop stuff commented out there, but you can see it's pretty easy. the other code is in the gtkdragcallback file.

Shane

>> 03/30/00 02:47PM >>>

It appears that the best way is using the DND built into GTK+ and Qt.

http://developer.gnome.org/doc/API/gtk/gtk-drag-and-drop.html

Since it already has all of the required signals can't we just go for it?

In regards to Sam and FEdit, have we heard from him lately? I'm interested in whether he wants to use FEdit to do the form designer and Object Inspector. I certainly don't want to tackle those at this time. :-)

He unsubscribed from the list on March 6th and I can't see any record of someone with a similar name subscribing after that.

HEY SAM!!! Are you on the list yet?

How will this tie in with the existing D&D already in GTK and Qt? If it is implemented in the LCL won't that just work within the application built with the LCL? How will it tie in with D&D to other applications?

Good question. I wasn't thinking that far ahead yet. See, in windows you can capture the mouse messages so that a form is getting those messages at all times, whether the mouse is within the control or not. In linux, I'm not sure how to do that yet. If I could then I would simply watch for the MouseUp and see if I was dragging. If so then I would get the data of the item I was dragging and send a DRAGDROP signal to the target window.

I am not that well versed with the drap and drop yet though so I will have to look into this a bit further.

In regards to Sam and FEdit, have we heard from him lately? I'm interested in whether he wants to use FEdit to do the form designer and Object Inspector. I certainly don't want to tackle those at this time. :-)

Shane

Shane Miller wrote

I have moved all the gtk files into the lcl/gtk directory and all the win32 files into the win32 directory.

Daahhh, I was just thinking of when and how we should do that. I've still some changes pending..

I think they should be remeoved as soon as possible, now there are two instances. I'll try to look at the makefiles, otherwhise we have to compile lazarus without them for a while.

Marc

This is something I said I'd do and wanted to do for months but never could figure out when was a good time to disturb the whole works to make the move.

I guess it's now. :-)

I would recommend all work stop until the make file is cleaned up and everything moved. If we are getting people interested we want the code in order and I will then need to modify the How-To's so people can get the files correctly.

Let me know when you have modifed the make and everything is changed so I can work on the How-To docs.

Also be sure to post it in the Developer News.

I added some drag and drop code. Not finished yet. Also I added code so when you saved a unit as a different name it would try and change that name in the unit source itself. Fails if you trick it with {unitname}
before the actual name. It simply parses for the unit name at this point.

Also, I had to change our SendMessage function call to CNSendMessage. The reason for this is that Windows has a SendMessage call that's not compatable with our and it can't be overridden because only class methods can be overriden.

CN stands for Control. I just pulled that out of my #$@ so if anyone NEEDS it changed to something else let me know otherwise lets just leave it.

The drag and drop support I added previously I was using gtk widget's drag/drop support. I think we should do something similiar to what Delphi did and support our own based on the WM_MOUSEMOVE and MOUSEUP/MOUSEDOWN calls.

That's all for now.
Shane

Shane Miller wrote

I really wanted this to get done prior to us getting more people involved. Marc, when you fix the make files, move everything to Interfaces/gtk and win32. I am fine with that.

Why don't we separate the .inc's and .pp's while we are at it? This will help in some aspects when the code in the .inc's might be windows specific. By linking against the correct .inc directory we then don't need to use #ifdefs. You know the way that the FCL is set up.

We might as well get everything setup correctly right now.

I don't believe I know enough about how it works at this point to answer your question. Yes, we could use a TComponent that could answer all these questions but I don't know how it would know it's children's (a TEdit's for example) methods and such.

I just don't know enough about this at this point.

BTW, welcome to the list and feel free to try and help out. Take your time and ask lots of questions!

Shane

>> 03/30/00 03:41PM >>>

I have a question for you: We need some kind of framework to be able to do this kind of work, right ? i was thinking maybe we need to have a TComponent that knows how to respond to something (messages?methods?) and describe itself (properties, methods, childrens and so forth). If we Had such a structure, it would make it easier to build a "component inspector"-like window. By parsing the source we can get the list of component that where created by the IDE (build/update a XML file for instance), rigth? and then create all the components from there (let the "Inspector" build a list of all the components (and build them) -- =probably not too hard-- and teach it how to read/change properties -- =hard part-- )

Did anyone started some "theory" on how all this would fit together ? (sorry for not participating a little bit more, but i'm having trouble understanding everything in there, but since it looks more and more like delphi, i hope i'll be able to contribute soon -:> )

Jok

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

Probably a good idea.

How will this tie in with the existing D&D already in GTK and Qt? If it is implemented in the LCL won't that just work within the application built with the LCL? How will it tie in with D&D to other applications?

Maybe it will I am just checking. :-)

I have moved all the gtk files into the lcl/gtk directory and all the win32 files into the win32 directory.

A new entry needs to be added to your ppc386.cfg file in /etc

-Fu/usr/lib/fpc/lazarus/lcl/gtk
(depending on your base directory)

Also the makefiels need to be modified. Can someone modify them please! I haven't deleted the files outr of LCL until the makefiles get modified. Could someone do this then remove the gtk files out of the lcl directory from CVS

Thanks
Shane

I have a question for you: We need some kind of framework to be able to do this kind of work, right ? i was thinking maybe we need to have a TComponent that knows how to respond to something (messages?methods?) and describe itself (properties, methods, childrens and so forth). If we Had such a structure, it would make it easier to build a "component inspector"-like window. By parsing the source we can get the list of component that where created by the IDE (build/update a XML file for instance), rigth? and then create all the components from there (let the "Inspector" build a list of all the components (and build them) -- =probably not too hard-- and teach it how to read/change properties -- =hard part-- )

Did anyone started some "theory" on how all this would fit together ? (sorry for not participating a little bit more, but i'm having trouble understanding everything in there, but since it looks more and more like delphi, i hope i'll be able to contribute soon -:> )

Jok

That's fine with me.

Also if you have changes to be made, commit them. As I said, I didn't delete the old files I simply started adding the new ones.

I really wanted this to get done prior to us getting more people involved. Marc, when you fix the make files, move everything to Interfaces/gtk and win32. I am fine with that.

Make that change as soon as possible and we can then start changing the How-To's and such. There shouldn't be many changes needed.

Sorry for the surprise move but I wanted it done prior to getting more people developing here. We need some organization of the files so they are easier to read. It's tough running through the entire directory of LCL looking for a file sometimes.

Thanks
Shane

>> 03/30/00 03:03PM >>>

Marc Weustink wrote

At 14:25 30-03-2000 -0600, Shane Miller wrote: >I have moved all the gtk files into the lcl/gtk directory and all the >win32 files into the win32 directory

BTW, wouldn't lcl/interfaces/gtk and lcl/interfaces/win32 be a better location ?

Marc

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

.. but I'am working on it in a seperate cvs branch.

It appears that the best way is using the DND built into GTK+ and Qt.

http://developer.gnome.org/doc/API/gtk/gtk-drag-and-drop.html

Since it already has all of the required signals can't we just go for it?

In regards to Sam and FEdit, have we heard from him lately? I'm interested in whether he wants to use FEdit to do the form designer and Object Inspector. I certainly don't want to tackle those at this time. :-)

He unsubscribed from the list on March 6th and I can't see any record of someone with a similar name subscribing after that.

HEY SAM!!! Are you on the list yet?

gdk_pointer_grab (if I've read it correctly)

As far as I have seen only parts of it are usable. I don't know if we should (or can) use the design interface like borland did in D3. Like D4 ii is impossible since they use interfaces (and AFAIK fpc doesn't support interfaces)

I certainly don't want to tackle those at this time. :-)

Maybe, if I'm finished with the current work on the graphics

Marc

Shane Miller wrote

Excellent idea. Can you or Marc figure out where to put eveything please. I

lcl/include ??

am leaving for Kentucky tomorrow to go on a golfing vacation. I will be back on Wednesday.

Have fun

Marc

I think we have to use a mixture of both.

Marc

Marc. I'll work up a layout and organization for the files tomorrow. As soon as the interfaces stuff is cleaned up we can then move the .inc's.