API blocking UI thread about spotifyapi-net HOT 8 CLOSED

I'm just trying to reproduce this, but sadly I can't.
The window is moving fine while music is playing, no stuttering at all @JimmyAppelt

from spotifyapi-net.

My god @JohnnyCrazy ... i just tested all apps en they are indeed running fine. I'm a lazy computer restarter (might had something to do with that 👎 )

My apologies for bringing this issue up.

If in any case i see any kind of behavior back ... i'l triple check !

from spotifyapi-net.

No Problem!

Although you are correct, with SynchronizingObject set to the form, it will run in the UI-Thread. But since only one small request is made to localhost, it should be running in about 1-10ms which is no problem for the UI. Maybe I will change this someday. Closing #45 then :)

from spotifyapi-net.

After all i wasn't drunk 😄

It appears on my machine if i'm running the example app or my own app for a longer period of time.

The thing is that it interferes with other features in my own app, that will have a small time out before these update and the UI will not go smoothly ether.

As for the time being i compiled the a .dll with async and await for my app use as current solution.

Could you tell why you designed the project with everything as event updates ?

from spotifyapi-net.

I ran the example for about 30 minutes but sadly couldn't reproduce window lags or similar. Which system are you running it on?

I maybe have one idea, will push it to another branch and maybe you could test it out

@JimmyAppelt

from spotifyapi-net.

This is about a year old, I suspect its no longer an issue now. /tsk

from spotifyapi-net.

Generally, if SynchronizingObject is set, the tick event will be run on that UI Thread. If you don't want this, you can remove it and invoke on the ui thread in every event. This will execute the http request in a separate thread.

Reopen if you still have issues

from spotifyapi-net.

Windows 10 64-bit

I needed to create another way to capture information from the local player itself.

Because of this issue and issue #51 :)

@stuntguy3000 such issue's don't magically disappear ;)

@JohnnyCrazy i would be happy to test it out, the only problem i have is issue #51 still

from spotifyapi-net.