Take the standard FirstLook demo for RadNumericTextBox and change the box to include the attribute Value="0". Now try entering the value .25 (without the leading 0). The number gets turned into "25" without the leading decimal. This is going to confuse my users who are used to entering numbers without looking at the screen.
Also, when I have Enabled="false" shouldn't it use the Disabled CSS overridden by whatever I put in <DisabledStyle /> ? I have
Also, when I have Enabled="false" shouldn't it use the Disabled CSS overridden by whatever I put in <DisabledStyle /> ? I have
<
DisabledStyle BackColor="gainsboro" ForeColor="black" Font-Bold="true" />
and it seems to ignore the ForeColor (it shows a dark gray forecolor instead). This is less important than the first problem, just wanted to see if there was a good workaround.4 Answers, 1 is accepted
0
Hi Andy,
The issue with the leading zero seems to be a bug and we have updated your Telerik points. As soon as our developers fix it we will send you a hotfix for the problem.
Concerning the ForeColor of a disabled RadInput control, it can not be changed under IE (note that under other browsers the color is respected). The same behavior is observed for all disable input controls under IE (you can test with an asp textbox control).
Best wishes,
Petja
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
The issue with the leading zero seems to be a bug and we have updated your Telerik points. As soon as our developers fix it we will send you a hotfix for the problem.
Concerning the ForeColor of a disabled RadInput control, it can not be changed under IE (note that under other browsers the color is respected). The same behavior is observed for all disable input controls under IE (you can test with an asp textbox control).
Best wishes,
Petja
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Hi Andy,
Find attached the latest unofficial Prometheus hotfix build which addresses the issue. Please, give it a try and let us know if you have further questions.
Greetings,
Petja
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Find attached the latest unofficial Prometheus hotfix build which addresses the issue. Please, give it a try and let us know if you have further questions.
Greetings,
Petja
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Andy F.
Top achievements
Rank 1
Iron
Rank 1
Iron
answered on 25 Jan 2008, 05:33 PM
Can't use this hotfix. It's messing with the widths of things in the RadPanels (my 100% width grid in a RadPanel is being sized to about 55% of the total width of the panel; in the Jan 15 release, it's 100% width), so there are some additional changes that snuck into this hotfix that are not quite ready for prime time and I couldn't get to the areas where I needed to test it.
0
Hi Andy,
Please, send us a sample code or a project which we can reproduce the problem with so we could fix the RadInput as soon as possible. Thank you for your cooperation.
Best wishes,
Petja
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Please, send us a sample code or a project which we can reproduce the problem with so we could fix the RadInput as soon as possible. Thank you for your cooperation.
Best wishes,
Petja
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center