 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / Programming / Mac Programming / December 2005plist limitation
I have several problems writing my own little screen saver. I'm going to start with the first one for the moment ;-) It seems to me that plists are very limited in size -- could that be? I've got a plist (happens to be from my screen saver). One of the properties is a string. Everything works when the string is about 60 kB. However, when i manually replace that string by another (valid) one that is about 3 MB, then nothing works any more. Even the Property List Editor gives me an error message, saying that the plist weren't a proper plist. (FYI: I exported the plist from Property List Editor as an xml plist, replaced the string using my favorite ASCII editor, saved it, and tried to open that xml plist with Property List Editor. Of course, i'm making sure that i preserve the original xml format of the plist.) Does anyone have any insights or suggestions? Best regards, Gabriel.  Signature/-----------------------------------------------------------------------\ | Any intelligent fool can make things bigger, more complex, | | or more violent. It takes a touch of genius - and a lot of courage - | | to move in the opposite direction. (Einstein) | \-----------------------------------------------------------------------/ > I have several problems writing my own little screen saver. > [quoted text clipped - 15 lines] > > Does anyone have any insights or suggestions? You almost certainly simply broke the plist by inserting something that doesn't parse. I'd recommend that you just make your changes using Property List Editor, since it will be smart enough not to generate bad syntax. To check your existing plist for syntax errors, you can use the 'plutil -lint' command from Terminal. That said, it's very likely that your error is a basic one. It sounds like you just pasted the string in without doing any preprocessing, which you cannot do in the general case. XML, like HTML, requires that you escape various characters. In this situation, you must escape the & and < characters, which become & and < respectively. You probably also want to escape > as > although as I recall it, this is not strictly required. Also, if you have any non-ASCII characters, make sure that you're editing the file as UTF-8 and not any other encoding. SignatureMichael Ash Rogue Amoeba Software Download XML Nanny (http://xmlnanny.com/) and try running the file through that. This checks for valid XML and will point out any problems like those mentioned in Michael's note. --jim |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.