Sign in Join

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

Mailing lists / lazarus / 2000-07

Some remarks and CVS Changes

3 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

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

Stefan Hille
to Marc Weustink: First a general note on editing: Please check if your editor saves tabs as spaces or…

Hi

Marc Weustink wrote 6 lines
HI, First a general note on editing: Please check if your editor saves tabs as spaces or *don't* use tabs in your code. Not all editors use the same tabspacing. This can result in very jumpy and unreadable code. Thanks.

I'm not sure if this is my fault. Did you notice this specially after I've committed?

Note on debugging: If you want to add debug code better use make you_name_it OPT=-g instead of export DEBUG=1. The latter enables also some unwanted checks which results into a crashing IDE

Ahhh, maybe that's the reason why I had some problems lately. I've already committed a fix for one file (was it gtkwinapi?) to workaround this.

bye,

Stefan

PS: Marc, glad to see you're still working on lazarus. I was feeling a little bit lonely lately

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

Reply by email

Marc Weustink
to Marc Weustink: First a general note on editing: Please check if your editor saves tabs as spaces or…
Stefan Hille wrote 13 lines
Hi On Mon, Jul 31, 2000 at 01:53:25AM +0200, Marc Weustink wrote: > HI, > > First a general note on editing: > Please check if your editor saves tabs as spaces or *don't* use tabs in > your code. Not all editors use the same tabspacing. This can result in very > jumpy and unreadable code. Thanks. I'm not sure if this is my fault. Did you notice this specially after I've committed?

Partly, it is a general remark, you're not the only one. I saw this earlier.

Show quoted text 8 lines
> Note on debugging: > If you want to add debug code better use make you_name_it OPT=-g instead of > export DEBUG=1. The latter enables also some unwanted checks which results > into a crashing IDE Ahhh, maybe that's the reason why I had some problems lately. I've already committed a fix for one file (was it gtkwinapi?) to workaround this.

Nope it was something in TPixmap.ReadStream.

But I kept getting errors till I compiled without debug info. So I stopped fixing others

PS: Marc, glad to see you're still working on lazarus. I was feeling a little bit lonely lately

Still there all the time.
The project I'm currently working on is under heavy pressure. It's delayed for the 3rd time. So when I was behind my PC in the night, I only managed to handle all email, get the latest sources and compile. Nu structural changes.

Marc

Reply by email

Marc Weustink

HI,

First a general note on editing:
Please check if your editor saves tabs as spaces or *don't* use tabs in your code. Not all editors use the same tabspacing. This can result in very jumpy and unreadable code. Thanks.

Note on debugging:
If you want to add debug code better use make you_name_it OPT=-g instead of export DEBUG=1. The latter enables also some unwanted checks which results into a crashing IDE

Some changes:

= Moved ObjectToGTKObject to GTKProc unit

* Fixed array checking in LoadPixmap
If you use export DEBUG=1 for debugging, rangechecking is also enabled. Declaring a "dynamic" arraypointer as array[0..0] triggers this check for elements > 0 :-)

+ Moved LM_SETENABLED to API func EnableWindow and EnableMenuItem Solved some problems in widows being created to early (and is more generic). The EnableMenuItem needs to be finished

+ Added TWinControl.CMEnabledChanged
Enabled the windw through API if the handle is created

+ Added Default enabled in TControl.Create
Wasn't set so all components got created disabled

- Removed the hwnd/drawable asignment in CreateCompatibleDC After rereading the dox this is more compatible

Marc

Reply by email