Why disable scrolling on a disabled form

Classic Servoy
1

When setting a form disabled, the scroll bar becomes inactive. Anyway to disable a form but keep scrolling alive?

2

We could change the disabled forms to have enabled scrollbars (if they are needed).
For now you can use something like

for (i = 0; i < elements.length; i++)
{
	elements[i].enabled = false;
}

to reach this purpose instead of setting the form’s enabled state. All the elements in the form must have a name in order for this to work.

3

We could change the disabled forms to have enabled scrollbars (if they are needed).

I think that would be reasonable. Disabled means for me: I can’t change or do anything. But I can see things. If I don’t want that, I hide the whole form.

4

To be honest I never disable a form, only elements. Gives me (but who am I :) ) the feeling of complete control and much more flexibility…

5

I don’t do that either ;-). Buttons usually look very ugly, too…

6

Since we already have more votes for enabled scrollbars and none against :D, this will be changed in Servoy 3.5.1.

7

Enabled scrollbars sounds great…seems to be a reasonable idea as a “disabled” form is probably meant to be looked at, at some point, by someone.

While we are on this topic, should the tabs and scrollbars of tabpanels and portals also be enabled by default on a disabled form?

Thoughts?

8

If the form that contains the tabpanel/portal is disabled, I think the tabpanel/portal should be disabled too. Changing the tab in a tabpanel or scrolling inside some components of the form is, I think, enabled-form behavior.

The idea is to not be able to interact with the form, but be able to see the current visual state of the form when the form is disabled.