-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only 1/2 of the bubbles are presented #91
Comments
Any progress on this? |
@dvlpd Are you working with the react-native or iOS library? |
I work with iOS library, sir |
any updates? |
Hey @jesster2k10 any updates for the react-native lib? |
are you adding nodes inside viewDidLoad? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is an issue in the current version of the library to which only half of the specified nodes are shown. This issue is related to #89, however, I thought it would be better to open a much more conclusive issue.
New Issue Checklist
Issue Description
The issue stems from the Magnetic view showing only half the number of nodes .i.e. showing 8 opposed to 15 nodes.
The cause of the issue is unknown, however, after some investigation, it seems to be that it has to do with the
node.position
set in theaddChild
function.When I run
print(node.position)
I get the following in the console:and only 8 elements are shown on the screen like so:
however, when using the absolute position on both the x and y axis, so the
node.position = CGPoint(x: abs(x), y: abs(y))
,and extra two elements are shown:
Despite that, when showing the nodes count, 47 nodes are drawn onto the screen, more than are visible:
So, my hypothesis is that the issue with only half of the items being shown stems with the positions they are assigned.
In particular, these lines in
Magnetic.swift
Environment
It's worth nothing that this code is running in a react-native wrapper, from a library that I created around this https://github.com/jesster2k10/react-native-bubble-select
The text was updated successfully, but these errors were encountered: