| From Martyn Shaw <martynshaw99@...>
| Fri, 30 Oct 2009 23:54:53 +0000
| Subject: [Audacity-devel] enable/disable Save menu--how?
> No problem, I see the arguments, having skimmed this thread. Clearly
> low priority.
>
> It would appear from this thread that enabling 'save' and an entry on
> the history list are synonymous. Maybe that's what we need to address
> for some cases, post release. A 'feature request' to enable 'save' if
> state is changed (other than things that go on the history list).
Ed voted +1 too, I note. I'm not sure if some may find even this idea
annoying, particularly those who habitually save the project every
few steps to "be on the safe side".
If I save my project just before exit, scroll and zoom around a bit just
to check it over, then exit, do I want to see the "Save changes?" dialogue
again? There are already some users who think we shouldn't ask that
question at all if the project contents has been exported, so be aware
that dialogue does have an annoyance factor.
That's why I asked if there was some other solution such as a separate .ini
file in the Audacity data folder that stored these values for each project
on exit. I'm not suggesting that's a great idea (I don't know how it would
delete entries for projects that no longer existed), but was positing
the question. Users do want state information saved, but I think they
are looking for something more subtle than being forced to resave if
they change state.
If there really is no other way than storing in the .aup file, yes I'd
vote for this too (it could go on our tracker as a "developer supported"
enhancement), but I'd be thinking this might need a preference?
Gale
> Vaughan Johnson wrote:
> > Sorry, Martyn, but I disagree. As I explained, we decided explicitly not
> > to save all changes (before even you joined the project, venerable
> > colleague!), like moving windows, etc. I really don't think Save
> > enabling should be dependent on window position. To save position in the
> > project file is reasonable, but then they can get out of sync if you
> > moved the window after finishing anything that sets. Gale, do you think
> > users would find that a big bug? Overall, I consider the idea low priority.
> >
> > - V
> >
> >
> > Martyn Shaw wrote:
> >> Hi Ed
> >>
> >> I see what you are up to (I think); enabling save so that any change
> >> to 'state' can be made, and using this as an example? Presumably that
> >> will include moving the window? Not a bad thing but I think we should
> >> debate if we want it in 2.0, given time constraints.
> >>
> >> I'm not seeing many P2s left on
> >> http://wiki.audacityteam.org/index.php?title=Release_Checklist and
> >> wouldn't want to see anything delay 2.0 release.
> >>
> >> TTFN
> >> Martyn
> >>
> >> Ed Musgrove wrote:
> >>> I am trying examine an extremely trivial bug (or possibly a feature
> >>> request
> >>> <grin>). I need to know how to enable the File/Save menu item for a
> >>> project.
> >>>
> >>> --Ed
> >>> PS if inquiring minds want to know this is what I'm working on (but
> >>> if/when I bring it to the list I will create a new subject:
> >>>
> >>> Changes in project state (i.e. zoom level), though stored in the save
> >>> file,
> >>> do not "un-gray"/enable the File/Save menu item.
> >>>
> >>> This bug is at best a P5 -- more like a P9 (a real bug but it
> >>> probably only
> >>> affects the reporter, the reporter is a developer, the fix is trivial
> >>> and
> >>> has no apparent side effects <grin>).
> >>>
> >>> Currently saved state data (of which I'm aware):
> >>>
> >>> xmlFile.WriteAttr(wxT("sel0"), mViewInfo.sel0, 10);
> >>> xmlFile.WriteAttr(wxT("sel1"), mViewInfo.sel1, 10);
> >>> xmlFile.WriteAttr(wxT("vpos"), mViewInfo.vpos);
> >>> xmlFile.WriteAttr(wxT("h"), mViewInfo.h, 10);
> >>> xmlFile.WriteAttr(wxT("zoom"), mViewInfo.zoom, 10);
> >>> xmlFile.WriteAttr(wxT("rate"), mRate);
> >>>
> >>> Proposed solution:
> >>>
> >>> As a test case, add to all "On... Zoom" functions code which enables the
> >>> File/Save menu item.
> >>>
> >>> \audacity\src\Menus.cpp(4063):void AudacityProject::OnZoomIn()
> >>> \audacity\src\Menus.cpp(4128):void AudacityProject::OnZoomOut()
> >>> \audacity\src\Menus.cpp(4143):void AudacityProject::OnZoomToggle()
> >>> \audacity\src\Menus.cpp(4163):void AudacityProject::OnZoomNormal()
> >>> \audacity\src\Menus.cpp(4169):void AudacityProject::OnZoomFit()
> >>> \audacity\src\Menus.cpp(4221):void AudacityProject::OnZoomFitV()
> >>> \audacity\src\Menus.cpp(4230):void AudacityProject::OnZoomSel()
> >>>
> >>> Add something like this:
> >>> Project_menubar->Enable(wxID_SAVE,true);
> >>> before any return except the "do-nothing" returned (if it is there)
> >>>
> >>>
> >>>
> >>> ------------------------------------------------------------------------------
> >>>
> >>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> >>> is the only developer event you need to attend this year. Jumpstart your
> >>> developing skills, take BlackBerry mobile applications to market and
> >>> stay ahead of the curve. Join us from November 9 - 12, 2009. Register
> >>> now!
> >>> http://p.sf.net/sfu/devconference
> >>> _______________________________________________
> >>> audacity-devel mailing list
> >>> audacity-devel@...
> >>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >>>
> >>
> >> ------------------------------------------------------------------------------
> >>
> >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> >> is the only developer event you need to attend this year. Jumpstart your
> >> developing skills, take BlackBerry mobile applications to market and
> >> stay ahead of the curve. Join us from November 9 - 12, 2009. Register
> >> now!
> >> http://p.sf.net/sfu/devconference
> >> _______________________________________________
> >> audacity-devel mailing list
> >> audacity-devel@...
> >> https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >>
> >
> >
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> audacity-devel mailing list
> audacity-devel@...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
|
