iOS Question Panel enabled/disabled behaviour different to B4A

The behavior of these controls is based on the behavior of the native controls.

Why do you disable the panel in B4A? What does it do?

There is no Enabled property for panels in B4i.

Erel,

Erel said:

Why do you disable the panel in B4A? What does it do?

Click to expand...

It is a container for a host of other views (e.g. radio buttons) - its a long story.

Erel said:

There is no Enabled property for panels in B4i.

Click to expand...

Splitting hairs - I never used the term "Enabled property" wrt B4I panels - I am en/disabling them with
UserInteractionEnabled

Erel said:

The behavior of these controls is based on the behavior of the native controls.

Click to expand...

So I take it the different behaviours I am observing are correct - as this is a fairly fundamental difference it should be prominently documented somewhere - have I missed it?

Don't take my snarly posts too much to heart - I continue to be immensely impressed with what you have done...

JackKirk said:

Erel,



It is a container for a host of other views (e.g. radio buttons) - its a long story.



Splitting hairs - I never used the term "Enabled property" wrt B4I panels - I am en/disabling them with
UserInteractionEnabled



So I take it the different behaviours I am observing are correct - as this is a fairly fundamental difference it should be prominently documented somewhere - have I missed it?

Don't take my snarly posts too much to heart - I continue to be immensely impressed with what you have done...

Click to expand...

Those differences are because of the differences of the platforms. Klaus has a great documentation for both b4i and b4a. You should check it.

Hi,

Could you give me a pointer - I've tried some forum searches without success.

Thanks...

What is the question? How to disable all child views of a panel?

Erel, the question has evolved to "is there any documentation that indicates differences between B4A and B4i wrt effects of panel enabled state on child views"

In my initial post I noted a significant difference that I thought I had found.

Regards...

JackKirk said:

Erel, the question has evolved to "is there any documentation that indicates differences between B4A and B4i wrt effects of panel enabled state on child views"

In my initial post I noted a significant difference that I thought I had found.

Regards...

Click to expand...

link to guide to klaus' documentation about b4i : https://www.b4x.com/b4i/files/guide.zip

tufanv,

Thanks for your interest - I was aware of Klaus' beginners guide and had been thru it thoroughly some time ago.

I just went through it again - its section on B4A vs B4I doesn't cover the issue this thread is about.

If Klaus reads this, could I be so bold as to suggest the following enhancement (in red) to 11.2:

~~~~~~~~~~~~~~~~~~~~~~~~~
11.2 Panel
B4i
Panels don’t have a background bitmap.
But you can draw onto a Panel with a Canvas.

If a Panel, without event routines, covers other views the events are NOT submitted to the underlying views. In B4A they are!
If you want to submit them, you must set the UserInteractionEnabled property to False:

Panel1.UserInteractionEnabled = False

If a panel is disabled (UserInteractionEnabled = False) its child views are also disabled regardless of the UserInteractionEnabled setting you apply to the child view.

Transparent panel: Background: Color.Transparent Alpha = 1

B4A
Panels have a background bitmap.
It is also possible to draw onto a Panel with a Canvas.
If a Panel, without event routines, covers other views the events ARE submitted to the underlying views. In B4i they are NOT!
To avoid this, one solution is to add an empty event routine.

If a panel is disabled (Enabled = False) its child views can be disabled or enabled, depending on the Enabled setting you apply to the child view.

Transparent panel: Background: Color.Transparent Alpha = 0
~~~~~~~~~~~~~~~~~~~~~~~~~

This all assumes my discovery is correct...