How about things that might trigger cascades of component resizing?
automatic sizes?
image components switching pictures inside arrangements?
For propagated effects, do you have pre-calculated lists of vertical and horizontal neighbors, or do you have to recalculate neighbors off the original matrix of components?
I use a subroutine to check and see if it is a string of three or more blocks vertically. If so when you press the top block or any block with three below the same color, I do a sound and change the blocks to a elimination color. Then when the sound ends I check the list for that elimination color and move the blocks from above down.. for specials I have a special checker, which calculates which blocks adjacent to the special block need to be eliminated. Like for the horizontal ray gun I calculate which blocks are to the left and right of the special and mark them for elimination. Then I do the sound, change those blocks images to a horizontal Ray effect. When the sound finishes I then eliminate those blocks. I use elimination subroutine that will drop the blocks. I use lots of lists for effects like the horizontal gradient.
How many sound components do you have?
(Trick question - the Sound component blocks execution)
Only 22 players, but no sound blocks. I use the players as timers also. Like change blocks to an explosion image, play explosion sound, when player finished change blocks to holes, drop the blocks into holes. Works. Got rid of a timer, the flashing bomb, and that removed some slow down. I suspect too many timers enabled at the same time is a bad thing
1 Like
Some articles on waiting and timing here
Alternatively use only 1 player and set the sound to play before playing
Reuse your components...
Taifun
But you can have only one 'when player finished' block per player. That's why I use multiple players, when they finish they can do unique things, after a time delay, the length of the sound mp3. Does it hurt to have many players as long as they aren't playing at the same time?
Are you planning on updating your extension with this? Sure a lot of people including me would be interested and thankful
Still working on it. Some parts work OK, others not quite as I would like. Android Developers documentation is generally terse, and without examples (especially for us), it therefore is a bit hit and miss for the uneducated (like me). Watch this space.
I certainly will be checking in, thank you very much. I'd like to just minimize the navigation bar and keep the status bar. For now I made a fake status bar
Unfortunately, the thing I have the biggest problem with is the Nav bar. I can hide it, but would have to remove the colour from the status bar.
You might have more success with adjusting the margins of your arrangements ( I have included a method for this)
I tried your hidebar extension and it worked, I used taifun tools hide SUI block since it was already added to the project and it worked also. I prefer a black status and navigation bar so I'm not concerned with setting their coloring, more concerned with being forced to have them colored
I can do both black (with white icons and text) 
More info here:
Hey,
I was reading all the post carefully but what I still don't understand:
When I have for exampel 3 arrangements below each other on my screen and I set all arrangement heights to "fill parent" or "automatic" there is no issue with the navigation bar.
But as soon I size one of these arrangement heights via a percentage the navigation bar overlapps the arrangment. (please see pictures on my first post)
It happens consitently also on other projects and just appeared after the update to 2.76
I saw in several post and articles this topic with the latest google change (API35) which is made responsible for that. But somehow this doesnt make sense to me since when all arrangements are set to automatic/fill parent everything is properly shown. (so the companion app does the right thing with the nav bar and screen height)
So, is there may be a small bug in the latest update? Or if not what is the explanation for this behavior?
Best regards
I had to use percentages with my arrangements, every row of buttons is an arrangement, 15 of them. Them. I needed them all the same size and yet needed the title buttons bigger. I don't think automatic would work for me. That's interesting that it works fine if you used all automatic arrangements.
I'm still trying to reproduce this problem. Would you be willing to send me an aia file of an app where the bottom us under the navbar?
It should put some of arrangement c behind the nav bar. (In my case it completely covers arrangement c)
If you change arrangement b to fill parent, then everything fits.
If we have a method to find the heights of the status, navigation and title bars, then we can calculate the available screen height. Or if screen height is automatically calculated depending on which bars are visible/invisible.
1 Like
