Rest() makes RESTful calls after validating the tokens. _Access() uses the authorization code previously returned to get an access code, this code will be used every time the access token needs to be refreshed. The root request contains the authorization code, once this call is received the code is retrieved to be used by _Access(), the response for this is a JavaScript function to close the tab. The _Socket() method responds to each of the calls made to the web server, most of the calls give an HTTP 204 response. If needed, it calls the Auth() method that launches the authorization page and starts what can be considered a small web server to wait for the response sent by Spotify after clicking 'Allow' on the authorization page. The constructor ( _New()) reads the options and validates them, when finished the required tokens are properly at disposal. Here's a small explanation of what they do and the flow for them:

The other methods are there to be left as-is, given the fact that they contain the logic to keep the API calling as simple as possible. GuiControl NowPlaying_:, Static2, % pad spotifyPlaying Gui Add, Text, -Wrap w300 x5, % spotifyPlaying The following code is nowhere near ready to be taken seriously (it lacks an awful lot of validations and relies in super-globals), is here as a mere example of how to present data coming from the API: global spotifyPlaying := ''

Now, let's show what's currently playing. The authorization and token refresh are done automatically and it's not needed to manually call the methods, however, if for some reason a new access token is desired, is just a matter of call: spotify.Auth() ini is as previously detailed: global spotify := new Spotify_Status('options.ini') First, we create an instance, the structure of the.

Autohotkey spotify