9 Answers, 1 is accepted
0
Hi Patrick,
I've tried to replicate the same behavior, however to no avail.
May you verify whether you have merged Office2013ResourceDictionary in App.xaml?:
I'm attaching you small sample demo, that I used for testing purposes.
Would it be possible to take a look at the attachment and let us know how it differs from yours?
Any additional version about the version you used will be highly appreciated, as well.
Regards,
Vanya Pavlova
Telerik
I've tried to replicate the same behavior, however to no avail.
May you verify whether you have merged Office2013ResourceDictionary in App.xaml?:
<
Application
x:Class
=
"TextBoxDisabled.App"
xmlns:telerik
=
"http://schemas.telerik.com/2008/xaml/presentation"
StartupUri
=
"MainWindow.xaml"
>
<
Application.Resources
>
<
ResourceDictionary
>
<
ResourceDictionary.MergedDictionaries
>
<
telerik:Office2013ResourceDictionary
/>
<
ResourceDictionary
Source
=
"System.Windows.xaml"
/>
</
ResourceDictionary.MergedDictionaries
>
</
ResourceDictionary
>
</
Application.Resources
>
</
Application
>
I'm attaching you small sample demo, that I used for testing purposes.
Would it be possible to take a look at the attachment and let us know how it differs from yours?
Any additional version about the version you used will be highly appreciated, as well.
Regards,
Vanya Pavlova
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Patrick
Top achievements
Rank 2
Iron
Iron
Iron
answered on 09 Apr 2014, 03:07 PM
Hello Vanya,
I can not reproduce it with your example, but I see it in my application.
The main differences are that my control is inside a document pane that is part of a docking, that the enable/disable is made using a button and that the data context is changed by code after the control is displayed.
I will make tests to look at the condition that makes the problem and add a new reply.
Patrick
I can not reproduce it with your example, but I see it in my application.
The main differences are that my control is inside a document pane that is part of a docking, that the enable/disable is made using a button and that the data context is changed by code after the control is displayed.
I will make tests to look at the condition that makes the problem and add a new reply.
Patrick
0
Patrick
Top achievements
Rank 2
Iron
Iron
Iron
answered on 10 Apr 2014, 05:00 AM
Hello Vanya,
here is a test case that reproduce the problem.
The main difference is that I have loaded the resources as specified in the documentation:
What is the purpose of the <telerik:Office2013ResourceDictionary/> resource specification?
It is mentionned nowhere in the documentation!!!!
Even adding it to my test case, the border is not displayed!
But the border is displayed when you click on the TextBox.
Patrick
here is a test case that reproduce the problem.
The main difference is that I have loaded the resources as specified in the documentation:
<
ResourceDictionary.MergedDictionaries
>
<
ResourceDictionary
Source
=
"/Telerik.Windows.Themes.Office2013;component/Themes/System.Windows.xaml"
/>
</
ResourceDictionary.MergedDictionaries
>
What is the purpose of the <telerik:Office2013ResourceDictionary/> resource specification?
It is mentionned nowhere in the documentation!!!!
Even adding it to my test case, the border is not displayed!
But the border is displayed when you click on the TextBox.
Patrick
0
Patrick
Top achievements
Rank 2
Iron
Iron
Iron
answered on 10 Apr 2014, 05:09 AM
Vanya,
just something that could be important: you were using version 2014.1.224.45 of the Telerik controls and I am using version 2014.1.331.45.
I will create a support ticket for the test case.
Patrick
just something that could be important: you were using version 2014.1.224.45 of the Telerik controls and I am using version 2014.1.331.45.
I will create a support ticket for the test case.
Patrick
0
Hello Patrick,
As a kind of follow up, I've updated the project you have already sent. Indeed, there is a difference between these versions. Actually we are talking about the IsReadOnly state of the TextBox, not about the disabled one. Looking back, we had an internal discussion and designer's review of this theme and the IsReadOnly state of the TextBox was changed, following the design guideline. When the TextBox enters this state the outer border of this element should not be visible to the end-user and that should be the expected behavior.
Regards,
Vanya Pavlova
Telerik
As a kind of follow up, I've updated the project you have already sent. Indeed, there is a difference between these versions. Actually we are talking about the IsReadOnly state of the TextBox, not about the disabled one. Looking back, we had an internal discussion and designer's review of this theme and the IsReadOnly state of the TextBox was changed, following the design guideline. When the TextBox enters this state the outer border of this element should not be visible to the end-user and that should be the expected behavior.
Regards,
Vanya Pavlova
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Patrick
Top achievements
Rank 2
Iron
Iron
Iron
answered on 10 Apr 2014, 03:47 PM
Vanya,
the result of this change is not good: the TextBox control has no border, but other controls, such as DateTimePicker or ComboBox, that must be disabled, have a border. That doesn't look good.
Patrick
the result of this change is not good: the TextBox control has no border, but other controls, such as DateTimePicker or ComboBox, that must be disabled, have a border. That doesn't look good.
Patrick
0
Hi Patrick,
We had the same discussion on that matter. If you remove the outer Border of RadDateTimePicker and RadComboBox in ReadOnly state it's strange, indeed.
We finally decided to keep the behavior, which is by design.
Any attempt to revert back these changes could lead to a potential breaking change, that we want to avoid.
Currently, if you need this Border, I may suggest you to modify the template of TextBox against Office2013
theme and remove the animation that resets the BorderThickness of the root container.
Hope this helps.
Regards,
Vanya Pavlova
Telerik
We had the same discussion on that matter. If you remove the outer Border of RadDateTimePicker and RadComboBox in ReadOnly state it's strange, indeed.
We finally decided to keep the behavior, which is by design.
Any attempt to revert back these changes could lead to a potential breaking change, that we want to avoid.
Currently, if you need this Border, I may suggest you to modify the template of TextBox against Office2013
theme and remove the animation that resets the BorderThickness of the root container.
Hope this helps.
Regards,
Vanya Pavlova
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Patrick
Top achievements
Rank 2
Iron
Iron
Iron
answered on 18 Apr 2014, 04:46 AM
Hello Vanya,
look at this screen shot to see how it looks bad when you mix a read-only TextBox to other controls.
The TextBox is read-only, because this lets the user select the content to copy it.
Patrick
look at this screen shot to see how it looks bad when you mix a read-only TextBox to other controls.
The TextBox is read-only, because this lets the user select the content to copy it.
Patrick
0
Hello Patrick,
Thank you for the followup. I will forward your feedback to our developers for further investigation.
Regards,
Vanya Pavlova
Telerik
Thank you for the followup. I will forward your feedback to our developers for further investigation.
Regards,
Vanya Pavlova
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.