Use json_encode to encode values for the autocomplete boxes.
syntax bug fixes for add-one subform option
Track vertical pos on save and reload there
Add awareness of radios to subform default creation

New subform entries pickup the default values for elements  in the
subform that have defaults specified. But only for certain element types
we've bothered to make this logic for.  Now radio buttons are included.
Default to colheads when dealing with calcs
Initialize and return $entryMap

This way, you can call cloneEntry and get a list of the new entries that
were created.  The array is keyed by form and entry id and the values
are the newly created cloned entries that correspond to the entry_id
keys.
Sep multiple values with linebreak only, no commas
Merge pull request #101 from jegelstaff/pickup-defaults-for-radios

Add awareness of radios to subform default creation
Merge pull request #99 from jegelstaff/subform-add-one-at-a-time

syntax bug fixes for add-one subform option
Merge pull request #100 from jegelstaff/set-scroll-position

Track vertical pos on save and reload there
Merge pull request #98 from jegelstaff/json-encode-quickselect

Use json_encode to encode values for the autocomplete boxes.
Set add-one button as default choice
Removing unnecessary stripslashes
Add flag to pres. quicksearches when load reports

Instead of resetting all columns to match the values saved in the
report, we now keep any values the user has typed in/selected.  If the
report has a diff. value for a given column then the value from the
report will replace the user value. Other user values will remain in
place and not be neutered.
Moving processing of custom buttons

This way, we can handle custom button actions before the data is
gathered, so modifications are reflected properly, etc.
Moving calculation processing up

This needs to happen right after the getData for the list of entries, so
that the calculation process (which relies on work getData does to build
the proper query for sums, etc) gets the actual info it needs from the
actual query for that page, and not from some interceding getData
process that might have run in a template or somewhere else.
Adding "raw" calculation result to print process

This allows for templating/formatting of the results more easily. For
now, we're just making the counts show up differently, but this
can/should be extended to all types and the whole calculation process
simplified.
Updating text

Mostly related to AOHC
Converting file to UTF8
Adding login redirect for anon Drupal users