I've found that it's possible when trying to store arbitrary binary data in strings using some methods of Plist Class to create an "invalid" plist that can't be opened by Apple's Property List Editor. It never happens when storing numbers, ascii strings, or booleans, and you can get binary data (like pictures) to work with some added xml escaping and un-escaping routines.
I'll have a look at CFDictionaryMBS but my experience with any kind of Core Foundation stuff in RS has been really bad - incredibly difficult debugging because I never seem to be able to find human-readable variable values in the debugger. Maybe I'm doing something wrong... julia On 10/11/11 6:00 AM, "[email protected]" <[email protected]> wrote: > >Message: 3 >Date: Mon, 10 Oct 2011 09:15:09 -0700 >From: Dennis Birch <[email protected]> >Subject: Re: [MBS] Creating a plist file with MBS plugins >To: MBS Real Studio Plugin List <[email protected]> >Message-ID: <[email protected]> >Content-Type: text/plain; charset=us-ascii > >Hi Julia, > >On Oct 10, 2011, at 6:51 AM, Julia Truchsess wrote: > >> This doesn't involve MBS but it's very good and very useful: Plist Class >> for Realbasic. I use it all the time. > >Thanks for pointing that out. I actually have been using the PList class, >but was warned on the NUG a while back that it shouldn't be relied upon >for creating "official" plist files (or something like that). I never got >a really satisfactory answer as to why that was. But in hopes of not >needing to worry about it further I decided to use the MBS classes since >I was already incorporating some of the plugin functionality in my >current project. > >-- Dennis _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
