The first FLV packet was getting thrown off by initialTimeStamp, because
I foolishly forgot that even if the function was called with 0 as the
argument for the timestamp, it would still subtract the -1 from that.
Also made the capitalization of timestamp to be consistent with other
variable in the file.
I'd rather have the cursor for the desktop texture to show properly than
show up garbled. I'd rather be spending my time in obs-studio right now
though. obs-studio will have a built-in way of dealing with
multi-texture based sources much better (rendering to texture)
Currently only handles the vanilla OBS case of two possible codecs, i.e.
it won't list multiple listed supported codecs as alternatives in the
warning message; also doesn't verify that the listed codecs are actually
available in OBS
Other than that it supports multiple "supported audio codec" entries
in services.xconfig per service, in case anyone wants to white list
both MP3 and AAC for their service:
```
recommended : {
"supported audio codec" : "MP3"
"supported audio codec" : "AAC"
}
```
This should allow plugins to implement their own version of a log window
without having to worry about providing lightweight-ish and non-blocking
callback functions for OBSApi.
@jp9000
Implement log window
Also made it so that the log window position/size is saved. Defaults to
600x500, centered to the main monitor if no configuration found.
@palana
Log system integration and callback behavior
Due to updatesAvailable being uninitialized there was a chance no error
message would be shown in case HTTPGetFile or ParseManifest returned
an error (the latter only when returning an error before setting
updatesAvailable) or the response code from HTTPGetFile was neither 200
nor 304
Currently an error is shown in case OK or Apply is clicked to preserve
the non-modifying behaviour of Cancel
TODO: add warnings somewhere to notify the user of problems before OK
or Apply is clicked
No new log files will be added to prevent the current log file from
becoming the topmost entry, which would render the "Upload last Log File"
entry useless
Also includes UI for opening specific log files directly from the OBS UI
On successful upload the resulting (non-API) URL is copied into the
clipboard and a message box signalling successful upload is displayed.
This should probably be expanded into a dialog with buttons to retry
copying the URL to the clipboard and maybe a text box with the URL
preselected.
Whether or not the upload URL should be cached (per log file) and reused
in case of duplicate upload (attempts) is still open for debate.
