Hi, Here is a patch for the ``dataseq-operations-action'' function that makes remove the integer parsing on object ids.
I know this would break most applications which makes use of dataseqs and its sublcasses, but I think it's more correct to not assume that an id is always a number. Please, let me know what you think about it. Thanks, Andrea. -- Software vuol dire conoscenza! Per questo dev'essere un bene comune! Usa software libero e contribisci a cambiare il mondo: http://www.softwarelibero.it http://www.fsf.org http://www.gnu.org
-- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
# HG changeset patch # User Andrea Russo <[email protected]> # Date 1309184591 -7200 # Node ID 2cec47487822d8e4118c1385dc9b2f354b09c514 # Parent dde87661f2512dce4b5fc51ca1b9bac308102722 Don't assume tha object ids are always integers in ``dataseq-operations-action''. diff -r dde87661f251 -r 2cec47487822 src/widgets/dataseq/operations-action.lisp --- a/src/widgets/dataseq/operations-action.lisp Mon Jun 27 16:09:43 2011 +0200 +++ b/src/widgets/dataseq/operations-action.lisp Mon Jun 27 16:23:11 2011 +0200 @@ -12,7 +12,7 @@ (dataseq-clear-selection obj) (loop for i in (request-parameters) when (string-starts-with (car i) "item-") - do (dataseq-select-item obj (parse-integer (substring (car i) 5)))) + do (dataseq-select-item obj (substring (car i) 5))) (loop for i in (append (dataseq-item-ops obj) (dataseq-common-ops obj))
