Bug 28038 - Enum values that combine other values don't use correct names
Summary: Enum values that combine other values don't use correct names
Alias: None
Product: Objective Sharpie
Classification: Desktop
Component: General ()
Version: 2.0.3
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Aaron Bockover [MSFT]
Depends on:
Reported: 2015-03-14 15:40 UTC by Dave Dunkin
Modified: 2015-03-15 12:34 UTC (History)
0 users

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:

Description Dave Dunkin 2015-03-14 15:40:07 UTC
If an enum value is set to a combination of other enum values, the ObjC names are used, not the C# names.

Example from Pop:
	public enum POPAnimationClampFlags : ulong
		None = 0uL,
		Start = 0uL << 1uL,
		End = 1uL << 1uL,
		Both = kPOPAnimationClampEnd | kPOPAnimationClampStart
Comment 1 Aaron Bockover [MSFT] 2015-03-15 12:34:19 UTC
Turns out this was specifically an issue with names starting with a 'k[UppercaseLetter]' prefix. The 'k' was being stripped before the original name was registered for remapping.