Xcode: rb_nibtool no longer picking up actions
I've been following the discussions about getting Xcode 4.3 to find rb_nibtool. The symlink works for me. However it seems to deal OK with outlets but is not working at all for received actions - even in the simplest cases. What may be interesting is that even before I installed 4.3 it stopped recognising actions in 4.2. As far as I'm aware I changed nothing in my setup at this time, so I wonder if it's an Apple Software update that has caused the problem? At present I'm stuck and can't get actions to work in 4.2 or 4.3 even though rb_nibtool is being invoked in both cases. I know because it successfully recognises any change to outlets. I'm using the nightly build from last night (dated 24th Feb). Steve
There is a known problem, (at least It's known to me...) with rb_nibtool and certain forms of ruby block syntax. Specifically, multi-line {} syntax causes it to fail. I've run into this with the dispatch gem doing things like Dispatch::Job.new { #some expensive op } that code, while ruby 1.9.2/3 kosher, causes the nibtool to bomb. However, Dispatch::Job.new do #some expensive op end works just fine. Does your code use {'s or begin/end ? -Pkj On Feb 24, 2012, at 1:36 PM, Steve Clarke wrote:
I've been following the discussions about getting Xcode 4.3 to find rb_nibtool. The symlink works for me. However it seems to deal OK with outlets but is not working at all for received actions - even in the simplest cases.
What may be interesting is that even before I installed 4.3 it stopped recognising actions in 4.2. As far as I'm aware I changed nothing in my setup at this time, so I wonder if it's an Apple Software update that has caused the problem?
At present I'm stuck and can't get actions to work in 4.2 or 4.3 even though rb_nibtool is being invoked in both cases. I know because it successfully recognises any change to outlets.
I'm using the nightly build from last night (dated 24th Feb).
Steve _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
No, I'd already read earlier comments about the block syntax. I can't get actions recognised at all, even in the most trivial cases. If everyone else is OK I might just be doing something stupid. Steve On 24 Feb 2012, at 18:43, Kevin Poorman wrote:
There is a known problem, (at least It's known to me...) with rb_nibtool and certain forms of ruby block syntax.
Specifically, multi-line {} syntax causes it to fail. I've run into this with the dispatch gem doing things like
Dispatch::Job.new { #some expensive op }
that code, while ruby 1.9.2/3 kosher, causes the nibtool to bomb. However,
Dispatch::Job.new do #some expensive op end
works just fine. Does your code use {'s or begin/end ?
-Pkj
On Feb 24, 2012, at 1:36 PM, Steve Clarke wrote:
I've been following the discussions about getting Xcode 4.3 to find rb_nibtool. The symlink works for me. However it seems to deal OK with outlets but is not working at all for received actions - even in the simplest cases.
What may be interesting is that even before I installed 4.3 it stopped recognising actions in 4.2. As far as I'm aware I changed nothing in my setup at this time, so I wonder if it's an Apple Software update that has caused the problem?
At present I'm stuck and can't get actions to work in 4.2 or 4.3 even though rb_nibtool is being invoked in both cases. I know because it successfully recognises any change to outlets.
I'm using the nightly build from last night (dated 24th Feb).
Steve _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Can you show your code, was it working in 4.2? - Matt On Fri, Feb 24, 2012 at 10:57 AM, Steve Clarke <steve@sclarkes.me.uk> wrote:
No, I'd already read earlier comments about the block syntax. I can't get actions recognised at all, even in the most trivial cases. If everyone else is OK I might just be doing something stupid.
Steve
On 24 Feb 2012, at 18:43, Kevin Poorman wrote:
There is a known problem, (at least It's known to me...) with rb_nibtool and certain forms of ruby block syntax.
Specifically, multi-line {} syntax causes it to fail. I've run into this with the dispatch gem doing things like
Dispatch::Job.new { #some expensive op }
that code, while ruby 1.9.2/3 kosher, causes the nibtool to bomb. However,
Dispatch::Job.new do #some expensive op end
works just fine. Does your code use {'s or begin/end ?
-Pkj
On Feb 24, 2012, at 1:36 PM, Steve Clarke wrote:
I've been following the discussions about getting Xcode 4.3 to find rb_nibtool. The symlink works for me. However it seems to deal OK with outlets but is not working at all for received actions - even in the simplest cases.
What may be interesting is that even before I installed 4.3 it stopped recognising actions in 4.2. As far as I'm aware I changed nothing in my setup at this time, so I wonder if it's an Apple Software update that has caused the problem?
At present I'm stuck and can't get actions to work in 4.2 or 4.3 even though rb_nibtool is being invoked in both cases. I know because it successfully recognises any change to outlets.
I'm using the nightly build from last night (dated 24th Feb).
Steve _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Here's the code. It couldn't be any simpler: class AppDelegate attr_accessor :window, :prop1 , :prop3 def close_me(id_sender) puts ("close_me invoked") end def applicationDidFinishLaunching(a_notification) # Insert code here to initialize your application puts ("finished launching") end end This doesn't work in 4.2 either. I can't say for sure it worked earlier in 4.2 becasue I only just created it as a trivial case. What I do know is that a more complex app delegate stopped working in 4.2 for no apparent reason. In relation to the example above, I tried creating an Object-C class that contained only an explicit IBAction for the close_me method. That worked fine and the app ran as expected. When I removed the .h file, IB still showed all was OK. i.e. the close_me action was shown together with the id of the sender. When I deleted the link from the sender the action was no longer shown. Hope this makes some sense. Steve On 24 Feb 2012, at 18:58, Matt Aimonetti wrote:
Can you show your code, was it working in 4.2?
- Matt
On Fri, Feb 24, 2012 at 10:57 AM, Steve Clarke <steve@sclarkes.me.uk> wrote: No, I'd already read earlier comments about the block syntax. I can't get actions recognised at all, even in the most trivial cases. If everyone else is OK I might just be doing something stupid.
Steve
On 24 Feb 2012, at 18:43, Kevin Poorman wrote:
There is a known problem, (at least It's known to me...) with rb_nibtool and certain forms of ruby block syntax.
Specifically, multi-line {} syntax causes it to fail. I've run into this with the dispatch gem doing things like
Dispatch::Job.new { #some expensive op }
that code, while ruby 1.9.2/3 kosher, causes the nibtool to bomb. However,
Dispatch::Job.new do #some expensive op end
works just fine. Does your code use {'s or begin/end ?
-Pkj
On Feb 24, 2012, at 1:36 PM, Steve Clarke wrote:
I've been following the discussions about getting Xcode 4.3 to find rb_nibtool. The symlink works for me. However it seems to deal OK with outlets but is not working at all for received actions - even in the simplest cases.
What may be interesting is that even before I installed 4.3 it stopped recognising actions in 4.2. As far as I'm aware I changed nothing in my setup at this time, so I wonder if it's an Apple Software update that has caused the problem?
At present I'm stuck and can't get actions to work in 4.2 or 4.3 even though rb_nibtool is being invoked in both cases. I know because it successfully recognises any change to outlets.
I'm using the nightly build from last night (dated 24th Feb).
Steve _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Sorry- correction to previous post: When the Obj-C header is deleted IB does still show the action close_me. However it is flagged as an error saying that close_me is not defined on AppDelegate. Steve On 24 Feb 2012, at 19:22, Steve Clarke wrote:
Here's the code. It couldn't be any simpler:
class AppDelegate attr_accessor :window, :prop1 , :prop3
def close_me(id_sender) puts ("close_me invoked") end def applicationDidFinishLaunching(a_notification) # Insert code here to initialize your application puts ("finished launching") end end
This doesn't work in 4.2 either. I can't say for sure it worked earlier in 4.2 becasue I only just created it as a trivial case. What I do know is that a more complex app delegate stopped working in 4.2 for no apparent reason.
In relation to the example above, I tried creating an Object-C class that contained only an explicit IBAction for the close_me method. That worked fine and the app ran as expected. When I removed the .h file, IB still showed all was OK. i.e. the close_me action was shown together with the id of the sender. When I deleted the link from the sender the action was no longer shown.
Hope this makes some sense.
Steve
On 24 Feb 2012, at 18:58, Matt Aimonetti wrote:
Can you show your code, was it working in 4.2?
- Matt
On Fri, Feb 24, 2012 at 10:57 AM, Steve Clarke <steve@sclarkes.me.uk> wrote: No, I'd already read earlier comments about the block syntax. I can't get actions recognised at all, even in the most trivial cases. If everyone else is OK I might just be doing something stupid.
Steve
On 24 Feb 2012, at 18:43, Kevin Poorman wrote:
There is a known problem, (at least It's known to me...) with rb_nibtool and certain forms of ruby block syntax.
Specifically, multi-line {} syntax causes it to fail. I've run into this with the dispatch gem doing things like
Dispatch::Job.new { #some expensive op }
that code, while ruby 1.9.2/3 kosher, causes the nibtool to bomb. However,
Dispatch::Job.new do #some expensive op end
works just fine. Does your code use {'s or begin/end ?
-Pkj
On Feb 24, 2012, at 1:36 PM, Steve Clarke wrote:
I've been following the discussions about getting Xcode 4.3 to find rb_nibtool. The symlink works for me. However it seems to deal OK with outlets but is not working at all for received actions - even in the simplest cases.
What may be interesting is that even before I installed 4.3 it stopped recognising actions in 4.2. As far as I'm aware I changed nothing in my setup at this time, so I wonder if it's an Apple Software update that has caused the problem?
At present I'm stuck and can't get actions to work in 4.2 or 4.3 even though rb_nibtool is being invoked in both cases. I know because it successfully recognises any change to outlets.
I'm using the nightly build from last night (dated 24th Feb).
Steve _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
I believe the parameter for an action method must be named "sender" not id_sender ? -Pkj On Feb 24, 2012, at 2:33 PM, Steve Clarke wrote:
Sorry- correction to previous post: When the Obj-C header is deleted IB does still show the action close_me. However it is flagged as an error saying that close_me is not defined on AppDelegate.
Steve
On 24 Feb 2012, at 19:22, Steve Clarke wrote:
Here's the code. It couldn't be any simpler:
class AppDelegate attr_accessor :window, :prop1 , :prop3
def close_me(id_sender) puts ("close_me invoked") end def applicationDidFinishLaunching(a_notification) # Insert code here to initialize your application puts ("finished launching") end end
This doesn't work in 4.2 either. I can't say for sure it worked earlier in 4.2 becasue I only just created it as a trivial case. What I do know is that a more complex app delegate stopped working in 4.2 for no apparent reason.
In relation to the example above, I tried creating an Object-C class that contained only an explicit IBAction for the close_me method. That worked fine and the app ran as expected. When I removed the .h file, IB still showed all was OK. i.e. the close_me action was shown together with the id of the sender. When I deleted the link from the sender the action was no longer shown.
Hope this makes some sense.
Steve
On 24 Feb 2012, at 18:58, Matt Aimonetti wrote:
Can you show your code, was it working in 4.2?
- Matt
On Fri, Feb 24, 2012 at 10:57 AM, Steve Clarke <steve@sclarkes.me.uk> wrote: No, I'd already read earlier comments about the block syntax. I can't get actions recognised at all, even in the most trivial cases. If everyone else is OK I might just be doing something stupid.
Steve
On 24 Feb 2012, at 18:43, Kevin Poorman wrote:
There is a known problem, (at least It's known to me...) with rb_nibtool and certain forms of ruby block syntax.
Specifically, multi-line {} syntax causes it to fail. I've run into this with the dispatch gem doing things like
Dispatch::Job.new { #some expensive op }
that code, while ruby 1.9.2/3 kosher, causes the nibtool to bomb. However,
Dispatch::Job.new do #some expensive op end
works just fine. Does your code use {'s or begin/end ?
-Pkj
On Feb 24, 2012, at 1:36 PM, Steve Clarke wrote:
I've been following the discussions about getting Xcode 4.3 to find rb_nibtool. The symlink works for me. However it seems to deal OK with outlets but is not working at all for received actions - even in the simplest cases.
What may be interesting is that even before I installed 4.3 it stopped recognising actions in 4.2. As far as I'm aware I changed nothing in my setup at this time, so I wonder if it's an Apple Software update that has caused the problem?
At present I'm stuck and can't get actions to work in 4.2 or 4.3 even though rb_nibtool is being invoked in both cases. I know because it successfully recognises any change to outlets.
I'm using the nightly build from last night (dated 24th Feb).
Steve _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
That does indeed seem to fix it. Thanks. I'm still confused though because I have lots of stuff that used to work and that uses id_sender. Did something change in rb_nibtool? Steve On 24 Feb 2012, at 19:39, Kevin Poorman wrote:
I believe the parameter for an action method must be named "sender" not id_sender ?
-Pkj
On Feb 24, 2012, at 2:33 PM, Steve Clarke wrote:
Sorry- correction to previous post: When the Obj-C header is deleted IB does still show the action close_me. However it is flagged as an error saying that close_me is not defined on AppDelegate.
Steve
On 24 Feb 2012, at 19:22, Steve Clarke wrote:
Here's the code. It couldn't be any simpler:
class AppDelegate attr_accessor :window, :prop1 , :prop3
def close_me(id_sender) puts ("close_me invoked") end def applicationDidFinishLaunching(a_notification) # Insert code here to initialize your application puts ("finished launching") end end
This doesn't work in 4.2 either. I can't say for sure it worked earlier in 4.2 becasue I only just created it as a trivial case. What I do know is that a more complex app delegate stopped working in 4.2 for no apparent reason.
In relation to the example above, I tried creating an Object-C class that contained only an explicit IBAction for the close_me method. That worked fine and the app ran as expected. When I removed the .h file, IB still showed all was OK. i.e. the close_me action was shown together with the id of the sender. When I deleted the link from the sender the action was no longer shown.
Hope this makes some sense.
Steve
On 24 Feb 2012, at 18:58, Matt Aimonetti wrote:
Can you show your code, was it working in 4.2?
- Matt
On Fri, Feb 24, 2012 at 10:57 AM, Steve Clarke <steve@sclarkes.me.uk> wrote: No, I'd already read earlier comments about the block syntax. I can't get actions recognised at all, even in the most trivial cases. If everyone else is OK I might just be doing something stupid.
Steve
On 24 Feb 2012, at 18:43, Kevin Poorman wrote:
There is a known problem, (at least It's known to me...) with rb_nibtool and certain forms of ruby block syntax.
Specifically, multi-line {} syntax causes it to fail. I've run into this with the dispatch gem doing things like
Dispatch::Job.new { #some expensive op }
that code, while ruby 1.9.2/3 kosher, causes the nibtool to bomb. However,
Dispatch::Job.new do #some expensive op end
works just fine. Does your code use {'s or begin/end ?
-Pkj
On Feb 24, 2012, at 1:36 PM, Steve Clarke wrote:
I've been following the discussions about getting Xcode 4.3 to find rb_nibtool. The symlink works for me. However it seems to deal OK with outlets but is not working at all for received actions - even in the simplest cases.
What may be interesting is that even before I installed 4.3 it stopped recognising actions in 4.2. As far as I'm aware I changed nothing in my setup at this time, so I wonder if it's an Apple Software update that has caused the problem?
At present I'm stuck and can't get actions to work in 4.2 or 4.3 even though rb_nibtool is being invoked in both cases. I know because it successfully recognises any change to outlets.
I'm using the nightly build from last night (dated 24th Feb).
Steve _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
participants (3)
-
Kevin Poorman
-
Matt Aimonetti
-
Steve Clarke