I have lots of gridedit widgets created like this:
(defun admin-tags-page ()
(make-instance 'gridedit
:name 'tags
:data-class 'tag
:view 'tag-table-view
:item-form-view 'tag-form-view))
You'll notice that there is no :item-data-view specified -- it should
not be necessary, as the gridedit widget displays data using the table
view and allows editing using the form view. Nobody ever displays the
data using a data-view.
There has been a regression in weblocks, and I can't seem to find
it. The problem is with dataform, its render-dataform-form function. See
the (when break-out) clause -- it switches the ui-state to :data. This
in itself is not a big problem, unless the form actually gets
rendered -- in my case, there is no data view, so this will fail.
I am not sure where the problem is -- is it the state switching in
dataform, or gridedit trying to render the form in the :data state
(which should not happen). I am sure that the problem wasn't there
several months ago.
Could this be related to my logs being flooded with these messages?
STYLE-WARNING: During the rendering phase, #<GRIDEDIT MYAPP::TAGS> was
marked dirty and skipped after already being rendered, which should
typically be done only during action handling
I am unable to track this down, so help and/or suggestions would be very
much appreciated.
--J.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---
