Bug 2578 - Notification.LedOnMS is no longer an int in 4.0.1
Summary: Notification.LedOnMS is no longer an int in 4.0.1
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 4.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Atsushi Eno
Depends on:
Reported: 2011-12-19 19:23 UTC by Redth
Modified: 2014-04-04 07:16 UTC (History)
3 users (show)

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 Redth 2011-12-19 19:23:19 UTC
In 4.0.1, the Notification.LedOnMS and Notification.LedOffMS properties have been changed to NotificationFlags type, instead of int to allow specifying of a milliseconds value.
Comment 2 Atsushi Eno 2011-12-19 23:19:11 UTC
True, that was a wrong enum transition. It is fixed in our source tree for next release. Thanks.
Comment 3 Udham Singh 2014-03-28 08:20:25 UTC
I have checked this issue on following builds:

Windows 8.1
Xamarin Studio : 4.2.3 (build 60)
Xamarin.Android : 4.13.0 (Business Edition)

Screencast: http://screencast.com/t/tSeJo5CF0V

This issue is working fine. Hence, I am closing this issue.
Comment 4 Udham Singh 2014-04-04 07:16:06 UTC
Please ignore the screencast of comment 3, consider this screencast for comment 3 : http://www.screencast.com/t/EZfE3igt3