Hi, I've met situation where too many widgets were rendered only because their slots values were changed. For any widget there are only few slots on which widget state depends. So there is no need to have :affects-dirty-status-p T for any slot. Yes, it would require new major release number but let it be as it is. I think :affects-dirty-status-p set to T by default is a mistake. It helps to avoid some (mark-dirty ...) statements but gives restrictions for cases where some widgets should not be rendered.
Thanks for response. суббота, 3 января 2015 г., 11:10:06 UTC+2 пользователь Daniel Borchmann написал: > > > Hi, > > In df17f29, the default value for :affects-dirty-status-p was changed > From t to nil. I find this change quite severe, as it breaks backward > compatibilty and a lot of existing weblocks code (including mine). If > we would follow semantic versioning, this would even require a new major > release number. My wish would be to revert this change. > > The corresponding commit refers to a “repeated rendering bug.” Can > somebody please elaborate what this is exactly? And, if it can be fixed > by changing the default value of :affects-dirty-status-p, couldn't we > just as well add some explicit statments like `:affects-dirty-status-p > nil` for the widgets involved in the particular instance of this bug? > > Thanks for maintaining weblocks! > > Daniel > > -- > Daniel Borchmann http://daniel.kxpq.de > GPG (Mail) 0849 473E 6BF0 B504 DF0B D640 455E 3610 01FF 778F > -- You received this message because you are subscribed to the Google Groups "weblocks" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/weblocks. For more options, visit https://groups.google.com/d/optout.
