Slow swapping from card to card[found reason]
Posted: Wed Aug 19, 2015 12:40 pm
livecode versions: 7.0.5 & 7.0.6
Hi Folks,
I seem to constantly run into speed problems with lc in the windows environment. As my app grows so the speed decreases. I have 15 cards 6 of which are libraries of functions and things like a calendar picker and time picker and behaviours. From a user perspective there are 9 cards to navigate around. During development in the IDE going from card to card takes 7 seconds.
I have timed the change by having 2 global variables, one I put in the "closecard" handler where I record the long time of departure and the other I put at the beginning of the "preopencard" handler and record the long time of arrival. In so doing I hope I have avoided my code which may well be inefficient.
I have created a standalone in windows of the above app. The time taken to move from card to card is 4 seconds. Interestingly, going from card to card on my Android phone is generally less than one second - one second at the outside.
The app has been written with a view to using it in the Windows and Android environments. In this regard the language is very accommodating, however, the speed in Windows means that I cannot use it in that environment and if that were the case it would be somewhat disappointing.
It seems to me that speeding up the time between the closecard and preopencard handler is beyond my control - that may be a bit naive. Can anyone shed some light on how I may reduce this time please.
Thank you,
Hilton.
Hi Folks,
I seem to constantly run into speed problems with lc in the windows environment. As my app grows so the speed decreases. I have 15 cards 6 of which are libraries of functions and things like a calendar picker and time picker and behaviours. From a user perspective there are 9 cards to navigate around. During development in the IDE going from card to card takes 7 seconds.
I have timed the change by having 2 global variables, one I put in the "closecard" handler where I record the long time of departure and the other I put at the beginning of the "preopencard" handler and record the long time of arrival. In so doing I hope I have avoided my code which may well be inefficient.
I have created a standalone in windows of the above app. The time taken to move from card to card is 4 seconds. Interestingly, going from card to card on my Android phone is generally less than one second - one second at the outside.
The app has been written with a view to using it in the Windows and Android environments. In this regard the language is very accommodating, however, the speed in Windows means that I cannot use it in that environment and if that were the case it would be somewhat disappointing.
It seems to me that speeding up the time between the closecard and preopencard handler is beyond my control - that may be a bit naive. Can anyone shed some light on how I may reduce this time please.
Thank you,
Hilton.