-
Notifications
You must be signed in to change notification settings - Fork 304
Debug
Debugging tools are provided as the default demo build. Help is provided in the Help tab. The default tools allow you to profile and test out different configurations on the CommentCoreLibrary.
在默认的编译环境下，我们提供了一套简单的调试工具。默认的工具允许你简单的进行程序运行时间分析和测试各种不同的播放环境配置。这些工具的使用可以参考相应的帮助标签。
The debugging interface offers direct links to a subset of the provided sample tests. They are meant to cover most of the effects available for Comments with mode < 8.
测试界面包括了向一系列测试样例的链接。它们设计成了会涵盖几乎所有的复杂的对于mode<8的弹幕的效果。
These set up some runtime filters that can dynamically modify danmaku upon send. Of these one is the profiler. The profiler is implemented as a runtime filter, and since by design CCL only allows one runtime filter, setting another runtime filter will invalidate the profiler.
过滤器分三种，第一种会过滤掉弹幕，第二种会在弹幕发送前对其进行变化，第三个是在行进间操控弹幕。在Debugger里面你看到的过滤器章节是第三种过滤器（运行时过滤器）。其中有一个是 Profiler（性能向标），这个实际上是一个特殊的运行时过滤器。因为根据设计，运行时过滤器只能有一个，所以在进行性能评测时如果启动了另一个过滤器，性能评测將被覆盖而无法进行。
The profiler is not a strict profile of the framerate. Instead it is representing the load when updating the DOM tree.
性能评测器不是一个严肃的测试。尤其是其帧率部分，并不真正反应浏览器刷新页面的帧率。实际上，它是由修改DOM树的“工作耗时”计算而出的。
The code execution window will evaluate code within the demo's runtime. This will allow you to inspect objects without having to pull out the developer tools.
代码区可以允许你对测试的弹幕管理器进行直接的编程操作。当然，在console里面也可以去做这些操作，Code区域只是提供一个便利。
We have provided some tests in /tests/. While we strive for coverage, these tests are not guaranteed to fully cover every feature case provided. Also since there is more data for Bilibili, there are more tests for that format. Most of the tests are unmodified. When no license is given, please assume the author of the danmaku uses a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.‘
在给出样例测试的同时我们还提供了一套更广泛的测试。它位于/tests/ 文件夹中。虽然我们尽力让他们包括了所有能出现的复杂情况，但是实际上也不容易实现。所以这些测试也未必能完全测试还原度。大部分测试文件均直接抓自Bilibili或其余站点，有少数手工制作的测试。如果没有另外声明，请人为作者采取了CC BY-NC-ND 4.0许可协议。