sergiomorchon / fitbit-views Goto Github PK

I refactored my app code to use Multi View SDK but the performance is just not good. I wasn't able to identify errors properly as they all pointed to views.js try catch. Now I have to scrap all the work put into the update (´;︵;`)

I wanted to divide my views as index.js and index.gui because they were getting large and hard to manage. But at least the performance was way better. I even faced memory errors while swapping of views and fitbit simulator randomly sometimes randomly crash upon me throwing Internal Error.

Is they any way to make swapping of views asynchronous or anything that improves the performance. Please update it!

Hi Sergio,

I plan to use your project. Please add a license, so I can be confident to use it 😉
Thanks!

Use a setTimeout(, 0) to reset the stacktrace on the device, so on deep call stacks it can save some memory allocations.

Hi @SergioMorchon,

First of all, thank you for implementing fitbit-views. It's makes transitions between different screens in an app very easy!

I am having trouble achieving the functionality in my app that I want due to the current current API implementation. My problem is that I am unable to determine which view brought me to the current view, and I am unable to know exactly what view back() will return me too (if at all!).

For example, if I have 3 views (A, B and C) and both views A&B have ability to call next('C'), I would like understand which view (A or B) caused me to enter view C. This would enable different functionality in view C depending on what the previous view was. But currently, this seems impossible because the the stack is not exported, and there is no way to know what view the back() would take me to.

Could you somehow expose the stack and make a getter function for it that allows people to see the sequence of views which caused the app to arrive at the current view?

Thanks for your help, let me know if I can aid in anyway!

Hi Sergio!

With the SDK 5.0 the document.replaceSync() got deprecated. Would it be possible to use fitbit-views with the new SDK along with the old one?

Hi again,

I am having some trouble with parameter passing using the physical back button. I will first explain the situation:

I have a view B, which I entered using next('views/B', {from: 'A'); from view A. This now means that view B expects the parameter "from" whenever entering that view.

The problem arises when I leave view B for view C, and when in view C the physical back button is pressed. This causes the regular back(), function to be called which means no parameter is passed back to view B, causing view B to produce the error:
App: Unhandled exception: TypeError: wrong type of argument ((null):1,1)
App: Unhandled exception: TypeError: Cannot read property 'from' of undefined
? at app/views/B.js

Is there someway to do either of the following?

1. Disable the physical back button on some views?
2. Pass parameters in the back() function when the physical back button is pressed?

Thanks again for your help!