Issue of lots of unused variables in Forms type declaration

[vfclists]

Whenever controls are added to a form, variables are created for them, although they may never be used.

Labels are a good example of this.

What is the general approach for dealing with this issue, besides eliminating unused variables from the source?

What are the unwanted side effects of removing them.

What effects does that normally have on the .lfm files etc?

[marcov]

This is normal. Don't edit, it will break.

The LFM declares nothing on pascal level, that's what those fields are. Those fields _are_ the control instance, not an additional variable.

[vfclists]

This is normal. Don't edit, it will break.

The LFM declares nothing on pascal level, that's what those fields are. Those fields _are_ the control instance, not an additional variable.

If you don't ever expect to use the variable referring to a control, or its subcomponents anywhere in the code, isn't it safe to delete it?

Does the form streaming/loading system need the variables to be there even if they are never used?

[taazz]

This is normal. Don't edit, it will break.

The LFM declares nothing on pascal level, that's what those fields are. Those fields _are_ the control instance, not an additional variable.

If you don't ever expect to use the variable referring to a control, or its subcomponents anywhere in the code, isn't it safe to delete it?

  no if you want to make it safe to delete convert to dynamically created one.

Does the form streaming/loading system need the variables to be there even if they are never used?

Those variables are in the published section of the form for a reason, it is the only access point for the streaming mechanism if you move the definitions to a protected section then you will get exceptions.