Closed GoogleCodeExporter closed 9 years ago
Why? maybe someone wants to change the status of the rules even while omnidroid
is disabled
Original comment by eligeler...@gmail.com
on 13 Jul 2010 at 10:39
Otherwise it gives the impression that those rules are enabled. I guess as an
alternative we could provide some visible indication on the SavedRules screen
as to whether omnidroid is enabled or not.
I think users may disable omnidroid and forget that it's not running. They
realize that omnidroid isn't processing any rules and think it's broken since
we show a list of enabled rules and yet none are being caught.
Original comment by case.and...@gmail.com
on 13 Jul 2010 at 10:53
also i might have set of rules that I have enable, and i want to shut down
omnidroid, and then start again, i wouldn't want to go through all saved rules
and enable the ones I want
Original comment by salomeju...@yahoo.com
on 13 Jul 2010 at 11:15
That's a good point. I think some indication on that screen will suffice to let
the user know that omnidroid is disabled.
Original comment by eligeler...@gmail.com
on 13 Jul 2010 at 11:16
definitely, when you do enable rule, we would want pop up warning that
omnidroid is disabled.
Original comment by sv767%ny...@gtempaccount.com
on 13 Jul 2010 at 11:20
We decided just to put a message on the main screen to let the user know that
omnidroid is disabled (otherwise would have to hard code on every page that it
is disabled)
Original comment by eligeler...@gmail.com
on 13 Jul 2010 at 11:29
Original comment by case.and...@gmail.com
on 16 Jul 2010 at 12:51
How do I edit a linear layout which was created in an xml file?
Original comment by eligeler...@gmail.com
on 18 Jul 2010 at 9:07
What do you mean by edit? Do you mean changing its properties during runtime?
If that's the case, you should be able to get the instance of that layout by
using findViewById().
Original comment by renc...@gmail.com
on 18 Jul 2010 at 9:45
I think this is done.
Original comment by case.and...@gmail.com
on 5 Aug 2010 at 10:39
Original issue reported on code.google.com by
case.and...@gmail.com
on 13 Jul 2010 at 10:30