Bug 11215 - Bug in properties list editor
Summary: Bug in properties list editor
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 4.0.1
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2013-03-17 16:45 UTC by Joseph Remes
Modified: 2013-03-18 17:52 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Joseph Remes 2013-03-17 16:45:31 UTC
Just found what looks like a bug in the Property List Editor.
I decided to foray into using child panes in Settings. So I created a new plist called 'Advanced' and linked to it from Root.plist.
So far so good. But when I create a PSTextFieldSpecifier entry, it refuses to allow me to add a DefaultValue key to the dictionary. It *will* allow this when I am editing Root.plist, but not in Advanced.plist.
I was able to add this XML Element using TextEdit and it sure seems to be working, although I have not tested this exhaustively yet. But what the heck is the problem with the Xamarin.Studio plist editor? Or am I missing something?
Comment 1 Jeffrey Stedfast 2013-03-18 14:51:31 UTC
Xamarin Studio 4.0.2 should be hitting stable today or tomorrow, I think. When it goes live (or you can install it from the Beta channel if you are up for it), can you check this again?

It appears to work for me and I *do* recall fixing a DefaultValue bug after 4.0 was released.

Thanks!
Comment 2 Joseph Remes 2013-03-18 17:33:18 UTC
Just got Studio 4.0.2.
The 'Default Value' problem appears to be fixed. Cool!
Comment 3 Jeffrey Stedfast 2013-03-18 17:52:24 UTC
Awesome!