You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2017. It is now read-only.
Hope this not a waste a time, but I think I might have found a problem with core-list. I have been about to reproduce it using the Core and PaperExamples.
Using 'polymer-core-and-paper-examples/web/core_list_dart/basic.dart' I lowered the number of TestItem it would initially produce. I did this by reducing count from 50000 to 5. So Now when I compile and run the example I just have five items on the screen.
Then I click the 'Add Row at Index' button, this just adds a TestItem to the top of the list. I continue to until to add the first generated TestItem moves off the screen. I then scroll up to bring that item back into view and then add another item. This is when I get:
Exception: The null object does not have a method '_addFromInteger'.
NoSuchMethodError: method not found: '_addFromInteger'
Receiver: null
Arguments: [1520]package:core_elements/core_list_dart.dart:1040 CoreList._positionItems@407177370package:core_elements/core_list_dart.dart:934 CoreList.<anonymous closure>
in the web console. If I continue with this behaviour, very quickly lose all the items in the list they disappear. I continue to receive the above message in the console
Repeating this various combination yields the same result. The only variation I have been able to notice is that if a allow all the TestItems which were initially generated to disappear off the screen before I scroll to bring the first one back into view. I get a range error.
Again will the above all the TestItem quickly disappear out of view. I hope you can confirm this.....
Normally I just use core-list to present the user with a list of items and ask them select one. That works wells, because the list I pass in does not change. The use case that lead me to that above problem was a attaching the core-list model to a stream which was stream which was send events in burst, very quickly I was missing messages and needing to scroll back up to see the lastest one's and this is when this problem arose.
Any insights would be appreciated.
Ray.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi Guys
Hope this not a waste a time, but I think I might have found a problem with core-list. I have been about to reproduce it using the Core and PaperExamples.
Using 'polymer-core-and-paper-examples/web/core_list_dart/basic.dart' I lowered the number of
TestItem
it would initially produce. I did this by reducingcount
from 50000 to 5. So Now when I compile and run the example I just have five items on the screen.Then I click the 'Add Row at Index' button, this just adds a
TestItem
to the top of the list. I continue to until to add the first generatedTestItem
moves off the screen. I then scroll up to bring that item back into view and then add another item. This is when I get:in the web console. If I continue with this behaviour, very quickly lose all the items in the list they disappear. I continue to receive the above message in the console
Repeating this various combination yields the same result. The only variation I have been able to notice is that if a allow all the
TestItems
which were initially generated to disappear off the screen before I scroll to bring the first one back into view. I get a range error.Again will the above all the
TestItem
quickly disappear out of view. I hope you can confirm this.....Normally I just use core-list to present the user with a list of items and ask them select one. That works wells, because the list I pass in does not change. The use case that lead me to that above problem was a attaching the core-list model to a stream which was stream which was send events in burst, very quickly I was missing messages and needing to scroll back up to see the lastest one's and this is when this problem arose.
Any insights would be appreciated.
Ray.
The text was updated successfully, but these errors were encountered: