[lazarus] bugfixes

[Toke Herkild]

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

> Michael Van Canneyt <michael.vancanneyt at wisa.be> wrote:
> 
> > > 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.
> > 
> > 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 ?
> 
Mattias Gaertner wrote:
> 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
> 
> _________________________________________________________________
>      To unsubscribe: mail lazarus-request at miraclec.com with
>                 "unsubscribe" as the Subject
>     archives at http://www.miraclec.com/list_archives/lazarus
>