XCode: error from debugger: the program being debugged is not being run.
If you are getting this in your XCode run log:
No executable file specified.
Use the "file" or "exec-file" command.
No executable file specified.
Use the "file" or "exec-file" command.
The program being debugged is not being run.
The program being debugged is not being run.
After copying a project and renaming everything... then you missed the "executable name" on the target. Click your Target, and "Get Info", then click the Properties tab, and rename the Executable to the same name as the Product Name in the Build settings.

Tags: mac xcode | (0) Comments | Add Comment

Const Armageddon
So after getting about 9000 warnings building Lgi with the latest XCode 3.x I decided that I would do something about it. A lot of the warnings consisted of "casting from const char* to char* is deprecated" because I was passing a string constant into a char* arg. So I fix one of those. Which causes 4 more. And so I fix some more of those, and it snowballs... and snowballs... and then there is an avalanche of API's getting 'const' all through them. Many days latter I'm now back on top of the warnings. However now I've modified a number of base classes with virtual functions that had char* arguments. Of course the compiler doesn't warn you when your child class stops overriding the parent function does it! So the big hunt for mis-matched function definitions begins. No doubt I'll miss some and random stuff will just stop working, because the base class got the call, not the child class. *sigh*

Update: So after finding most of the problems by bumping into them accidentally I realized that I was going to missing something important anyway. So I wrote a python script that calls ctags to extract a bunch of symbol definitions, then it parses through all those and finds all the class methods, and compares their arguments and return type with the parent classes virtual function, and spits out an error if they differ. This was great, it picked up a few methods I'd missed, and gave me confidence that I could release the next build of Scribe without having broken functionality.

Tags: code | (0) Comments | Add Comment

Python Is Awesome
That is all.

Tags: code python | (0) Comments | Add Comment

Scribe/Mac unified toolbar
I got this working today:
Looks a little more native eh? I think the icons are still a little blurry, but to fix that I'll have to create full resolution source icons, which are 128x128. Currently they are 24x24, and they are getting scaled somewhat for display on the toolbar. First x4 to fill the 128x128 source image and then down to whatever size the HIToolbar wants to display them as.

I've been playing for years now with getting native scrollbars working. But thats proven too difficult so far for this little black duck.

Tags: mac code | (0) Comments | Add Comment