Sign in Join

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

Mailing lists / lazarus / 2000-01

Problems Solved thanks

5 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

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

Peter Dyson

Ok after the three msgs of help I tracked it down
to an old symlink
in /usr/bin (not the /usr/local/bin as normal).
Anyway a few rm's
and a bit of reorg with symlinks all is working
fine now.
�
To Michal, I am using the makefile and have renamed the /etc/ppc386.cfg
so as not to have confilcts.
�
I managed to�put together a gtk demo program
of GtkSpinButton. I have
figured what is happeneing about the signals and
message passing.
�
Though I am not too enamoured with the setting of
all properties in one hit
via the message system. This could cause lots of
flashing as users
sequentially set properties in some of the more
property laden components.
Maybe we need a property in one of the parent
classes to disable the posting
of the messages while programmatic updates to the
controls are being made.
�
Having suffered from controls that auto refresh
after each property change, I
for one cannot live with the flashing this causes. While I see this could cause
problems with Delphi coompatibilty, the flashing
and efficiency savings could
outwiegh this, especially if the property
assignments require the creation and or
destruction of object properties. Just imagine
trying to re-intialise a visible grid
control with the plethora of properties this type
of control has, and it trying to
refresh itself after each property
change.
�
Anyway I will have a go at implementing the
TSpinButton component, and see
how it goes.
�
Peter.

Reply by email

Peter Dyson
Hi, Welcome. One thing, can you turn of HTML/RTF formatting while sending to the

Lazarus

Show quoted text 5 lines
list. Not everybody is capable of reading this. Thanks Marc

Ouch I did not know I was doing that, Dammed MS!
I just had to rebuild NT due a HD dying on me and I did not know I was poting in that infernal format!

Apologies

Peter

Reply by email

Peter Dyson
to Marc Weustink: From: Peter Dyson ?? I cant see which control you are refering to, or what flashing. A…
Most of the time you are updating one or two properties once the control

is

created. If you need to do more you can use the same techniques you use in Delphi.

Thats usually some horrible window msg hook hack, not guranteed to be applicable on all platforms, though I must admit is only other ppls code I have had to implement this type of hack for.

Peter

Reply by email

Marc Weustink
to Marc Weustink: From: Peter Dyson ?? I cant see which control you are refering to, or what flashing. A…
you wrote 9 lines
> Most of the time you are updating one or two properties once the control is > created. If you need to do more you can use the same techniques you use in > Delphi. > Thats usually some horrible window msg hook hack, not guranteed to be applicable on all platforms, though I must admit is only other ppls code I have had to implement this type of hack for.

Naah, not with messagehooks, just something like
LockWindowUpdate, visible false, do updates, visible true, unlock

Marc

Reply by email

Marc Weustink
to Peter Dyson: Ok after the three msgs of help I tracked it down to an old symlink in /usr/bin (not the…

From: Peter Dyson

I managed to put together a gtk demo program of GtkSpinButton. I have figured what is happeneing about the signals and message passing.

?? I cant see which control you are refering to, or what flashing.

Though I am not too enamoured with the setting of all properties in one hit via the message system. This could cause lots of flashing as users sequentially set properties in some of the more property laden components.

A while ago there where lots of changes in the internal behaviour of TControl and TWinControl. Not all derived controls have been updated yet. This may result in some strange behaviour.

Maybe we need a property in one of the parent classes to disable the

posting

of the messages while programmatic updates to the controls are being made.

Most of the time you are updating one or two properties once the control is created. If you need to do more you can use the same techniques you use in Delphi.

Marc

Reply by email