Bug 30332 - on iOS setting button title animates.
Summary: on iOS setting button title animates.
Status: RESOLVED INVALID
Alias: None
Product: Forms
Classification: Xamarin
Component: iOS ()
Version: 1.4.3
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-05-21 22:48 UTC by George Cook
Modified: 2015-05-21 23:14 UTC (History)
0 users

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 INVALID

Description George Cook 2015-05-21 22:48:51 UTC
it's a ridiculous default behaviour from apple. It's very easy to turn off. But to do so requires that you wrap the call that set's the button text in setAnmation enabled calls, as such:

[UIView setAnimationsEnabled:NO];
[_button setTitle:@"title" forState:UIControlStateNormal];
[UIView setAnimationsEnabled:YES];

We can obviously do this in c# for iOS apps; but for Xamarin forms, we can't do this for the Button class.

it'd be insane for us to have to completely write our own button class from scratch just to get this behaviour, when you guys can just add 2 lines to your renderer (wrap the setting of the text). At most you'd need to add a property to enable/disable this absolutely terrible default behaviour.
Comment 1 George Cook 2015-05-21 23:14:50 UTC
thinking about it (with help as always from adam kemp), you guys shouldn't do this, as it's the standard iOS behaviour and while it's really silly, it'd be inconsistent to have a flag to turn it off just for iOS.