“translate scheme”

I managed to handle this in Objective-C. I've made an actual implementation here, but here's a sample of what it might look like:First let's take a look at the header file:// MyClass.h #import <JavaScriptCore/JavaScriptCore.h> // This is where JSExport lies /* * This is where the magic happens. Any method declared inside a JSExport protocol * will be translated into JavaScript. Quite useful. */ @protocol MyClassJavascriptMethods <JSExport> - (BOOL) method; - (NSString*) methodWithAnArgument:(NSDictionary*)argument; @end /* * This class must implement the above protocol */ @interface MyClass : NSObject <..., MyClassJavaScriptMethods> @endNotice the protocol, it's where the Obj-C - JS binding actually happens. Now let's move over to the implementation file:// MyClass.m #import MyClass.h @implementation MyClass // implement the MyClassJavascriptMethods protocol: - (BOOL) method { // do stuff } - (NSString*) methodWithAnArgument:(NSDictionary*)argument { // do some other stuff } @endNow

Our data was in a C++ class variable that was a struct which had .x, .y, .z ...we were not init'ing the .z of the struct butthen passing the .x .y .z values to glTranslate. So it would translate to outer space and get Z-clipped (my guess).The uninit'd variable checker in the compiler may not be catching this case.Once I fixed it, I didnt have much time to trace the why, etc... but I suspect the root cause is that class variables are notguaranteed to be zeroed in C++. I think this is Not like ObjC/NS, where the default init] method does set class variables to zero (by default) in an NSObject.

I actually solved my issue. Turns out in my scheme I had environment variables checked for run time arguments but no variables being passed in. By unchecking this my app is now running on the simulator again.

as I said in my other reply, the names cannot be the same and in factthey aren't in this case. Yours is DJ2 theirs though it translates to DJ2is in Korean and has a completely different meaning. You might complainabout the branding but unless you own a trademark or patent on it you'retilting at windmills.

I was able to make a brand new OSX project in Xcode 7.1 and build it as 32-bit by changing only two build settings. Specifically Architectures (32-bit Intel) and Automatic Reference Counting (No). So it is still possible to do this. Getting your legacy project to build probably involves some build settings and scheme changes.

Probably you are not going to find any problem to use this tutorial in Objective-C to apply to Swift because this guide is conceptual and about the SDK not specific for the language, also it's not that hard to translate from Objective-C to Swift.I started to develop in Swift following the Apple Introduction during the beta of iOS 7 and it was complete.I trully recommend tutorials from http://www.raywenderlich.com/, they are straight forward and very good for beginners.If you have any problem post your questions in the Apple Forum and people could help you.

Sounds like something that should be in the WatchOS framework 😉I guess I don't understand calendars and locale well enough to comprehend your hints/suggestions. When I created/forced a custom locale for gregorian calendars, the order of the Month/Day (I'm going to leave the year last always) never changes when I go from US to Germany region in the Run scheme. I did come up with *something* that seems to work (for US, Germany, France, Mexico, and Australia???).NSString *gregorianIdentifier = [NSLocale localeIdentifierFromComponents:@{ NSLocaleCalendar : [NSCalendar calendarWithIdentifier:NSCalendarIdentifierGregorian ] }]; NSLocale *gregorianLocale = [NSLocale localeWithLocaleIdentifier:gregorianIdentifier]; // Don't know why I need this??? // NSDictionary *gregorianComponents = [NSLocale componentsFromLocaleIdentifier:gregorianIdentifier]; NSDateFormatter *dateFormatter = [NSDateFormatter new]; // dateFormatter.dateFormat = [NSDateFormatter dateFormatFromTemplate: @MMM d options:0 locale:gregorianLo

Hmmm. When I change the Application Region in the Scheme (e.g. to France) and place this code in the viewDidLoad of another iOS application, the currentLocale is en_FR and the localizedString is 29 Oct (and this is why I think this code works for my purposes). But, when I place this same code in the WatchKit extension awakeWithContext (and change the Application Region to France again in the Watchkit App Scheme), and Run the watchkit app, the currentLocale is en_US and the result is Oct 29. Not what I expected. Have not tried this on the device though (haven't figured that out yet 😉.