On Sunday 22 June 2003 02:03 pm, Brent Vukmer wrote:
> Thanks, Daniel -- particularly for the tip about the menu!
>
> I don't know what happened with the variable names -- all of a
> sudden, when I did an "accept", the code got auto-formatted and the
> variable names turned into weird temp var names.  Really ticked me
> off -- but I don't know how to fix it!

Did you have the control-key down? (like if you have the ctrl/alt keys 
swapped and hit ctrl-S this happens sometimes).

> I'm still thinking about how to build the "summary comments" UI.  I
> don't want to make it too complicated, but I want to clue people in
> that they don't need to enter parens or QA tags in that field.
>
> I do intend to add the closed/approved/update QA tags to the UI,
> with some kind of "are you sure that you want to do this?"
> confirmation popup.
>
>
>
> -----Original Message-----
> From:	Daniel Vainsencher [mailto:danielv at netvision.net.il]
> Sent:	Fri 6/20/2003 1:45 PM
> To:	The general-purpose Squeak developers list
> Cc:
> Subject:	Re: [ANN] BugFixArchiveViewer 1.18 on SqueakMap
> Looks good. Comments -
> * I don't know why, but I'm seeing t1, t2 style temporary var
> names. Maybe something wrong with the fileout?
> * The menu disappears when something is clicked. Add stayUp: true
> near end of #buildQaTagsPane.
> * $( characters are allowed in the subject comments, which can
> disrupt the BFA. The quick and brutal fix is
> summaryComments
> 	^ summaryComments copyWithoutAll: '()'
>
> I think other than those, it is ready to deploy.
>
> BTW, why not consider [closed][approved][update] to be tags? (not
> that I mind them not being part of the default UI, since they
> should be used only by relatively few people).
>
> Daniel

-- 
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE