Hi Cesar

>I agree.
>But to fix the "modal" problems we need to use the scrollable container. Of course, I could transport all codes to a Container and make it scrollable, but IMO this would be an insult to Carlos Aloatti for the great job he did providing some really excellent tools and controls.
>For the scrollable container, it will need 7 files to be added. (1 header .H, 3 .vcx and 3 .vct)

No, no, I wouldn't want you to bring in all of his code into VFPPaint. Just an idea is to package it as an .app, will the user loose any functionality and integration?


>I'd like to have your opinion on this.

Thanks I am honored.


>1 - Add all controls in the form
> The final result may be a crowded form, but this can bring some facilities for users to customize it.
> This way, users can do whatever they want with them, and move these controls wherever they want.
>
>2 - Create a formset or some extra forms that would contain the required controls

These two I am a bit reluctant about, esp. #2.


>3 - Create separate toolbars for each controls category

Nice if we can have floating toolbars that are activated when a representative button is clicked (as in VFP and office applications)


>4 - Add a menu to the form containing the commands

For keyboard freaks like me I would appreciate it. Yes, in combination with the toolbars as mentioned in point #3, that is, if it is not too much work


>5 - add an OutlookBar2003, VFPX project from Emerson Reed, and on each frame put the required controls / slidebars.
>IMO, this will bring the best visual and practical result, but will require to add some other classes to VFPPaint.
>
>
>This last possibility is the one I like most, and is the way I will work here in production. Do you think it will bring some problems ?

Good idea, but will it not take up a lot of (esp.) width as well as height? If the Outlookbar is there and the buttons are also there then that will be a lot of clutter, but if the buttons can be avoided almost if not completely then that is a good idea. Just from the top of my head, just like the optType buttons, the outlookbar can replace them, for eg the Text section of Outlookbar is selected then the text and font properties can be set in that outlookbar section and it will collapse when another section is selected thus hiding the text related fields/buttons completely.


>Thanks for the suggestions !

Welcome, it was a learning experience for me too.

Thanks.