I don't understand this; I would think in OOP that this problem is solved at the TControl level. Otherwise why would you have OOP ?

Michael.

Mattias,

I just downloaded Windows lazarus_ide_installer.exe, version 0.7. It looks quite impressive!!
Thanks for updating the Lazarus Developer News section too!

How far down on the priority list is:
- dropping components on a form?
- add events mechanism?

How may active developers does this project have? What is being done to attract more?

Kind regards,
Ronan van Riet

Mattias Gaertner wrote

> Thanks for updating the Lazarus Developer News section too! I'm not responsible for the lazarus webpage.

Correct, not the site as a whole. However you can add information to the Developer News sections and I incourage you to do so. You alone know what you are working on and can add information and tidbits about it. For example the updates that are occasionally sent to the mailing list can be added to the Developers News section.

This is what he was commenting on. Shane sent an update within the last several days.

The LCL provides all methods, that the IDE needs at TControl/TWinControl level, in OOP. But it is up to the components to implement the csDesigning state correctly. A combobox should be visible at design time, but should neither grab focus nor open the selection box when clicked. It would help a lot if a designed form captures all mouse and keyboard events. I'm not a gtk expert. Does someone knows a good trick to do this?

Mattias

Created an exception handler to handle all unhandled exceptions.

Application.Messagebox used TMessageBox class for it's dialog now. Added new icons for mtConfirmation so you can use MessageBox's mb_IconQuestion. I added a different icon for mtError and mtWarning

Changed some Messagedlg's over to App.MessageBox's for testing purposes.

Shane

Hi all,

New bugfixes:
- reduced OnResize Events
- fixed: form icon will now be set, even if form is invisible
- memleaks fixed: custommemo font, fhintfont in TScreen, unittree and fileinfo in definetemplates
- fixed hangup on wrong property code (class completion)
- fixed missing classname in new methods (class completion)

Mattias

I'm not responsible for the lazarus webpage.

How far down on the priority list is: - dropping components on a form?

The form editing is not far down the priority list, but it depends on a very stable, consistent and completed base. The boring truth is that the LCL defines about 40 components and although you can already use each of them in your programs, many of them have small workarounds for missing functions. The form editing is a quite complex part of the IDE. All components must be in total harmony/consistency and must give the IDE _all_ events in _exact_ the same manner. This is currently the case for only a few components. Further then all components must be streamable (save and load their properties to a resource). This is 90% completed. The missing 10% is for example all graphic and a few properties that need special ordering. The problem here is that if a component has 100 properties and only one of them fails the whole mechanism fails.

Short: High-Priority, but massive dependencies.
You can help us with that. Pick up one component and try to get it working in design mode. That means, the component must not eat mouse/keyboard events like a black hole and it must allow to draw on it. The main problem is the gtk widget.

- add events mechanism?

The "only" missing part is a good find declaration and compatibility check in the codetools. I will eventually do this, after clipboard, graphics and debugger.

How may active developers does this project have? What is being done to attract more?

Yeah, that's the main problem. Too less.

Marc Weustink is writing the gnu debugger support and is making progress. Shane tries to fix some of the form editing bugs.
I'm writing the clipboard support and then I will have a look on the graphics.

Mattias

Changed CodeTools AddUnitToMainUsesSection to prevent duplicate entries into the uses when dropping ontrols onto a form.

Fixed a bug in MessageBox

Shane

Hi all,

A few bugfixes:

- always build before run
- give a message if compiler path not set before building
- a 'make cleanall' in the lazarus dir should wipe out all ppu and o files
- fixed replacing of resources in source
- fixed reparsing before adding component
- the highlighted error line will now only be hidden if cursor moves
- error files can now be located in test projects

Mattias

I think, events much more urgent than debuggers and so on... With events Lazarus would become usefull IDE. Course, stability is required too.

Toke Herkild:
Hmm... I guess You'd have an eventhandler-handler eg: is_DesignState: Boolean;

Which will be read on the event OnDraw, Onclick, On..... and so forth.... This would mean that actions normaly done by the control will only be done if the control is not in designstate... I'd think that most of the actions of an control is not guided by gtk but by Pascal so if pascal tells the control to bypass the actual handling of the control an Dropdown would not dropdown if you click on it in designstate... eg:

if NOT is_DesignState Do Begin
code which opens Dropdown ...
end
else begin
what to do in designstate...
end;

I know This is only the blueprint but hopefully it'll help.... Regards,
Toke Herkild