In the end, I lost time, money, I’m baffled and still the only solution will be to fix tenth of Xojo projects because Xojo do not want to fix a bug. However the fact remains, despite what it’s written in the manual.Įven if this is written from long time, this doesn’t make it magically correct. The minimum reasonable expected behavior would have been you to change it to a feature request.īut no, you like doing the Feedback cop and close as many cases you can. This is not only disrespectful for the engagement and fondness of (paying) Xojo customers, but it’s counterproductive for Xojo itself.Įven supposing this would be a feature request (which is not IMHO) why did you close my Feedback case? This release expands the availability of Xojo’s new framework, making it easier to share code between the desktop, web, console and iOS. This is how they are used in comparison to JSONItem in the old Classic. The Data namespace includes two methods for dealing with JSON data: GenerateJSON and ParseJSON. It’s utterly unbelievable that a customer spend time in test, check and isolate where Xojo misbehave, discuss in the forum to get help, file Feedback requests, just to see you closing immediately the Feedback case (by Design).Īnd then, everything not working as it should, for you, is a feature request!?! That’s ridiculous. Austin, Texas, USA (April 14, 2015) Xojo, the company that enables 280,000 developers to build native cross-platform applications, today announced the availability of Xojo 2015 Release 2. Much of the new Xojo framework is available for all project types staring with Xojo 2015r2. Norman, the only thing more annoying of Xojo misbehaving, is your behavior in this kind of situations. HA! Norman “Feature Request” strikes again. Well since we have long documented that this IS where copyright info comes from it’d be a change in behavior If you check the pictures I posted, you can see Finder doesn’t ignore the CFBundleGetInfoString if present. I’m not surprised the Finder doesn’t show the older key - its deprecated so it probably ignores it entirely. Once to the plist as this specific key so that if you don’t use a tool like App Wrapper the get info window is correct.Īnd once to some other internal key that a tool like App Wrapper and the Finder would NOT use.Īnd then we read this key back in from the plist (as it can be localized so we HAVE to read it from any localized string sets that might Palardy: The only way we could deal with this would be to write it twice. Now, because we use the correct one, App Wrapper or any other tool changing it makes your long version change as well. The only thing that changed was the PLIST key that this data is being written out under. Its that item in 2012, 2011, 2010, 2009, 2008, and every version I launched as far back as I checked. “Long Version” has been the item that showed in the get info window as what is now known as copyright for a VERY long time. Long Version and CopyrightInfo are two different things and here Xojo is trying to fit one information in these two slots.
0 Comments
Leave a Reply. |