Heya Nils...

This will take a few messages to get everything explained...

First off... in your proc, you're grabbing the next object_id from the sequence... which is the same thing that happens when you pass "" for object_id to acs_object__new...

So you could do:

ad_proc -public mfp::note::add {
    -title:required
    -item_id
} {
    This proc adds a note.
} {
    if { ! [info exists item_id] } {
        set item_id ""
    }

    :
    :
}

and get a similar result (note also replacing "c eq 0" with "! c"; eq is a string compare, == is numeric)

More to come (about why even have the item_id come into the func if it's to be a new object) later :)

(quote)tutorial code shouldn't be needed to be fixed...(/quote)

Yes, there is that...

BUT

you got the app working?

Sometimes I think, "why not leave this bug in" so that the tutorial includes a small challenge...

Other times, I think it would be better if it were fixed.

If you read the bug report you'll see my {here's the point of passing in the item_id as received from the item_id key field of the form} comment, and you'll also see that I didn't put the type of posting right so you have to scroll to the right a lot to read it...

Anyway, the double-click thing is not unique to openacs, but not everyone gets that right. As an exercise, alter your app so that it passes the key from the form into the note__new call.