- Jun 24, 2024
-
-
Add a standalone documentation page on doxygen to reference how to create new crates for the core Rust bindings and new modules in Rust. The documentation is written on the latest changes made to merge the implementation and might not be 100% matching with what's currently been merged.
-
- Jun 23, 2024
-
-
-
-
-
Label by default should show the tool tip itself.
-
Although in Qt messages dialog level "2" corresponds to debug level, in a general aspect "3" corresponds to debug. Since we are using a non-Qt parameter "verbose" here to probe the level, we should treat the levels as according to the `vlc_log_type` enumeration.
-
-
-
-
-
-
-
-
?? returns left side if left side is empty string
-
-
Signed-off-by:Claudio Cambra <developer@claudiocambra.com>
-
macosx: React to ab loop change notifications rather than querying player controller every draw iteration in VLCPlaybackProgressSliderCell Signed-off-by: -
Signed-off-by: -
Since it is only used for this purpose, rename more accurately Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
macosx: Reorder VLCSliderCell to match other classes with C-style callbacks into libvlc (e.g. VLCLibraryModel) Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
Signed-off-by:
-
- Jun 22, 2024
-
-
-
An asynchronous timing report would fail/assert after a stream_Reset(). This issue was hidden since, most of the time, vlc_aout_stream_Flush() is called before vlc_aout_stream_Delete() but there are some rare case where vlc_aout_stream_Delete() is called without a flush.
-
Tests are sufficiently integrated into the automake test suite, and only a few features are missing: - Handling skipping and xfailing for rust tests. - Reporting tests by category (lib, doctest, etc) and being able to disable a category, there's currently not enough test to justify this right now. - Handling the incremental building of tests, which currently seems to be triggered everytime.
-
TEST_EXTENSIONS might be setup from different makefiles included, so it must be defined first.
-
Cargo can output the test results as JSON when running with unstable options. This script provides an automake test driver[^1] to run the tests and gather the results in the automake test suite. [^1]: https://www.gnu.org/software/automake/manual/html_node/Overview-of-Custom-Test-Drivers-Support.html
-
Since we'll be using edition = "2021", and we have a virtual workspace[^1], we need to specify the manifest resolver[^2]. Otherwise, cargo emits the following warning: warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"` note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions See release note[^3] for details on how this resolver changes the way features are selected for packages inside the workspace. [^1]: https://doc.rust-lang.org/cargo/reference/workspaces.html#virtual-workspace [^2]: https://doc.rust-lang.org/edition-guide/rust-2021/default-cargo-resolver.html [^3]: https://blog.rust-lang.org/2021/03/25/Rust-1.51.0.html#cargos-new-feature-resolver -
-
Signed-off-by: -
-
-
-
-
Otherwise we can not achieve graceful failure.
-
