Re: [Tile-dev] Style settings precedence

[Jeff H. <je...@ac...>]

My reading of your list ordering had me questioning immediately the sense of
#1 and #2 order.  I don't know that I'm relying on it (I have various
specialized bits), but I would vote to modify it regardless.

Jeff

Joe English wrote:
> Currently, the Tile theme engine uses the following 
> precedence order for computing element options:
> 
>     1. Dynamic settings specified by [style map ...]
>     2. Widget options specified by [$w configure ...]
>     3. Style defaults specified by [style configure ...]
>     4. Built-in defaults supplied by the element
> 
> So [style map ...] settings override widget settings.
> 
> If I remember correctly, the rationale for this order was so 
> that [style map ...] settings would act the same way as the 
> state-specific widget options like "-activeforeground" that 
> they replaced.  
> 
> However, I can't think of any use cases where this ends up 
> being helpful, and there's at least one case where it's 
> undesirable (see #1517110).  I'm starting to think that #1 
> and #2 should be swapped, so that widget options always take 
> precedence.
> 
> Any thoughts?  Is anyone relying on the current behavior?