Wednesday, February 18, 2015

Discovered and fixed a bug introduced by the new untested feature get_master_instance. When master was ContentType (which is the case on every XxxByController` table), Lino did not correctly set the master_instance of the action request (a TableRequest). Added a section to Integration Service which would have detected this.

lino_xl.lib.cal.AppointmentsByPartner (Table “Rendez-vous” dans l’onglet “Personne” ) no longer removes events more than 17 days in the future. And it now shows events in correct sort order.

Checkin and upgrade in CPAS de Châtelet.

maximum recursion depth exceeded

The new method lino.core.actions.Action.get_status() introduced yesterday came with another bug: trying to insert a pcsw.Client caused a RuntimeError maximum recursion depth exceeded while calling a Python object. This triggered another internal revolution in the action API (which still is unstable and has only very basic documentation https://www.lino-framework.org/dev/ar.html):

• the ar.insert_button() method is gone!

• More subtle changes around ar.get_permission, ar.spawn(), BoundAction.request_from. ar.spawn_request and a parent keyword to the contructor.