Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 1999-12

CVS Update

26 messages · 6 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Michael A. Hess
to Shane Miller: Currently when compiling I do a ppc386 -b -B -g lazarus.pp when I want to debug it but I…
Shane Miller wrote 6 lines
Currently when compiling I do a ppc386 -b -B -g lazarus.pp when I want to debug it but I still can't peek at variable values as it says that the symbol information isn't there. What am I doing wrong?

Did you build EVERYTHING with the -g? If not you need to rebuild the LCL using -g.

==== Programming my first best destiny! ==== Michael A. Hess Miracle Concepts, Inc. http://www.miraclec.com

Reply by email

Marc Weustink
to Shane Miller: Currently when compiling I do a ppc386 -b -B -g lazarus.pp when I want to debug it but I…
Shane wrote 5 lines
Currently when compiling I do a ppc386 -b -B -g lazarus.pp when I want to debug it but I still can't peek at variable values as it says that the symbol information isn't there. What am I doing wrong?

You mean you want to watch locals within a procedure --> type the name in uppercase.
If you want to watch membervars, for instance FList, type this->FLIST

Marc

Reply by email

Marc Weustink

Hi, cvs is updated

Fixed some samples
Fixed Dialog parent is no longer needed
Fixed (Win)Control Destruction
Fixed MenuClick

Marc

Reply by email

Shane Miller

It doesn't paint any text to the editor because I believe it looks to see if the HIGHLIGHTER property is assigned before repainting.

Shane

>> 12/07/99 06:23AM >>>

To get at least something showing, I commented out the TmwPasSyn stuff (two lines).
For now, not all events are working, but will in the near future.

Another problem is that the editor won't show lines when you use Lines.Add. You can see this in the debug output (a lot of painting, but no trace of ExTextOut)
I expect that this is because some API functions aren't implemented yet (notice in the output a linedraw from (largeint, largeint) to (250, 0)) and the visible part for the editor is way beyond the lines just added.

Marc

+ From: Marc Weustink
+
+ Changed a lot to get things more stable.
+
+ Marc
+
+ Removed some double events
+ Changed location of SetCallBack
+ Added call to remove signals
+ Restructured somethings
+ Started to add default handlers in TWinControl
+ Made some parts of TControl and TWinControl more delphi compatible
+ ... and lots more ...
+

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

Reply by email

Shane Miller

Got further!!!. I added the mwPasSyn1 back into mwEdit. For those unaware, mwPasSyn1 is the syntax highlighter for mwedit. Without it, the text is just plain old text.

I added it back and found it crashed again in NULLPROC. When I went into debug (DDD) I found that I got into the procedure but THIS = 0x0. Odd......then I noticed that when FProcTable was assigned to NullProc it was assigned by doing this:

FProcTable[I] := NullProc;

This is the correct way of doing it, but it doesn't work for FPC. I was surprised it compiled!!!! I changed it to

FProcTable[I] := @NullProc;
and it worked.....I need to change a few other things but we are further.

Shane

>> 12/07/99 07:43AM >>>

+ From: Shane Miller
+ Sent: Tuesday, 07 December, 1999 14:32
+
+ It doesn't paint any text to the editor because I believe it
+ looks to see if the HIGHLIGHTER property is assigned before
+ repainting.
+
+ Shane
+

?? and it does when setting Lines.Text ?? ... OK !

Marc

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

Reply by email

Marc Weustink

Changed a lot to get things more stable.

Marc

Removed some double events
Changed location of SetCallBack
Added call to remove signals
Restructured somethings
Started to add default handlers in TWinControl
Made some parts of TControl and TWinControl more delphi compatible ... and lots more ...

Reply by email

Shane Miller

updated CVS with the new changes. No noticable difference except it doesn't crash...

weus,
When we compile in {$mode Ddelphi} we get some other errors. I don't remember what they are off hand though. Sorry. Shane

>> 12/07/99 02:05PM >>>
you wrote 13 lines
Got further!!!. I added the mwPasSyn1 back into mwEdit. For those unaware, mwPasSyn1 is the syntax highlighter for mwedit. Without it, the text is just plain old text. I added it back and found it crashed again in NULLPROC. When I went into debug (DDD) I found that I got into the procedure but THIS = 0x0. Odd......then I noticed that when FProcTable was assigned to NullProc it was assigned by doing this: FProcTable[I] := NullProc; This is the correct way of doing it, but it doesn't work for FPC. I was surprised it compiled!!!!

Hmm.. I cant see why. But isn't this introduced by the fact that we are compileing in {$mode objfpc}.
I probably missed it, but why aren't we using {$mode delphi} ??

Marc

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

Reply by email

Marc Weustink
to Marc Weustink: Changed a lot to get things more stable. Marc Removed some double events Changed location…

To get at least something showing, I commented out the TmwPasSyn stuff (two lines).
For now, not all events are working, but will in the near future.

Another problem is that the editor won't show lines when you use Lines.Add. You can see this in the debug output (a lot of painting, but no trace of ExTextOut)
I expect that this is because some API functions aren't implemented yet (notice in the output a linedraw from (largeint, largeint) to (250, 0)) and the visible part for the editor is way beyond the lines just added.

Marc

+ From: Marc Weustink
+
+ Changed a lot to get things more stable.
+
+ Marc
+
+ Removed some double events
+ Changed location of SetCallBack
+ Added call to remove signals
+ Restructured somethings
+ Started to add default handlers in TWinControl
+ Made some parts of TControl and TWinControl more delphi compatible
+ ... and lots more ...
+

Reply by email

Marc Weustink
to Shane Miller: Got further!!!. I added the mwPasSyn1 back into mwEdit. For those unaware, mwPasSyn1 is…
you wrote 13 lines
Got further!!!. I added the mwPasSyn1 back into mwEdit. For those unaware, mwPasSyn1 is the syntax highlighter for mwedit. Without it, the text is just plain old text. I added it back and found it crashed again in NULLPROC. When I went into debug (DDD) I found that I got into the procedure but THIS = 0x0. Odd......then I noticed that when FProcTable was assigned to NullProc it was assigned by doing this: FProcTable[I] := NullProc; This is the correct way of doing it, but it doesn't work for FPC. I was surprised it compiled!!!!

Hmm.. I cant see why. But isn't this introduced by the fact that we are compileing in {$mode objfpc}.
I probably missed it, but why aren't we using {$mode delphi} ??

Marc

Reply by email

Peter Vreman
to Shane Miller: Currently when compiling I do a ppc386 -b -B -g lazarus.pp when I want to debug it but I…
Show quoted text 9 lines
>Currently when compiling I do a > >ppc386 -b -B -g lazarus.pp when I want to debug it but I still can't peek at >variable values as it says that the symbol information isn't there. >What am I doing wrong? You mean you want to watch locals within a procedure --> type the name in uppercase. If you want to watch membervars, for instance FList, type this->FLIST

All variables/procedure names should be uppercase. And you need to prefix 'this.' (that could be skipped if the langauge is C++) instead of 'self' when viewing object fields.

Peter

Reply by email

Shane Miller

Currently when compiling I do a

ppc386 -b -B -g lazarus.pp when I want to debug it but I still can't peek at variable values as it says that the symbol information isn't there. What am I doing wrong?

Shane

>> 12/07/99 12:17PM >>>

Got further!!!. I added the mwPasSyn1 back into mwEdit. For those unaware, mwPasSyn1 is the syntax highlighter for mwedit. Without it, the text is just plain old text.

I added it back and found it crashed again in NULLPROC. When I went into debug (DDD) I found that I got into the procedure but THIS = 0x0. Odd......then I noticed that when FProcTable was assigned to NullProc it was assigned by doing this:

FProcTable[I] := NullProc;

This is the correct way of doing it, but it doesn't work for FPC. I was surprised it compiled!!!! I changed it to

FProcTable[I] := @NullProc;
and it worked.....I need to change a few other things but we are further.

Shane

>> 12/07/99 07:43AM >>>

+ From: Shane Miller
+ Sent: Tuesday, 07 December, 1999 14:32
+
+ It doesn't paint any text to the editor because I believe it
+ looks to see if the HIGHLIGHTER property is assigned before
+ repainting.
+
+ Shane
+

?? and it does when setting Lines.Text ?? ... OK !

Marc

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

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

Reply by email

Shane Miller

OK. My toolbar code has been committed. It currently doesn't do anything yet. I have to create the gtkwidget's for the toolbar and toolbutton's yet, bt the object's get created correctly.

This is an early implementation and I figure I can get it to display a real toolbar in the next few days.

Marc, nice work on the MWEDIT component. I commented out my toolbar stuff and ran lazarus. I see it's colorizing the code now, at least the portion that's visible. How are you going to approach the problem that the mwedit component isn't receiving any key events? Plan on adding an eventbox to the canvas or bitmap control in gtkobject?

Shane

>> 12/07/99 02:05PM >>>
you wrote 13 lines
Got further!!!. I added the mwPasSyn1 back into mwEdit. For those unaware, mwPasSyn1 is the syntax highlighter for mwedit. Without it, the text is just plain old text. I added it back and found it crashed again in NULLPROC. When I went into debug (DDD) I found that I got into the procedure but THIS = 0x0. Odd......then I noticed that when FProcTable was assigned to NullProc it was assigned by doing this: FProcTable[I] := NullProc; This is the correct way of doing it, but it doesn't work for FPC. I was surprised it compiled!!!!

Hmm.. I cant see why. But isn't this introduced by the fact that we are compileing in {$mode objfpc}.
I probably missed it, but why aren't we using {$mode delphi} ??

Marc

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

Reply by email

Stefan Hille

Hi!

- Made TGroupBox working again
- Provided sample for TGroupbox

as mentioned earlier:

- TProgressBar / TTrackbar working again

good night,

Stefan

--------------------------------------------------------- Stefan Hille email: 48155 Muenster voice: 0251/664695

Reply by email

Marc Weustink

Fixed triple chars in editor. Events where fired more than once. Now it is checked if there already exists a callback.

Marc

Reply by email

Peter Vreman
to Shane Miller: OK. My toolbar code has been committed. It currently doesn't do anything yet. I have…
you wrote 13 lines
OK. My toolbar code has been committed. It currently doesn't do anything yet. I have to create the gtkwidget's for the toolbar and toolbutton's yet, bt the object's get created correctly. This is an early implementation and I figure I can get it to display a real toolbar in the next few days. Marc, nice work on the MWEDIT component. I commented out my toolbar stuff and ran lazarus. I see it's colorizing the code now, at least the portion that's visible. How are you going to approach the problem that the mwedit component isn't receiving any key events? Plan on adding an eventbox to the canvas or bitmap control in gtkobject?

You can also try to get shedit working for the LCL. You can take a look at the gtkdemo which already colors everything and you can edit/scroll/select already. Only mouse events don't work yet.

Peter

Reply by email

Marc Weustink
to Shane Miller: OK. My toolbar code has been committed. It currently doesn't do anything yet. I have…
Shane wrote 7 lines
OH-OH. I forgot to "add" ome files when I did my commit so my comctrls.pp file won't compile. I'll add them tomorrow. For now, comment out the toolwin in the uses clause, the TToolButtton and TToolbar classes along with the {$I Toolwin.inc} and {$I Toolbar.inc} statements near the end of the file. Sorry about that...

No worries, I commented it out with my last changes. You forgot to mention a piece of code in gtkobject.inc(creation of control) and main.pp(decl of var)

Changes to CVS:
I added/recoded the key event callbacks, so now we get Delphi compatible messages. The LCL message handlers are filled in ....

... and the editor edits !!!

(if you don't count triple uppercase chars without cursor movement ;-)

the trick: from the testform click the second button and TAB into the editor. Now it has focus and you can type what you want.

Marc

Reply by email

Marc Weustink
to Shane Miller: OK. My toolbar code has been committed. It currently doesn't do anything yet. I have…
Shane wrote 6 lines
Marc, nice work on the MWEDIT component. I commented out my toolbar stuff and ran lazarus. I see it's colorizing the code now, at least the portion that's visible. How are you going to approach the problem that the mwedit component isn't receiving any key events? Plan on adding an eventbox to the canvas or bitmap control in gtkobject?

Im working on that. The problem is that it receives key events, but they are mapped to the wrong messages. I'm rewriteing the callbacks for that. I'm only now desperate looking for some good documentation on what the gtk parameters mean in the callbacks. It's nice to know thay you have a 'key-press-event', but ist's even better if you know what the callback is trying to tell you.
I didn't like filling up a TWMKeyDown struct in the past, now it's even worse without proper docs.

Marc

Reply by email

Shane Miller
to Shane Miller: OK. My toolbar code has been committed. It currently doesn't do anything yet. I have…

OH-OH. I forgot to "add" ome files when I did my commit so my comctrls.pp file won't compile. I'll add them tomorrow. For now, comment out the toolwin in the uses clause, the TToolButtton and TToolbar classes along with the {$I Toolwin.inc} and {$I Toolbar.inc} statements near the end of the file.

Sorry about that...
---------------------------------------
Shane Miller
Get paid to surf the net!
http://alladvantage.com/go.asp?refid=DEX-870

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.miraclec.com/lazarus

Earlier message 58 lines
----- Original Message ----- From: "Shane Miller" To: Sent: Tuesday, December 21, 1999 3:32 PM Subject: RE: [lazarus] CVS Update > OK. My toolbar code has been committed. It currently doesn't do anything yet. I have to create the gtkwidget's for the toolbar and toolbutton's yet, bt the object's get created correctly. > > This is an early implementation and I figure I can get it to display a real toolbar in the next few days. > > Marc, nice work on the MWEDIT component. I commented out my toolbar stuff and ran lazarus. I see it's colorizing the code now, at least the portion that's visible. > How are you going to approach the problem that the mwedit component isn't receiving any key events? Plan on adding an eventbox to the canvas or bitmap control in gtkobject? > > Shane > > > >>> 12/07/99 02:05PM >>> > At 12:33 07-12-99 -0600, you wrote: > >Got further!!!. I added the mwPasSyn1 back into mwEdit. For those unaware, > >mwPasSyn1 is the syntax highlighter for mwedit. Without it, the text is > >just plain old text. > > > >I added it back and found it crashed again in NULLPROC. When I went into > >debug (DDD) I found that I got into the procedure but THIS = 0x0. > >Odd......then I noticed that when FProcTable was assigned to NullProc > >it was assigned by doing this: > > > >FProcTable[I] := NullProc; > > > >This is the correct way of doing it, but it doesn't work for FPC. > >I was surprised it compiled!!!! > > Hmm.. I cant see why. But isn't this introduced by the fact that we are > compileing in {$mode objfpc}. > I probably missed it, but why aren't we using {$mode delphi} ?? > > Marc > > > _________________________________________________________________ > To unsubscribe: mail with > "unsubscribe" as the Subject > archives at http://www.miraclec.com/list_archives/lazarus > > _________________________________________________________________ > To unsubscribe: mail with > "unsubscribe" as the Subject > archives at http://www.miraclec.com/list_archives/lazarus >

Reply by email

Marc Weustink

Hi,
Some changes:
+ removed the color depth dependency. pfDevice is now supporrted and bitmaps are default created with the depth of your system.
+ cleaned up key events a bit.
+ started to add scrollbar support (just as a test)

Im still searching why on a fixed widget I get a mouse/key down event, but no up event.

Marc

Reply by email

Michael A. Hess
to Curtis White: I haven't received any email from the list for quite a while now, so I was just wondering…
Curtis White wrote
I haven't received any email from the list for quite a while now, so I was just wondering if it was still alive. Is anyone still working on Lazarus?

You haven't been receiving any emails from the list due to the fact that you are no longer subscribed to the list. I checked the logs and the list received an unsubscribe request for you address on Jan.9th

-----------------------
unsubscribe: 35 32734
by: Sun Jan 9 15:52:25 EST
2000
-----------------------

That was the unsubscribe request if you want to check on why it occured. Since that time there have been over 125 emails to the list. You might want to check the archives to see what you have missed. Be sure to subscribe to the list again.

Please note that if anyone wants I can add them to the list as a permanent member. They or no one else can remove them from the list. Only I can remove them. If you would like this feature just let me know and I will set your address up that
way.

==== Programming my first best destiny! ==== Michael A. Hess Miracle Concepts, Inc. http://www.miraclec.com

Reply by email

Shane Miller

We are still working on the project. You should have been receiving mail from the list. It has been somewhat active.

Shane

>> 01/31/00 11:04AM >>>

I haven't received any email from the list for quite a while now, so I was just wondering if it was still alive. Is anyone still working on Lazarus?

Curtis

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

Reply by email