Android Question Small button on a larger one?

[Tjitte Dijkstra]

Is it possible to put a small button on a larger one? In one of my projects, I am creating something like a piano keyboard. The white keys are in line and the black keys are half the width of the white ones and the black keys are in the foreground.
But if I click on a white key, the neighbouring black key is not yet in the foreground.
How to solve this problem?

 

[zed]

It's a bad idea to use buttons.
Look at this code

I deleted the sound files because the zip file is too big

 

[Tjitte Dijkstra]

Zed, thank you so far.
I went on experimenting and tried the following: the keys as panels. That seems to be a better way.

 

[zed]

Yes, the signs seem like a good idea.
How do you plan to manage keys?

My first idea would be to put all the keyboard keys in a panel then use GetAllViewRecursive to find out which key is pressed.
But the problem you will encounter is pressing multiple keys at the same time.
This is the reason why I created objects and linked sounds to these objects.
In this case, you can press several keys at the same time.
I wish you good luck.

 

[aeric]

You don't press the top part of the white keys, right?

 

[Sandman]

Look at this code

That's a very good looking piano, is it a published app?

 

[zed]

That's a very good looking piano, is it a published app?

No not at all.
I did it to pass the time. I don't publish any apps.
The code is free.
Anyone can use it to make a complete app.
I also made 2 drum machines if you're interested, I'll post the code

 

[Sandman]

Well, I didn't try your code but just judging by the looks, the piano could very well be published. I imagine there are crazy amount of piano apps, but perhaps a basic one for $1 with no ads would be interesting for the market. Just saying...

Looking forward to seeing your drum machines.

 

[zed]

VDrum. Uses the same principle as the piano.
Drum and Piano, uses lists

I deleted the sound files. App too big to publish

The apps are not finished

Free Source code and royalty free

 

[zed]

You don't press the top part of the white keys, right?

Do you have another idea for this type of work?

 

[kimstudio]

@zed The UI of drum and piano is very nice and professional! I will make a virtual guitar app..

 

[zed]

@zed The UI of drum and piano is very nice and professional!

Tank you.

I will make a virtual guitar app..

Excellent idea. If I can help.

Personally, I do the code when I don't know how it works.
Once I understood how it worked, it was a lot less fun for me.
This is why my apps are almost never finished.
I code just to pass my time.

 

[aeric]

Do you have another idea for this type of work?

Agree with you. Buttons are not a good idea in this case. Button has no Touch event. Better to use Panels.

My previous idea was to use button at bottom that not overlap with top button.

 

[kimstudio]

I just drew the whole keyboard on a panel and check touch event for x, y to determine which key is pressed via calculation, and the top part of a white key also works. https://www.b4x.com/android/forum/threads/mini-synth.142655/

 

[zed]

Mini synthétiseur​

Excellent work.
In fact, I stopped DrumAndPiano development because I don't know how to generate live sound and if it's only used clips in lists, it's less interesting

 

[zed]

We stole the thread from @Tjitte Dijkstra.
We apologize, but it's for a good cause.

 

[Tjitte Dijkstra]

Zed,
Although the thread went a long way from my first question, I read all the answers with interrest.
In the meantime I discovered a new problem:
If I use the Mediaplayer to give a sound, after touching a key (panel) and that works fine, but after 50 - 70 tones, the mediaplayer stops and no sound is heard anymore. Is it a question of memory? (BTW: anytime the mediaplayer is used, I intialize it.)

 

[zed]

If I use the Mediaplayer to give a sound, after touching a key

It is best to use SoundPool. This allows multiple short sounds to be loaded and then played back those files with low latency.
MediaPlayer would be used to play the final recording. Otherwise, you have to have as many MediaPlayers as sound and the latency will be much higher.
If you have a 38-key keyboard, it's going to be a bit complicated.
On the other hand, you will only have one soundpool.

after 50 - 70 tones, the mediaplayer stops

Can you post a project. Like that, I can't tell you why? I never had this problem