I am confused over the use of "default" skin terminology
In the Configure Project dialog I select a skin that is supposedly the "default".
Let's use Metro, since it is very distinctive.
If I go to RadMenu tasks I can also select a "default" skin which is different from Metro. (basically shades of gray)
If I edit the HTML and change "skin="default" to "skin="" then I get something else entirely.
Removing "skin=" completely gives the the default project skin of Metro, as intended.
However, when I go back to RadMenu tasks, the skin remains listed as "default".
It seems to me that the term is overloaded.
I am also finding differences with Metro Touch, where I don't get the project default, and need to specify the skin explicitly for certain controls. Since that skin was just released, I think it will take a while for consistent integration. But those issues brought the confusion (in my mind) to the forefront.
Can anyone explain what is going on?
In the Configure Project dialog I select a skin that is supposedly the "default".
Let's use Metro, since it is very distinctive.
If I go to RadMenu tasks I can also select a "default" skin which is different from Metro. (basically shades of gray)
If I edit the HTML and change "skin="default" to "skin="" then I get something else entirely.
Removing "skin=" completely gives the the default project skin of Metro, as intended.
However, when I go back to RadMenu tasks, the skin remains listed as "default".
It seems to me that the term is overloaded.
I am also finding differences with Metro Touch, where I don't get the project default, and need to specify the skin explicitly for certain controls. Since that skin was just released, I think it will take a while for consistent integration. But those issues brought the confusion (in my mind) to the forefront.
Can anyone explain what is going on?