Back to Top

Some minor UI annoyances

14 posts / 0 new
Last post
astruyk
Offline
Last seen: 11 years 11 months ago
Joined: 12/12/2008 - 08:43
Some minor UI annoyances

First off, I love the program - great work.

I have a few minor things that have been bothering me for a while, and I finally decided to write them down:

1. 'Search' text-entry box doesn't start search when you press 'enter'. When I'm looking for a podcast, and I goto the search page - after entering a bunch of search terms I press enter, expecting that the search will begin. Instead it enters a new line in the text box.

2. 'Auto Download quantity' box on 'Podcast Edit' page should really be a spinner. It'd be nice not to have to use the keyboard to increase/decrease the number here. Typing into the box is annoying because I have to open my keyboard every time. Instead, there should be '+' and '-' buttons beside the box, so that I can just tap to increase/decrease the number. Also, this text entry box has the same 'enter adds newline' problem as the search textbox.

3. I can't start/stop playback with my headphone controls. I have the T-Mobile G1, and it comes with a set of headphones with a button on them. When using the default android media player to listen to podcasts, I can press the button to pause/unpause the currently playing audio file. This does not work in the embedded player in your program. I rely heavily on this feature, and not having it keeps me from using your embedded player.

eric
Offline
Last seen: 9 months 2 weeks ago
Joined: 11/06/2008 - 22:02
UI

Search text box - I agree, this also happened to me a couple times. Added it to future features.

Auto download - Agreed, added to list

Start/stop - This is already on the future feature list, but I'm glad you mentioned it because each person that mentions it gives us a feel for how important it is.

jasherai
Offline
Last seen: 11 years 11 months ago
Joined: 02/12/2009 - 04:15
Second the start/stop functionality

as requested, to increase priority for this feature I'd like to second the request for start/stop functionality.

eric
Offline
Last seen: 9 months 2 weeks ago
Joined: 11/06/2008 - 22:02
I'm starting to get the feeling....

I'm starting to get the feeling that this is important :-)

mcamou
Offline
Last seen: 5 years 2 months ago
Joined: 01/20/2009 - 17:12
Yes!

Start/stop, please!

eric
Offline
Last seen: 9 months 2 weeks ago
Joined: 11/06/2008 - 22:02
This is how it would work

I did some digging in the developer newsgroups on this and the way it currently works is that one application at a time can be registered to respond to the media button (headset button). So it's possible for me to do this but it would mean that DC would block the android media player from responding to the button. I could make this configurable, so you could turn on/off DC's responding to the button.

Is it useful to have DC respond to the button if it blocks the android player from responding to the button?

mcamou
Offline
Last seen: 5 years 2 months ago
Joined: 01/20/2009 - 17:12
Useful at least to me!

I don't use the Android Media Player nearly as much as I use DC so I wouldn't mind at all. Even if it's only when DC is in the foreground (whether the phone is locked or not) it would be very useful, or even grab it when you are playing (for pause and relinquish it when you're paused and not in the foreground. Something like that.

Alan
Offline
Last seen: 11 years 10 months ago
Joined: 02/06/2009 - 18:27
Hey yeah

Can you determine if DC is what was used to launch the media and only grab the input from the stop button if that's the case?

Or maybe start grabbing the input from the stop button when the play button is pressed on-screen from within DC and give it up when the pause button is pressed on-screen to allow the built-in media player to have it?

eric
Offline
Last seen: 9 months 2 weeks ago
Joined: 11/06/2008 - 22:02
The way it was described in the forums

...is that one application that is installed will receive the broadcast that the button was pressed. So it's not something that you can do some conditional logic while the application is running. It was admitted by one of the google guys that the current solution ~ 'doesn't scale', and something to the effect 'we'll address it in a future release'.

I haven't given up on this, I'll keep a close eye in the forums to see if anyone comes up with any creative solutions and let you know.

mcamou
Offline
Last seen: 5 years 2 months ago
Joined: 01/20/2009 - 17:12
Forwarding the intent?

A strange idea popped up in my mind. How about detecting whether you're interested in the event, and forwarding it if not? I.e., if nothing is currently playing in DC, forward the event to the media player via an intent.

eric
Offline
Last seen: 9 months 2 weeks ago
Joined: 11/06/2008 - 22:02
This is in progress

This turned out to be pretty simple. I've got it working on my phone, just need to make it configurable and get it through beta testing.

Thanks for keeping the pressure on :-)

ianwelles
Offline
Last seen: 11 years 1 month ago
Joined: 11/11/2009 - 15:10
Any suggestions on how to best handle this today?

I have a Droid and when I use the play/pause button on my bluetooth headset both DoggCatcher and the Android Media player stop and start. I can't seem to get it to control just DoggCatcher. What's the best way to make this happen?

ianwelles
Offline
Last seen: 11 years 1 month ago
Joined: 11/11/2009 - 15:10
Hmmm... I guess since the

Hmmm... I guess since the last update the behavior is changed. Now my headphone button controls only DoggCatcher. Since I mainly listen to podcasts this is mostly fine. But what happens when I am listening to the Android Media player?

eric
Offline
Last seen: 9 months 2 weeks ago
Joined: 11/06/2008 - 22:02
Button sharing

Basically you have to make a choice which application you would like bind to the headset button. If you enable the preference in DC, then it will own the button. When it's disabled, DC will ignore the button.

At the moment, with Android, there isn't any way to elegantly have applications share the button.

I did update the user guide to reflect this.

http://www.snoggdoggler.com/node/277