[Mono-bugs] [Bug 633503] New: UIActionSheet Stacking Order Incorrect (puts cancel button at the top)

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=633503

https://bugzilla.novell.com/show_bug.cgi?id=633503#c0


           Summary: UIActionSheet Stacking Order Incorrect (puts cancel
                    button at the top)
    Classification: Mono
           Product: MonoTouch
           Version: SVN
          Platform: Macintosh
        OS/Version: Mac OS X 10.6
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Class Libraries
        AssignedTo: gnorton at novell.com
        ReportedBy: tbaker000 at hotmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8

string[] buttonTitles = new string[] { "Button 1", "Button 2" };
UIActionSheet actionSheet = new UIActionSheet(title, actionSource, "Cancel",
null, buttonTitles);

This results in a button stacking order of "Cancel", "Button 1", "Button 2"
whereas the same code in Objective-c results in a stacking order of "Button 1",
"Button 2", "Cancel".

Note: Simply adding the Cancel to the end of buttonTitles instead of passing to
the actionsheet constructor is not a work around since the cancel button is a
different color and slightly offset when displayed. Okay I guess it is a work
around but not very aesthetic :)

Reproducible: Always

Steps to Reproduce:
string[] buttonTitles = new string[] { "Button 1", "Button 2" };
UIActionSheet actionSheet = new UIActionSheet(title, actionSource, "Cancel",
null, buttonTitles);
Actual Results:  
"Cancel"
"Button 1"
"Button 2"

Expected Results:  
"Button 1"
"Button 2"

"Cancel"

Software: Latest everything including iOS 4.0.2 and
monotouch 3.0.11


Monotouch rocks! :)

Thanks!

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.