| New Implementation. - a new macro, addedValueMacros.searchCalendar, can build a blog-like
calendar for navigating through the results of any search, as long as
it it ordered by a date valued variable. To make layout of reports
and templates easier, it can appear anywhere on a page where the
search was done - even outside of the search report. The parameters
are unusual, the first is the "customKey" that addedValues uses as a
unique label for each search , you can obtain this within a search
report using [[addedValues customKey:0000]]; the second is the number
of the first hit in the page - in search reports this is
[[firstPageHit]] . These values can be saved in temporary page
storage and passed to a call to searchCalendar *outside* of the
report with the pageNote macro. - the default value of timestamp variables could previously be set to
a specific date and time only. Now , these variables default value
can be the time of day at which the value was requested. When a form
rendering for timestamp variables is chosen, selecting the Initial
value of variable-name value will return the actual value when one
exists, otherwise the default value. This allows timestamp renderings
to always show the time of day (on the server). Bug fixes - a bug introduced in thetinyMCE implementation in addedValues 1.0.2,
where help and color picker and other popup windows didn't load
correctly. Fixed. - the createAsite postprocessor reported errors as occurring in
emailForm, not createAsite. Fixed. - loading a dumped schema file did not deal correctly with filenames
that already had a suffix. Fixed. - a script that handled ETP special actions when renaming a form, was
never shipped. Fixed. Known issues - none. Enjoy!
-- - David Bayly. Programmer and digest reader. dbayly at udena dot ch
Digest Readers do it once a day.
|
