godot-fmod - Godot with FMOD integration

Age	Commit message (Collapse)	Author
2021-07-30	doc: Use self-closing tags for `return` and `argument`	Rémi Verschelde
	For the time being we don't support writing a description for those, preferring having all details in the method's description. Using self-closing tags saves half the lines, and prevents contributors from thinking that they should write the argument or return documentation there.
2021-07-20	Add get_buffered_amount() to WebRTCDataChannel	David Snopek

2020-01-31	Update docs to version 4.0	clayjohn

2020-01-26	doc: Drop unused 'category' property from header	Rémi Verschelde
	We already removed it from the online docs with #35132. Currently it can only be "Built-In Types" (Variant types) or "Core" (everything else), which is of limited use. We might also want to consider dropping it from `ClassDB` altogether in Godot 4.0.
2019-06-30	doc: Add default values to all properties	Rémi Verschelde
	Thanks to @bojidar-bg's impressive work in #29380.
2019-06-27	doc: Fix scoped hyperlinks to same-class enums/methods	Rémi Verschelde
	The class name does not need to be specified when it is the current class.
2019-06-15	doc: Fix formatting, typos and some descriptions in new docstrings	Rémi Verschelde

2019-06-14	Add documentation for WebRTC classes.	Fabio Alessandrelli

2019-05-16	WebRTC refactor. Data channels, STUN/TURN support.	Fabio Alessandrelli
	A big refactor to the WebRTC module. API is now considered quite stable. Highlights: - Renamed `WebRTCPeer` to `WebRTCPeerConnection`. - `WebRTCPeerConnection` no longer act as `PacketPeer`, it only handle the connection itself (a bit like `TCP_Server`) - Added new `WebRTCDataChannel` class which inherits from `PacketPeer` to handle data transfer. - Add `WebRTCPeerConnection.initialize` method to create a new connection with the desired configuration provided as dictionary ([see MDN docs](https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/RTCPeerConnection#RTCConfiguration_dictionary)). - Add `WebRTCPeerConnection.create_data_channel` method to create a data channel for the given connection. The connection must be in `STATE_NEW` as specified by the standard ([see MDN docs for options](https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/createDataChannel#RTCDataChannelInit_dictionary)). - Add a `data_channel_received` signal to `WebRTCPeerConnection` for in-band (not negotiated) channels. - Renamed `WebRTCPeerConnection` `offer_created` signal to `session_description_created`. - Renamed `WebRTCPeerConnection` `new_ice_candidate` signal to `ice_candidate_created`