Unfortunately it proves that way you have chosen doesn't match best practices for creating UI.
Besides, it makes impossible to execute backup once again with the same or slightly changed backup settings (what I
alreadyprooved).
Also I didn't ask form hide anything. I'm asking to leave it without changes. Instead of changing meanin of backup
button,just pop up some modal requester with the information. 2 birds with one rock.
MK
23. 2. 2013 v 19:33, "Guillaume Lelarge" <guillaume@lelarge.info>:
> On Tue, 2013-01-22 at 16:55 +0100, Michal Kozusznik wrote:
>> Hello
>> I have idea about one more improvement to be queued.
>> After executing backup, Backup button turns into Done one (curious the
>> Cancel button remains, can't imagine the reason since it has the same
>> function than Done one).
>>
>
> The reason is that we don't hide widgets. We could disable it of
> course... but you won't be able to use Escape to close the window.
>
>> I suggest to leave the Backup button untouched making possible to
>> execute another backup.
>> It might be useful in case of dumping schema and data separately or just
>> performing backups of single objects with the same settings.
>
> We changed the Backup button to a Done button, so that people know the
> backup was done and won't run another one IIRC.
>
>
> --
> Guillaume
> http://blog.guillaume.lelarge.info
> http://www.dalibo.com
>
