Closed chrise86 closed 9 years ago
Sorry, I wouldn't know. We don't use RubyMotion ourselves. This is not an issue while compiling natively.
All those _cmd=<unavailable>
messages are a bit scary. I wonder what they are about.
Also this self=<unavailable>
I wonder if it's a RubyMotion incompatibility. Have you found any workarounds?
Haven't found anything :( had to give up given my current timeframe for what I'm doing :-/
I ran into the same issue and found that when using the sugarcube gem in your Rubymotion app there is a problem with [UILable new] pre version 3.3.1 - see also https://github.com/rubymotion/sugarcube/issues/172. Upgrading the sugarcube gem to 3.3.1 fixes this.
Hey @chrise86 could you please share some bits regarding how to start playing with such integration?
I just installed the SlackTextViewController
using motion-cocoapods, but I just can't figure out how to actually go and load the controller.
Thanks!
@dgilperez I pretty much just took the example here and converted to RubyMotion syntax
@chrise86 thanks! I happen to have some problem compiling / linking the library with Xcode 5.1.1, but 6.0 seems to be OK.
I’m trying to use https://github.com/slackhq/SlackTextViewController/ in a RubyMotion app, my controller overrides the init method with the following to use the table version:
But as soon as the controller is pushed, the app crashes with the following, using rake debug=1:
The class SLKTypingIndicatorView at line 88 is:
Do you have any idea what it could be?