|
View:
New views
17 Messages
—
Rating Filter:
Alert me
|
|
|
crash in the carbon event loopHi
I have a weird crash in the carbon RunApplicationEventLoop() function. According to the backtrace it crash somewhere in this method without touching one of my event handler. To be more precise mouse events work just fine but keyboard events seem to crash the application. Whatever I do with the handlers doesn't seem to change anything...(like disabling keyboard or mouse events handler or whatever..) I don't have a clue of what I am doing wrong so if someone had this kind of problems all advices are welcome.. Emmanuel Quetelard. _______________________________________________ MacOSX-dev mailing list MacOSX-dev@... http://www.omnigroup.com/mailman/listinfo/macosx-dev |
|
|
Getting back into MacOSX development after some time offHello,
I am returning back to Mac OSX development after some time off. I am resurrecting an app I haven't touched since 2007. I was able to get it to build to 10.5 SDK. Any pointers in migrating to 10.6 SDK. I know this is a rather general question. Alse I am using MOKit. Has anybody migrated MOKit to 10.6? Thanks, Jerry Porter _______________________________________________ MacOSX-dev mailing list MacOSX-dev@... http://www.omnigroup.com/mailman/listinfo/macosx-dev |
|
|
Re: Getting back into MacOSX development after some time offOn 11/11/2009, at 2:36 PM, jerry porter wrote: > Any pointers in migrating to 10.6 SDK. Have you installed Mac OS X 10.6 on your development machine and tried changing the Base SDK of the project or the target to Mac OS X 10.6? > > I know this is a rather general question. I also know this is a rather general answer. You'll have to be more specific. The source for MOKit is available at <http://sourceforge.net/projects/mokit/files/>. You can modify that source to compile for 10.6 too. Kiel _______________________________________________ MacOSX-dev mailing list MacOSX-dev@... http://www.omnigroup.com/mailman/listinfo/macosx-dev |
|
|
Re: Getting back into MacOSX development after some time offOn Wed, 11 Nov 2009 14:51:49 +1100, Kiel Gillard wrote:
> > On 11/11/2009, at 2:36 PM, jerry porter wrote: > >> Any pointers in migrating to 10.6 SDK. > > Have you installed Mac OS X 10.6 on your development machine and > tried changing the Base SDK of the project or the target to Mac OS X > 10.6? > >> >> I know this is a rather general question. > > I also know this is a rather general answer. You'll have to be more > specific. > > The source for MOKit is available at > <http://sourceforge.net/projects/mokit/files/>. You can modify that > source to compile for 10.6 too. I took a look at it just now and it is pretty outdated. There might be some things of value, but I would consider just removing it from your project and backfilling. W. _______________________________________________ MacOSX-dev mailing list MacOSX-dev@... http://www.omnigroup.com/mailman/listinfo/macosx-dev |
|
|
Re: Getting back into MacOSX development after some time offThanks,
I think I figured out how to "migrate" to 10.6 SDK in my code. I started by playing with the Active SDK and the architecture settings. I will just work my way through the deprecation warnings. I have the source to MOKit and I will probably toss it once I have gotten up to speed on the new UI enhancements now available in 10.6. I also have to get my head wrapped around the new IB too. Jerry Porter - - - When told the reason for daylight saving time the old Indian said ... "Only a white man would believe that you could cut a foot off the top of a blanket and sew it to the bottom of a blanket and have a longer blanket." - - - - - - Seen on a T-shirt: "Remember you are unique and special... Just like everyone else" - - - ----- Original Message ---- From: Steven Woolgar <Steven_Woolgar@...> To: macosx-dev@... Sent: Tue, November 10, 2009 11:49:25 PM Subject: Re: Getting back into MacOSX development after some time off On Wed, 11 Nov 2009 14:51:49 +1100, Kiel Gillard wrote: > > On 11/11/2009, at 2:36 PM, jerry porter wrote: > >> Any pointers in migrating to 10.6 SDK. > > Have you installed Mac OS X 10.6 on your development machine and > tried changing the Base SDK of the project or the target to Mac OS X > 10.6? > >> >> I know this is a rather general question. > > I also know this is a rather general answer. You'll have to be more > specific. > > The source for MOKit is available at > <http://sourceforge.net/projects/mokit/files/>. You can modify that > source to compile for 10.6 too. I took a look at it just now and it is pretty outdated. There might be some things of value, but I would consider just removing it from your project and backfilling. W. _______________________________________________ MacOSX-dev mailing list MacOSX-dev@... http://www.omnigroup.com/mailman/listinfo/macosx-dev _______________________________________________ MacOSX-dev mailing list MacOSX-dev@... http://www.omnigroup.com/mailman/listinfo/macosx-dev |
|
|
|
|
|
|
|
|
Re: Getting back into MacOSX development after some time offThanks, that is a great help.
Jerry Porter - - - When told the reason for daylight saving time the old Indian said ... "Only a white man would believe that you could cut a foot off the top of a blanket and sew it to the bottom of a blanket and have a longer blanket." - - - - - - Seen on a T-shirt: "Remember you are unique and special... Just like everyone else" - - - ________________________________ From: Mr. George Warner <geowar@...> To: macosx-dev@... Cc: jerry porter <jep9816@...> Sent: Wed, November 11, 2009 3:58:49 PM Subject: Re: Getting back into MacOSX development after some time off On Tue, 10 Nov 2009 21:10:17 -0800 (PST), jerry porter <jep9816@...> wrote: > I think I figured out how to "migrate" to 10.6 SDK in my code. > I started by playing with the Active SDK and the architecture settings. Remember that the SDK should be set to the NEWEST version of Mac OS X that you want to run on and the DEPLOYMENT_TARGET to the oldest. For example, for PowerPC Leopard, Intel Snow Leopard and deploy to Tiger: SDKROOT = macosx10.6 SDKROOT[arch=ppc] = macosx10.5 MACOSX_DEPLOYMENT_TARGET = 10.4 You should probably be at least testing with an x86_64 architecture. I usually use: ARCHS = $(ARCHS_STANDARD_32_BIT) x86_64 Note that this is the same for both debug and release configurations. If you only want to build the native architecture when debugging use this: ONLY_ACTIVE_ARCH = YES Note: the above build setting will cut-n-paste into your project or target build settings (if the appropriate table view has focus). -- Enjoy, George Warner, Schizophrenic Optimization Scientist Apple Developer Technical Support (DTS) _______________________________________________ MacOSX-dev mailing list MacOSX-dev@... http://www.omnigroup.com/mailman/listinfo/macosx-dev |
|
|
|
|
|
Re: crash in the carbon event loopOn Wed, Nov 11, 2009 at 5:57 PM, Emmanuel Quetelard
<Emmanuel.Quetelard@...> wrote: > Actually when I don't release any event, the crash still there, so it can't be that (or there is something I didn't understand) . Can it be a release of something else than an event that could cause this crash? Any time you have a memory management bug, it can manifest itself as something else. And since you didn't post your code or the backtrace, there's really nothing more informative anyone can say. Things to take away: 1) If you crash, it's usually because of an over-release. 2) You should be running the clang static analyzer frequently. Especially after you crash. 3) If fixing the static analyzer's warnings doesn't help, and you decide to post to a mailing list, you need to include the backtrace and any code involved. --Kyle Sluder _______________________________________________ MacOSX-dev mailing list MacOSX-dev@... http://www.omnigroup.com/mailman/listinfo/macosx-dev |
|
|
|
|
|
|
|
|
|
|
|
Re: Getting back into MacOSX development after some time offThank,
However I am not to concerned with being backward compatible. I just want to move my code forward. BTW so far so good, purging out the warnings so far. Jerry Porter - - - When told the reason for daylight saving time the old Indian said ... "Only a white man would believe that you could cut a foot off the top of a blanket and sew it to the bottom of a blanket and have a longer blanket." - - - - - - Seen on a T-shirt: "Remember you are unique and special... Just like everyone else" - - - ----- Original Message ---- From: Matt Neuburg <matt@...> To: macosx-dev@... Sent: Mon, November 16, 2009 1:09:27 PM Subject: Re: Getting back into MacOSX development after some time off On Wed, 11 Nov 2009 12:58:49 -0800, "Mr. George Warner" <geowar@...> said: >On Tue, 10 Nov 2009 21:10:17 -0800 (PST), jerry porter <jep9816@...> wrote: >> I think I figured out how to "migrate" to 10.6 SDK in my code. >> I started by playing with the Active SDK and the architecture settings. > >Remember that the SDK should be set to the NEWEST version of Mac OS X that you want to run on and the DEPLOYMENT_TARGET to the oldest. For example, for PowerPC Leopard, Intel Snow Leopard and deploy to Tiger: > >SDKROOT = macosx10.6 >SDKROOT[arch=ppc] = macosx10.5 >MACOSX_DEPLOYMENT_TARGET = 10.4 I often hear this stated as the "conventional wisdom", but my own experience is that if I do that, I don't get the warnings I need in order to discover that my app is not backwards compatible. m. -- matt neuburg, phd = matt@..., <http://www.tidbits.com/matt/> A fool + a tool + an autorelease pool = cool! AppleScript: the Definitive Guide - Second Edition! http://www.tidbits.com/matt/default.html#applescriptthings _______________________________________________ MacOSX-dev mailing list MacOSX-dev@... http://www.omnigroup.com/mailman/listinfo/macosx-dev _______________________________________________ MacOSX-dev mailing list MacOSX-dev@... http://www.omnigroup.com/mailman/listinfo/macosx-dev |
|
|
Re: Getting back into MacOSX development after some time offOn 16.11.2009, at 19:09, Matt Neuburg wrote: >> SDKROOT = macosx10.6 >> SDKROOT[arch=ppc] = macosx10.5 >> MACOSX_DEPLOYMENT_TARGET = 10.4 > > I often hear this stated as the "conventional wisdom", but my own > experience > is that if I do that, I don't get the warnings I need in order to > discover > that my app is not backwards compatible. m. Interesting. What are those "warnings I need" you don't get? The only problems I had were with new/obsolete delegate methods, because compiler doesn't know which are going to be called and which are not going to be called. And no SDK setting can help you with that. izidor _______________________________________________ MacOSX-dev mailing list MacOSX-dev@... http://www.omnigroup.com/mailman/listinfo/macosx-dev |
|
|
Re: Getting back into MacOSX development after some time offOn 17.11.2009, at 10:00, Izidor Jerebic wrote:
> Interesting. What are those "warnings I need" you don't get? I'm not Matt, but the issue he's probably referring to is calling methods that are only available in the newer OS versions. The compiler/linker will not tell you that you're calling one of those, and that you need to add checks or fallbacks for the older OS versions you support. OTOH, by using the oldest system version you support as the SDK, you *can't* call any newer APIs by accident, as they're simply not defined. If you really want to use newer API, you have to jump through a few hoops, of course (put new-OS-specific code in a loadable bundle, declare the methods yourself and look them up manually, or whatever else is appropriate in your case). The difference is, you're making the compatibility-breaking calls explicit. Cheers, -- Uli Kusterer "The witnesses of TeachText are everywhere..." _______________________________________________ MacOSX-dev mailing list MacOSX-dev@... http://www.omnigroup.com/mailman/listinfo/macosx-dev |
|
|
|
| Free embeddable forum powered by Nabble | Forum Help |