"One big unit".... Not a good idea ....
Hi, thanks for the answer!
..."virtually" as I wrote. I saw it solution in Lazarus Source
So, it isn't a good idea?
stdctrls.pp:
{$I customgroupbox.inc}
{$I customcombobox.inc}
{$I customlistbox.inc}
{$I custommemo.inc}
{$I customedit.inc}
{$I customlabel.inc}
{$I customcheckbox.inc}
{$I scrollbar.inc}
{$I memoscrollbar.inc}
{$I memostrings.inc}
{$I buttoncontrol.inc}
{$I buttons.inc}
{$I checkbox.inc}
{$I radiobutton.inc}
{$I togglebox.inc}
{$I customstatictext.inc}
This technique help eliminate other problems too.. because in one unit, I have more control for class variables, for example the "private" works differently, for example. private isn't private, I can use it, or I need strict private to real private.
I assume, that the extra units, that are not currently added are only needed for code you will add? E.g, so you can have local variables with types defined in the extra unit?
I definded own important type, for example similar of this:
TSelectMode = (smOne, smTwo);
This is not added automatically, if this isn't defined (or used) in the main (registered) unit.
In that case install the package "cody".
Assign the "Unit/Identifier Dictionary" to a keyboard shortcut.
Now if you start typing the name of a constant or type, you can invoke the dictionary and it will offer you matching types, and if you confirm add the unit that they are declared in.
Thanks for the idea, but as I read is help for me, but I want help for users, who uses my package...