Why did I not notice it earlier? ...
"Object Inspector: The Boolean property editor now uses a CheckBox by default. A ComboBox with "False", "True" can still be selected in options. The control is now a custom drawn TCheckBoxThemed which is used for both selected and non-selected properties, thus making them visually identical. "It is much better to leave these kind of overengineered features off by default.No need to shove them down our throats.
HiJust done a fresh install of 1.6rc2 on osx 10.6.8.At first it seems ok, so I tried to just rebuild lazarusand get the following error.LAZUTILs error code 256and cant rebuild lazarus.Obviously I have not tried to install any packages as they will fail..Any IdeasJosh
Blaazen, are you reading this? Any idea why TCheckBoxThemed affects the key presses?Anyway I will look at this during the weekend.
Just wondering... Why did all my previous installed component-palletes dissapeare?
Just done a fresh install of 1.6rc2 on osx 10.6.8.At first it seems ok, so I tried to just rebuild lazarusand get the following error.LAZUTILs error code 256and cant rebuild lazarus.
Any steps/tests you want me to do let me know
Why do you feel that a CheckBox for a boolean value is overengineering?
CheckBox is the most natural control for booleans. That is what CheckBox was created for in the first place.
That's why I changed it to a more natural and logical control.
Anyway, I did not quite understand your reasoning but fortunately you can configure the boolean property editor to your liking.
@joshI could create a simple GUI app with a tbutton, and this would compile and run, but I cannot re-build lazarus, or add any components that require a rebuild of lazarus to function.I have tried re-freshing lazarus files from menu, and removing all pp files as a last ditch attempt, but this did not help.It maybe something in my config, but odd as to 1.4.4 running.the main difference is fpc 3.0.0 over 2.6.4..