Journler Finalizing

May 06, 2005 12:18

Another recording test on this end, want to make sure playback is working...
Excellent.
Sent 0.9 off to Dave and Mike, working on 0.9.1 right now. With 0.9.1 I will release the program to Apple as a near final beta program.
Cleaning up memory all over the place. Have found a dozen or so leaks as well as sloppy memory handling, ie too much reliance on autorelease. New policy: if I need to allocate an object, I allocate and initiate it so I can immediately release it when I am finished. Simply better and supposedly faster than autorelease.
Just cleaned up some memory in search, hope that didn't fuck up the searching.
Improving error checking as well, especially at wake from nib where I require certain objects ( journal, search manager, sound input device ) in order to accomplish later things. I absolutely must check for errors here.
Indeed. It seems I've introduced a bug into the search manager...
Something going wrong with the release vs autrelease in the internalAdd method. Works fine with autrelease but not with an explicit release to two variables I create, one a string and the other a text. Odd.
And will it be alright with a CFRelease call? Yes. Okay. Strange.
IMPORTANT
Woah, just noticed that setup creates an old style entries file which is not saved into the old format till a quit. This works because of a backwards compatibility implementation that I eventually will trash. Setup must write both the entries and topics files in the 0.7.3 format. This may be related to Blog Center crashing on first run.
00.58 The Fixes Continue
Just checking to make sure that save change works.
Found another autorelease problem. Why I would need autorelease rather than alloc/init and release when the variable never leaves its current scope boggles me.
01.47 Record Controller Test
Journler Finalizing 1.mp3
Note that I need to set the display name of the converted file so that it does not show the mp3 extension.
I've received an error trying to add the path to my recordings array. I suspect I'm encountering a similar problem with blog tracking.
Previous post Next post
Up