[web2py] Re: Clockpick

2010-11-12 Thread winti
for me as well, since 1.89.1 clockpick appears as villas describes. On Nov 12, 9:23 pm, villas wrote: > Hi All, > > The latest upgrade seems to have broken Clockpick.  The times now > appear in the top teft corner of the screen instead of adjacent to the > input.  I've played around with it,  but

[web2py] Re: Clockpick

2010-11-12 Thread villas
Hi All, The latest upgrade seems to have broken Clockpick. The times now appear in the top teft corner of the screen instead of adjacent to the input. I've played around with it, but I couldn't see what's wrong. To test it, just add a DB table to the Welcome app containing a time field and the

[web2py] Re: Clockpick

2010-11-02 Thread villas
Hi M Well, I did check truck. However the header of calendar.js still says Version 1.2.4 so I didn't know that you had done it. When you next get the chance, please update the header too :) Thanks for attending to this, D On Nov 1, 8:29 pm, mdipierro wrote: > changeset:   1032:532ac00026

[web2py] Re: Clockpick

2010-11-01 Thread mdipierro
changeset: 1032:532ac00026ea user:mdipie...@massimo-di-pierros-macbook-2.local date:Wed Oct 13 09:31:07 2010 -0500 summary: clockpick 1.28, thanks villas On Oct 13, 6:39 am, villas wrote: > Massimo, > I know that clockpick is not everyone's favourite, but until something >

[web2py] Re: Clockpick

2010-11-01 Thread mdipierro
I am pretty sure I did this. Did I not? Did I miss something? On Oct 13, 6:39 am, villas wrote: > Massimo, > I know that clockpick is not everyone's favourite, but until something > better comes... I wonder whether you would consider updating it from > 1.24 to 1.28 in calendar.js? > > The upgrade