The display bit did the trick and with all the computing going on, the
updating is still responsive. Thanks to Randall for the tips.
Martin Stoufer wrote:
I totally forgot about the 'display' call. I will try that as a first
pass. As for refactoring, that IS the long term solution to the
probl
I totally forgot about the 'display' call. I will try that as a first
pass. As for refactoring, that IS the long term solution to the problem,
but the legacy code is like a pool of mud when it comes to moving it
around. I will need a shot of courage before I dive into that.
Randall Meadows wro
On Aug 28, 2008, at 10:37 AM, Martin Stoufer wrote:
I am developing an app that is utilizing some legacy C code that I
have massaged into Objective-C classes. In one of them, I am trying
to drive an NSProgressIndicator view as defined by the NIB for the
project. There is a core processing l
I am developing an app that is utilizing some legacy C code that I have
massaged into Objective-C classes. In one of them, I am trying to drive
an NSProgressIndicator view as defined by the NIB for the project. There
is a core processing loop that originally spit out multiple '.' to
stdout as i