Author Topic: Stop after current event  (Read 7504 times)

Pako

  • Full Member
  • ***
  • Posts: 132
I have one feature request, related to MusicBee API.
It would be good if there was an event, that would be triggered,
when the "stop after current" its status changes.
Now it is necessary to use polling, if I want to have corresponding icon on button on the remote control.
The event would have been much better.

Thanks, Pako

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34313
i will look to do this towards the end of the 2.3 development, so maybe late february (thats a guess!)

Pako

  • Full Member
  • ***
  • Posts: 132
i will look to do this towards the end of the 2.3 development ...
I thank you very much for accommodating approach.

so maybe late february (thats a guess!)
It does not matter. Now it works well with polling, but I look forward to I'll be able to turn it off.  :)

Pako

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34313
this is in the next v2.3 update
api revision: 36
notification type enum:
StopAfterCurrentChanged = 28

Pako

  • Full Member
  • ***
  • Posts: 132

Pako

  • Full Member
  • ***
  • Posts: 132
I noticed, that the event StopAfterCurrentChanged does not work as I expected.
This is how it looks in reality:

I think that in the end there should also be the event StopAfterCurrentChanged,
because at the moment of stopping (at the end of the song) the state of StopAfterCurrent is changed.
MusicBee version: 2.4.5203.

Thanks, Pako
Last Edit: April 03, 2014, 03:05:13 PM by Pako

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34313
i have changed the ordering in the last update

Pako

  • Full Member
  • ***
  • Posts: 132
i have changed the ordering in the last update
I am a little confused.
There are two options.
1) I wrote it incomprehensible and it was not well understood
2) I did not understand correctly answer (I understand it, that in the current beta version already, it should work in a new way)

So I will try to explain it again in other words:
1) MusicBee played a song
2) The user (in any way) sets the flag Stop after current
3) MusicBee triggers event StopAfterCurrentChanged
4) The song ends
5) The flag Stop after current is automatically reset
6) MusicBee not triggers event StopAfterCurrentChanged. I think it is not correct.

However, it is of course possible to dispense without it ...

Pako