Closed GoogleCodeExporter closed 9 years ago
This will not going to happen in this way.
EMM provide the user with wide veriety of updaters.
Auto updaters are always needed.
What might happen is, that you will have the ability to mark the selected
movies at
once, than you can run the marked movies updater on them.
Original comment by nadas.bence@gmail.com
on 25 Jun 2009 at 4:58
Yes, however, you're missing the point.
The standard for windows development is to set all filters separately as an
explicit
and overt transaction, then the "process" step is a polymorphic action
enumerating
those selected.
Before you disregard, you should consider taking a vote among new users / doing
usability testing. It's not only a more standardized approach, it allows the
user
to see what is being processed before hand.
Many programs similar to Ember have gone through this same change/upgrade,
including
the most downloaded tagging app out there: Tag&Rename.
Original comment by rus...@gmail.com
on 25 Jun 2009 at 5:48
There are already visual cues for new movies, marked movies, movies missing
items,
etc. You already know which movies will be processed for new movies (the green
ones)
or marked movies (the red ones) or missing items (don't have check boxes). So
I'm not
quite understanding the point of having another step of selecting these movies
first,
then running the updater.
Original comment by jason.schnitzler
on 25 Jun 2009 at 6:15
Mark as verified to close the issue.
Original comment by nadas.bence@gmail.com
on 26 Jun 2009 at 7:39
Original issue reported on code.google.com by
rus...@gmail.com
on 25 Jun 2009 at 4:00