It shouldn't result in a default; it should raise an exception. This dialogue is used in several places and if the user cancels then the operation that caused the dialogue should handle the exception to do sometihng more meaningful; cancel the SystemNavigation>>#browseMyChanges for example.

> On 2020-02-25, at 9:25 AM, Thiede, Christoph <Christoph.Thiede at student.hpi.uni-potsdam.de> wrote:
> 
> If we choose a default value, I would vote for 'xyz'. It's more obvious than "anon" IMO ...
> However, the use cases for not entering user initials should be very rare, shouldn't they? It would be a pity if people "clicked that pop up away" and committed to what repository/changeset ever all under the same default value. Why can't we leave the situation as is?
> 
> Best,
> Christoph
> Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von K K Subbu <kksubbu.ml at gmail.com>
> Gesendet: Dienstag, 25. Februar 2020 16:11:49
> An: John Pfersich via Squeak-dev
> Betreff: Re: [squeak-dev] Infinite dialog loop in authorinitials
>  
> On 25/02/20 7:45 PM, Marcel Taeumel wrote:
> 
> > I think we will leave this for 5.3. I am happy to change it to some 
> > default value after the release.
> > 
> > We could return a default value for those calls to #authorInitials but 
> > keep the prompt alive for new request. Hmm...
> +1. I understand the need to get 5.3 out soon. I didn't realize all the 
> side effects of this change.
> 
> Regards .. Subbu


tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
The best packed information most resembles random noise.