Closed GoogleCodeExporter closed 8 years ago
I couldn't recreate this... 2.0.7 should already remember the show/hide states
for
each page and it should save the states to the document. Can you give me a
sample doc
and scenario that recreate this issue? Sorry for the trouble..
Original comment by soichih
on 27 Nov 2009 at 4:59
No worries. It's hard to articulate... let's see:
In a 3 page document ... let's say that by default they all have the budget
view
open.
If I go ahead and close the budget view in page one, the budget view will STILL
be
open on pages 2 and 3. And yes, when I return to page one, it closes again.
What I'm suggesting, is that when you close the budget view on one page, it
closes
the view on all pages.
It's really only an issue if you have a lot of pages (like I do ... I think my
document has about 25 pages) I constantly flip between pages ... so it would
seem
easier for the "close budget" option to kind of act as a permanent toggle ...
regardless of what page you're on.
Basically, I'm wondering if it'd be better if it didn't remember. Does this
make any
sense?
Original comment by rafikib...@gmail.com
on 27 Nov 2009 at 7:12
Ah, I see... it makes sense.
My thinking was that the toggler should behave like the balance graph toggler -
assuming that user will adjust the budget during the first part of the month
then
closes it (after everything settles) and user will simply add expenses for the
rest
of the month.. So I saw the pattern emerging for each pages when users would
want to
have a budget open, and when they want it to be closed.
Now, what you said makes total sense -- that if a user constantly switches back
and
forth between various pages, then having this toggle *sticks* across various
pages
should be more optimal.
To be honest, I can't think of a good way to compromise between these 2 modes..
I've
only implemented this feature because some users were having trouble by
accidentally
changing the budget amount by hitting the budget graph area while they were
scrolling
a page. This toggler was a kind of a hack to prevent that from happening.
Would it be okay to keep it as is until I see which use-cases are majority among
dsbudget users, and then switch it if necessary?
Original comment by soichih
on 27 Nov 2009 at 9:12
Oh sure, it can totally stay as is.
I see the value of the toggler being set for each page as well. And I can't
think of a
compromise either (not one that wouldn't be extremely confusing anyway).
Plus, I think my needs are a bit unique ... since I get the feeling that I'm
one of the
only people crazy enough to make budget plans 6 months in advance.
Original comment by rafikib...@gmail.com
on 27 Nov 2009 at 9:23
Original comment by soichih
on 27 Nov 2009 at 11:26
Original issue reported on code.google.com by
rafikib...@gmail.com
on 27 Nov 2009 at 4:09