How to disable mousewheel in MudBlazor's MudNumericField - mudblazor

my MudNumericField look like this:
<MudNumericField #bind-Value="To" Label="To" Variant="Variant.Outlined" Step="1M" ReadOnly="true" HideSpinButtons="true" />
Despite being Readonly I can change its value using mousewheel (pressing shift key). Is it a bug?

Yes, it's likely a bug. It has been resolved in 6.0.5 version of Mudblazor however.
Source: https://github.com/MudBlazor/MudBlazor/releases/tag/v6.0.5

Related

Can't change system font to custom font in Xcode 11 Beta

I'm trying to change the font of a UILabel to a custom font but the option is locked and says 'Custom (non installed)', but I do have custom fonts in fact it works fine in Xcode 10
Right now, it's not working in XCode 11 beta but you can follow one workaround. Change text style from Plain to Attributed. It allows you to change the font.
If you don't want to do it by install the font on the mac. It is also possible in the XML of the xib:
Add the following inside <document> tag. Usually bellow </dependencies> tag.
<customFonts key="customFonts">
<array key="Roboto-Medium.ttf">
<string>Roboto-Medium</string>
</array>
<array key="Roboto-Regular.ttf">
<string>Roboto-Regular</string>
</array>
</customFonts>
changing for your custom font.
And inside <label> tag:
<fontDescription key="fontDescription" name="Roboto-Medium" family="Roboto" pointSize="18"/>
You should see something like:
Custom font
Upgrade to Xcode 11 Beta 5. That solved it for me.

IntelliSense: aria-valuemax and data-ng-style aaaargh?

While typing code in a Razor (.cshtml) file using Visual Studio 2013 (Update 4) with ReSharper 8.2.3 (updated by suggestion from this question), my IntelliSense is doing stuff that is driving me crazy. I am a heavy user of the IntelliSense+Tab key when typing to speed up my coding, but some common keywords keep defaulting to suggestions that aren't as intuitive as you'd think. Examples:
<input type="whatever" value="something" /> prefers aria-valuemax instead of value:
<input type="whatever" style="yada yada" /> prefers data-ng-style instead of style:
I know this is a niggling thing, but it is driving me nuts, and it seems to me that IntelliSense should be preferring value and style here simply because what I'm typing does not start with aria and data in the respective examples. Does anyone know how to turn this behavior off?
This is the AngularJS plugin for ReSharper. The latest version is a bit more sane with respect to item ordering and will choose style over data-hg-style. However, most of this goodness comes from ReSharper itself, and the latest version of the plugin requires ReSharper 9.1.

inline disable button not working in Firefox

I have two buttons, which are initially disabled
<button class="back" id="back" disabled="true">Back</button>
<button class="forward" id="next" disabled="true">Next</button>
Safari and Chrome read it just fine
But Firefox does not
I'm running FF 26.0. Removing ="true" doesn't fix it.
I don't know why, but after restarting FireFox, it works again. Weird...
I'm not sure which version of firefox you are using, but the latest version (26.0) seems to have no trouble disabling the button. In either case, you do not need to specify "true" or "false". Simply put
<button class='back' id='back' disabled>Back</button>
<button class='forward' id='next' disabled>Next</button>
W3 Disabled Attribute

Microsoft.Phone.Controls.Toolkit ListPicker throws XamlParseException

After being advised that the native ComboBox was not the way to go I was told to look at the Silverlight Toolkit ListPicker. So I did and have got a problem.
I opened a new project and pulled a new ListPicker onto the MainPage. The ListPicker looks like:
<toolkit:ListPicker x:Name="Result">
<toolkit:ListPickerItem Content="Win" />
<toolkit:ListPickerItem Content="Place" />
<toolkit:ListPickerItem Content="Lose" />
</toolkit:ListPicker>
When trying to run this I get an XamlParseException with InnerException of InvalidProgramException. All I did was drag the control on, and add some ListPickerItem. Removing the items still results in the error, removing the ListPicker control completely allows the page to be shown with no error.
I'm sure I've missed something, but any documentation I have read seems to point towards this markup being fine, including http://windowsphonegeek.com/articles/listpicker-for-wp7-in-depth
I can provide any other info required.
ListPickerItem is a class used internally by the ListPicker and should not be used directly.
If you just want to add a list of items, you can use strings to do it, like this:
Add a new namespace on top of the Page to access the String class:
xmlns:sys="clr-namespace:System;assembly=mscorlib"
Then, just change the ListPicker code to this:
<toolkit:ListPicker>
<sys:String>Win</sys:String>
<sys:String>Place</sys:String>
<sys:String>Lose</sys:String>
</toolkit:ListPicker>
The problem was that the wrong dlls had been registered, i.e. 7 and not 7.1. I had to uninstall and reinstall to get it to update correctly and it worked.

Binding to x:Name in XAML breaks my app in Mango

This line works in Windows Phone 7.0 but not in 7.1 (NullReferenceException thrown). Note that I checked that Name is never null or empty.
<CheckBox x:Name="{Binding Name}" Content="{Binding Label}" />
Removing x:Name, all things being equal, prevent the app to crash. Why is that ?
You can't bind x:Name , it's the equivalent of declaring a variable in C#. And it doesn't make sense to do either, as it's not a visual property.
Surely you meant to bind the Header property of the CheckBox?
My openion is Name property didn't take at runtime.
When you upgraded from 7.0 to 7.1 the xmlns:x in your header might be wrong. create a brand new page and make sure that that line is the same.

Resources