WPFfor d

[Adam Wilson]

On Tue, 19 Feb 2013 23:37:58 -0800, Jacob Carlborg <doob at me.com> wrote:

> On 2013-02-19 21:43, Adam Wilson wrote:
>
>> My point is that I should not have to rebuild a scrollbar from the
>> ground up when I want to make it look different. Or button, or textbox,
>> or whatever. When I need scrolling functionality I just use a scrollbar
>> then style it for the required usage, in many ways this vastly reduces
>> improper widget function due to being able to apply a standard
>> implementation to a much wider variety of usages, I have ListBoxes in my
>> WPF projects that you'd have no idea were just ListBoxes because the
>> look nothing like an OS ListBox For example one ListBox I have looks
>> more like a TreeView, except that I didn't actually need the TreeView
>> capability, I just need to make it LOOK like one. I also usually add
>> some useful visuals that the OS widget could never do.
>
> Most in most tool kits you can override a drawing function or specify  
> some properties to change to look of a control.
>

Most allow you to tweak certain aspects, not remove the entire rendering  
output and start over. I've never found any OS widget kit that allows  
completely and total control of the widget at the pixel level.

-- 
Adam Wilson
IRC: LightBender
Project Coordinator
The Horizon Project
http://www.thehorizonproject.org/