Re: [Lazarus] 2 small designer improvements ?

[Zaher Dirkey via lazarus]

 first one is good
I don't like second idea it cause a lot of flickers if not implemented well.

On Fri, Dec 14, 2018 at 3:54 PM DougC via lazarus <
lazarus@lists.lazarus-ide.org> wrote:

> I like and support both ideas, allowing drop on component to replace it
> with another and allowing typed text to be entered into a component
> property of the selected widget!
>
> --
> ___
> lazarus mailing list
> lazarus@lists.lazarus-ide.org
> https://lists.lazarus-ide.org/listinfo/lazarus
>


-- 
I am using last revision of Lazarus, FPC 3.0 on Windows8.1

Best Regards
Zaher Dirkey
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus

Re: [Lazarus] 2 small designer improvements ?

[DougC via lazarus]

I like and support both ideas, allowing drop on component to replace it with 
another and allowing typed text to be entered into a component property of the 
selected widget!-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus

[Lazarus] 2 small designer improvements ?

[Michael Van Canneyt via lazarus]

Hi,

Recently, I had the occasion to use the following drawing tool quite a lot:

https://jgraph.github.io/drawio/src/main/webapp/index.html

It has a nifty feature which I think could be implemented in lazarus as
well:

Dropping a widget on another one, replaces the widget with the new one.
It takes over whatever properties can be taken over.

Obviously, you don't want this all the time, more often than not you simply
want to drop a new control on another so in Lazarus this should be done using
some modifier key (ALT ?).

Now, I know there is already the 'change class' functionality, so the request 
is simply to implement that functionality in a more drag & drop friendly way. 
You know the component, you know the replacement component class - and the rest

should already be there.

Secondly,
I think that the name/caption of a component should be changeable in-place 
by simply  starting to type when the component is selected. 
(in the above tool, you set the text property of whatever widget is selected)


This is something Morfik Appsbuilder already had 10 years ago, and which
makes life more easy.
And yes, I am aware of the setting 'ask name on create', but this is not
quite it...

Just 2 ideas.

Michael.
--
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus