That's OK. I'm not sure with the styling of the Export at bottom of the screen but no biggy.
The main issue that I'm working through is the a working app in a trunk from 2012-07-21 is broken in the current trunk. One issue appears to be related to the auth_users table. Would not play nicely with 2012-08-19 and the fix was to delete the table and manually recreate it. (couldn't see any reason from tools.py, as table defs looked the same) An unresolved issue is with a .represent link loading the calling, rather than the called form in the target div (2012-07-21 works perfectly) i.e. db.RaceData.date.represent = lambda value,row: A(value, callback=URL(app, "race","Rcard",args=[row.date,row.course]),target="Rcard") On Friday, 24 August 2012 11:58:41 UTC+10, Massimo Di Pierro wrote: > > Yes. The grid was an experimental feature in 1.99.7. We are still making > minor tweaks to it. > The query button is gone because its effect can be achieved by giving > focus to the search input. > The add button moved up to save space. > The export feature has been improved. There are many export options and we > thought a good way was to add links at the bottom. > > Notice that the old export form was problematic because did not work well > with LOADed grids. > > Anyway, it should not break existing functionality. Doesn't it look better > now? > > Massimo > > On Thursday, 23 August 2012 20:47:03 UTC-5, Simon Ashley wrote: >> >> Its appears that SQLFORM.grid formatting has changed recently in the >> trunk: >> (with no change to the application) >> >> >> - The Query button has been dropped, >> - Add button moved to on top of the query field. >> - Export function changed from before the table to after with >> hyperlinks options rather than drill down box selections >> >> >> Is this an intentional move? >> >> >> <https://lh6.googleusercontent.com/-_QRTUDjLW0s/UDbbjh6lYVI/AAAAAAAAADg/JFjcfzZV0us/s1600/grid+example+1png.png> >> >> --
