Android Question Transparent panel

[rossati]

Why a transparent panel does not inhibit the view below?

Thannks

John Rossati

 

[klaus]

Because that's how Android works.
Just add an empty Sub MyPanel_Click event routine to consume the event.
Replace MyPanel by the name of your Panel.

 

[rossati]

Thanks Klaus

 

[LucaMs]

Because that's how Android works.
Just add an empty Sub MyPanel_Click event routine to consume the event.
Replace MyPanel by the name of your Panel.

I don't know why but on my phone the click event plays a sound, if you use the Click event, my tablet not; for this reason I prefer to use the Touch event.

 

[sorex]

you can turn off these tick sounds.

 

[LucaMs]

you can turn off these tick sounds.

The specific (of that panel) or should I turn off all of them?

 

[sorex]

it's a general setting on the device.

on my phone it's under settings > sound > touch sounds

 

[rossati]

Thanks Klaus
As you can have guessed I am being to make a modal input, it works with click event;
with the touch event, if I touch, on ending the "modal" the program crash.

John Rossati

 

[rossati]

I apologize: I believe the crash was due to my mistake: the sub who ran the touch event was declared without operands.
John Rossati

 

[klaus]

To be precise, adding a transparent Panel is NOT a modal input!
You need to process the user input yourself after the end of the routine where you call the Panel.
In a real modal input, like the Dialogs library, the process is interupted waiting for the user input in the calling routine.

 

[rossati]

Thanks
I think I did what you suggest; I am attaching the app if you can help someone.
this feature will be added to my form generator, freely downloadable from the website: www.condorinformatique.com.

John Rossati

 

[klaus]

Sorry, but today I have no time to look at your program, I have my grandson at home.
I will look at it tomorrow afternoon.

 

[rossati]

Thanks, I also almost Everyday I have some nephews who kidnap my PC.

John Rossati

 

[klaus]

I had a look at your code, it works, but I have following comments:

- You should not stop the main thread with:
Do While Not(ready)
DoEvents
Loop

- You should not use the same name, InputBox in this case, for a View added in the Designer and another in the code.
You have a warning about this in the Logs Tab. The same with btn.

- I wouldn't create the Dialog in the code each time when the function is called and remove evrything when you leave it.
I would add a layout in the Designer and use the Visible property.

Your code works like a modal dialog but blocks the main thread as long as the dialog is displayed, which is not recomended.

Attached you find a modified version of your code with my vision.
It's not 'modal' and doesn't block the main thread.
And finaly, I would make a CustomView.

 

[rossati]

Thanks
Marco app is only a container for try a Dialog function, I agree that is not the best to stp the main thread but it is the behavior that I wanted, that is a function returning a value.
I added Dialog to my form (de)generator.
A CustomView is a good idea.
Attached Formgen.

Best regards

John Rossati

(Marco1 doesn't works becaus I aheve not yet update B4.)

 

[klaus]

I was not aware that you are using an older version of B4A.
At least you can see in the differences in the code.
The layout file format has changed since B4A V 6.31.

 

[rossati]

Yes I see your suggestions; I have B4A V 6.31, and when I try to open the layout I receive an error unknown: 12.

 

[klaus]

Attached you find a 6.31 version.