Using experimental/monopinvokecallback with unity 2017
Nobody has claimed this yet.
- Dominant language
- Objective-C++
- Stars
- 2.7k
- Forks
- 734
- Avg merge
- 11h 39m
- Merged PRs (30d)
- 1
Description
Is there a way to update this experimental branch with all the changes that would allow it to work with Unity 2017?
Could it be added to the master?
It seems to work great. With it I can have unity call javascript and javascript call unity sequentially so they can stay in sync. Without it communication occurs randomly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the experimental/monopinvokecallback branch and comparing it with master, then check the Unity 2017 integration path. Done means the sequential JavaScript-to-Unity and Unity-to-JavaScript callbacks work under Unity 2017 and the resulting changes are suitable for inclusion in master.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, unity
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100