Thanks: I filed the request.
Bob Rice
On Oct 11, 2009, at 5:10 PM, Jordan K. Hubbard wrote:
On Oct 11, 2009, at 1:45 PM, Robert Rice wrote:
NSTimer wil work well for my app except I will still need to use a
thread to read data from my GPS receiver unless I can find a non-
blocking serial I
Well in the meantime, doesn't a daemon that issues distributed
notifications accomplish a similar goal?
Hunted and pecked from my iPhone
On Oct 11, 2009, at 2:10 PM, "Jordan K. Hubbard" wrote:
On Oct 11, 2009, at 1:45 PM, Robert Rice wrote:
NSTimer wil work well for my app except I will s
On Oct 11, 2009, at 1:45 PM, Robert Rice wrote:
NSTimer wil work well for my app except I will still need to use a
thread to read data from my GPS receiver unless I can find a non-
blocking serial I/O package.
[ jkh jumps up and down yelling "GCD! GCD!" until he is dragged away]
The Core
Hi Laurent:
NSTimer wil work well for my app except I will still need to use a
thread to read data from my GPS receiver unless I can find a non-
blocking serial I/O package.
I see that Apple has developed a "Core Location Framework" for the
iPhone but I don't see any documentation to indic
In theory any runtime exception should be caught by the runloop and
you should see a line in your Xcode console.
As for your timer question, using NSTimer is definitely good in case
your callback doesn't do too much. Since this will all be run in the
main thread through the run loop, if you
Hi Matt:
I am using the most recent build.
I get a traceback for compile errors but not for execution errors on
the NS run loop.
Bob
On Oct 11, 2009, at 2:49 PM, Matt Aimonetti wrote:
The "NSTimer.
scheduledTimerWithTimeInterval_target_selector_userInfo_repeats
"syntax is the RubyCocoa
The
"NSTimer.scheduledTimerWithTimeInterval_target_selector_userInfo_repeats"syntax
is the RubyCocoa syntax, you need to use the selector approach in MacRuby,
very much like obj-C.
If you are on 0.5 beta or a recent nightly build, you should get a
traceback, otherwise, you can still try to catch
Thanks John::
I wasn't familiar with this new syntax. I was using the old syntax
"NSTimer.scheduledTimerWithTimeInterval_target_selector_userInfo_repeats
" but I see it doesn't work in MacRuby.
MarRuby is giving me error messages without a traceback. Is there a
way to enable tracebacks?
On Oct 11, 2009, at 9:19 AM, Robert Rice wrote:
Do you have a preferred method for doing backgound tasks in MacRuby
- perhaps separate threads?
I would say GCD is probably your best bet for this, since you can
simply arrange to have a ruby block execute when your timer fires.
Of course,
Hi Bob,
(you are going to kick yourself) you have misplaced the colon between
target and self - there is a comma there, and the colon has been
placed in front of "target", so the method is not being recognised.
eg:
@synchro_timer =
NSTimer.scheduledTimerWithTimeInterval(TIME_INTERVAL
Congratulations MacRuby Development Team:
My application almost runs now in MacRuby.
Is NSTimer class supported in MacRuby?
I was doing background processing using NSTimer as follows:
@timer = NSTimer.scheduledTimerWithTimeInterval( 5.0, :target,
self, :selector, :periodicUpdate, :userInfo,
11 matches
Mail list logo
