mudlet-makers team mailing list archive

[Ramiel <leigh.stillard@xxxxxxxxx>]

Ahh ok, gotcha.

I'm reporting bugs from win32 at the moment, I don't use ubuntu much these
days.

On Mon, Dec 7, 2009 at 11:57 PM, Heiko <koehnheiko@xxxxxxxxxxxxxx>
wrote:

> Ramiel, Vadi is referring to connection dialog->profile history where
> old profile snapshots can be loaded - default is latest. Everytime you
> click on the button "save profile" (not talking about export profile
> here - the former button called save_as), a new snapshot will be saved.
> All snapshots can be found in profile/current
>
>
> Vadim Peretokin schrieb:
>  > Click save Profile, close/crash mudlet, when opening, you should see
> the
> > time and date of the time when you saved profile there.
> >
> >
>
> --
> Hard crashes of mudlet result in lost data, if 'Save profile' has not been
> clicked
> https://bugs.launchpad.net/bugs/493404
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Mudlet the MUD client: New
>
> Bug description:
> If you cause a hard crash of mudlet, you will lose all your data if you
> haven't clicked 'save profile' since your last change.
>
> While clicking 'save profile' is a workaround for this, it is unintuitive,
> especially if you're doing a lot of work on a large script.
>
> I would suggest an autosave feature be put in, saving changes to disk after
> each save function is performed. For those who like things as it is, perhaps
> the autosave feature could be disabled with a settings checkbox..
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/mudlet/+bug/493404/+subscribe
>

-- 
Hard crashes of mudlet result in lost data, if 'Save profile' has not been clicked
https://bugs.launchpad.net/bugs/493404
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.

Status in Mudlet the MUD client: New

Bug description:
If you cause a hard crash of mudlet, you will lose all your data if you haven't clicked 'save profile' since your last change.

While clicking 'save profile' is a workaround for this, it is unintuitive, especially if you're doing a lot of work on a large script. 

I would suggest an autosave feature be put in, saving changes to disk after each save function is performed. For those who like things as it is, perhaps the autosave feature could be disabled with a settings checkbox..