I forgot to mention that adding a mark-dirty call to the end of dataedit-add-items-flow does fix the problem, though I'm not sure if that's the correct place to put it.
On Wednesday, January 21, 2015 at 8:50:44 AM UTC-8, Jason Miller wrote: > > Quicklisp just updated the version it has, and after updating, I noticed > that the gridedit "Add" doesn't force a redraw, so has no effect. Is that > related to this change? > > On Friday, January 16, 2015 at 3:50:43 PM UTC-8, o_z wrote: >> >> I will fix widgets bugs if they appear but not going to check all >> widgets. Weblocks selenium tests work now, that's enough for me at this >> point. >> >> суббота, 10 января 2015 г., 12:34:37 UTC+2 пользователь Daniel Borchmann >> написал: >>> >>> ghItlhpu' o_z <[email protected]>: >>> > 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. >>> >>> Ok, I see your point. Are you now going through all the widgets built >>> in in weblocks and see where `MARK-DIRTY` or `:AFFECTS-DIRTY-STATUS-P T` >>> is neccessary? I had some trouble with gridedit now updating >>> automatically when I wanted to add a new item (but recent commits in the >>> main repository may have fixed that; I will it out soon). >>> >>> Best, >>> >>> 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.
