Forum | Appery.io

Duplicate Show Hide Spinner calls.

One thing I have notice in past few weeks is that when I doing any multiple rest service call, busy indicator hide way too early. I dig around js source code which found that inside mobilebase.js, we have subscribed ajax's start and stop event to fire show and hide indicator, but inside tiggzi.js, we still register numbers of those show and hide action in different place. Result early hidespinner call.

Something even worse is that it even doing show and hide on send and complete event while already registered for ajax's start and stop event.

I have comment out send and complete function's show and hide action which still not hide too early, at end I comment out all show and hide method from tiggzi.js and purely rely on ajax's event which end up rather perfect.

I know there are case that not belong to ajax which need busy indicator, but register so many event will cause a lot of issue. It will be good if left show and hide action as optional instead of build in function. Or put it inside one of action inside event list.

When project is simple you won't notice difference, but when project getting larger and complex, it's really not good idea to handle show and hide at tiggzi side.

Thanks for reporting this, we'll test more.

The Ajax loader (for service invocation and page navigation) -- it's something we were planning to turn off by default and let the user decide when to show it.

I'm also having this problem. What's the status of this?

We are working on this issue.

Here is how to hide the status: #ajaxBusy {display: none !important;} until we resolve this issue.

Could you please share your project and tell us how it can be reproduced?

I thought you were already working on this

We were working on this and this is already fixed (will be available after the next release). I need project where it reproducible to test. I know that your project is shared already. Could you tell us where it's reproducible?

Ok sorry I misunderstood.

If you open my project you will be presented with a login screen.

user test
password testpass

Then there are 3 rest services invoked

one to check the login details (this one seems to show a spinner)

then the spinner seems to disappear while the other rest services run. There is one to bring back the initial recipe loaded on the next page and another one to load the menu (accessed by either clicking the menu icon at the top left of the recipe page, or by swiping right.

I hope that helps.

While you're in there, maybe you could check out the current problem I have - If the menu is longer than the recipe, and you scroll down on the recipe, the menu wraps around the recipe. I need to find a way to stop this. The menu is actually stored in a div before the the page element on the recipe page.