REFERENCE
Documents
641 entries · Page 1 of 5
"Hot reload didn't pick up my change"A section in the C++ SDK staging document extensions: "Hot reload didn't pick up my change". Documentation must be checked against the delivered package for each release.
0. 先读这个A section in the C++ SDK staging document known_issues: Read this first. Documentation must be checked against the delivered package for each release.
1. HTML Parse -> DOMA section in the C++ SDK staging document architecture: 1. HTML Parse -> DOM. Documentation must be checked against the delivered package for each release.
1. OverviewA section in the C++ SDK staging document components: 1. Overview. Documentation must be checked against the delivered package for each release.
1. OverviewA section in the C++ SDK staging document extensions: 1. Overview. Documentation must be checked against the delivered package for each release.
1. OverviewA section in the C++ SDK staging document kui-editor: 1. Overview. Documentation must be checked against the delivered package for each release.
1. OverviewA section in the C++ SDK staging document lua: 1. Overview. Documentation must be checked against the delivered package for each release.
1. OverviewA section in the C++ SDK staging document virtual_list: 1. Overview. Documentation must be checked against the delivered package for each release.
1. `kui-preload`:提前备好还没打开的界面A section in the C++ SDK staging document performance: 1. kui-preload prepares interfaces before they open. Documentation must be checked against the delivered package for each release.
1. 一句话结论A section in the C++ SDK staging document positioning_and_benchmark: 1. Conclusion. Documentation must be checked against the delivered package for each release.
1. 为什么需要它A section in the C++ SDK staging document extension_repaint_contract: 1. Why it is needed. Documentation must be checked against the delivered package for each release.
1. 先澄清一个术语:`repaintAreaPercent` 不是 CDP 字段A section in the C++ SDK staging document devtools_perf_fields: 1. repaintAreaPercent is not a CDP field. Documentation must be checked against the delivered package for each release.
1. 创建工程A section in the C++ SDK staging document getting-started: 1. Create a project. Documentation must be checked against the delivered package for each release.
1. 编号族怎么读A section in the C++ SDK staging document known_issues: 1. How to read issue ID families. Documentation must be checked against the delivered package for each release.
1.1 What is KUI's Lua engine?A section in the C++ SDK staging document lua: 1.1 What is KUI's Lua engine?. Documentation must be checked against the delivered package for each release.
1.1 What is a "virtual component"?A section in the C++ SDK staging document components: 1.1 What is a "virtual component"?. Documentation must be checked against the delivered package for each release.
1.1 What is a KUI Extension?A section in the C++ SDK staging document extensions: 1.1 What is a KUI Extension?. Documentation must be checked against the delivered package for each release.
1.1 What it providesA section in the C++ SDK staging document kui-editor: 1.1 What it provides. Documentation must be checked against the delivered package for each release.
1.1 What you getA section in the C++ SDK staging document virtual_list: 1.1 What you get. Documentation must be checked against the delivered package for each release.
1.2 DistributionA section in the C++ SDK staging document kui-editor: 1.2 Distribution. Documentation must be checked against the delivered package for each release.
1.2 Three sources of virtual componentsA section in the C++ SDK staging document components: 1.2 Three sources of virtual components. Documentation must be checked against the delivered package for each release.
1.2 Three ways to create a custom elementA section in the C++ SDK staging document extensions: 1.2 Three ways to create a custom element. Documentation must be checked against the delivered package for each release.
1.2 What can Lua do in KUI?A section in the C++ SDK staging document lua: 1.2 What can Lua do in KUI?. Documentation must be checked against the delivered package for each release.
1.2 When to reach for themA section in the C++ SDK staging document virtual_list: 1.2 When to reach for them. Documentation must be checked against the delivered package for each release.
1.3 Capabilities matrixA section in the C++ SDK staging document extensions: 1.3 Capabilities matrix. Documentation must be checked against the delivered package for each release.
1.3 Capabilities matrixA section in the C++ SDK staging document kui-editor: 1.3 Capabilities matrix. Documentation must be checked against the delivered package for each release.
1.3 What they are NOTA section in the C++ SDK staging document virtual_list: 1.3 What they are NOT. Documentation must be checked against the delivered package for each release.
1.3 What virtual components can doA section in the C++ SDK staging document components: 1.3 What virtual components can do. Documentation must be checked against the delivered package for each release.
1.3 Why Lua and not JavaScript?A section in the C++ SDK staging document lua: 1.3 Why Lua and not JavaScript?. Documentation must be checked against the delivered package for each release.
1.4 LimitsA section in the C++ SDK staging document extensions: 1.4 Limits. Documentation must be checked against the delivered package for each release.
1.4 What virtual components are NOTA section in the C++ SDK staging document components: 1.4 What virtual components are NOT. Documentation must be checked against the delivered package for each release.
10. Data Binding & Reactive StateA section in the C++ SDK staging document lua: 10. Data Binding & Reactive State. Documentation must be checked against the delivered package for each release.
10. FAQA section in the C++ SDK staging document virtual_list: 10. FAQ. Documentation must be checked against the delivered package for each release.
10. Lua API: Clipboard & UndoA section in the C++ SDK staging document kui-editor: 10. Lua API: Clipboard & Undo. Documentation must be checked against the delivered package for each release.
10. Observed AttributesA section in the C++ SDK staging document components: 10. Observed Attributes. Documentation must be checked against the delivered package for each release.
10. Performance Monitoring & SEH GuardA section in the C++ SDK staging document extensions: 10. Performance Monitoring & SEH Guard. Documentation must be checked against the delivered package for each release.
10.1 ClipboardA section in the C++ SDK staging document kui-editor: 10.1 Clipboard. Documentation must be checked against the delivered package for each release.
10.1 Reactive state objectsA section in the C++ SDK staging document lua: 10.1 Reactive state objects. Documentation must be checked against the delivered package for each release.
10.1 SEH guard (Windows)A section in the C++ SDK staging document extensions: 10.1 SEH guard (Windows). Documentation must be checked against the delivered package for each release.
10.1 Why filter?A section in the C++ SDK staging document components: 10.1 Why filter?. Documentation must be checked against the delivered package for each release.
10.2 Binding to the DOMA section in the C++ SDK staging document lua: 10.2 Binding to the DOM. Documentation must be checked against the delivered package for each release.
10.2 Performance statsA section in the C++ SDK staging document extensions: 10.2 Performance stats. Documentation must be checked against the delivered package for each release.
10.2 Runtime mutationA section in the C++ SDK staging document components: 10.2 Runtime mutation. Documentation must be checked against the delivered package for each release.
10.2 Undo / RedoA section in the C++ SDK staging document kui-editor: 10.2 Undo / Redo. Documentation must be checked against the delivered package for each release.
10.3 Computed propertiesA section in the C++ SDK staging document lua: 10.3 Computed properties. Documentation must be checked against the delivered package for each release.
10.3 Resource limitsA section in the C++ SDK staging document extensions: 10.3 Resource limits. Documentation must be checked against the delivered package for each release.
11. Authoring in C++A section in the C++ SDK staging document components: 11. Authoring in C++. Documentation must be checked against the delivered package for each release.
11. Bundled ExtensionsA section in the C++ SDK staging document extensions: 11. Bundled Extensions. Documentation must be checked against the delivered package for each release.
11. Lua API: Movement & DeletionA section in the C++ SDK staging document kui-editor: 11. Lua API: Movement & Deletion. Documentation must be checked against the delivered package for each release.
11. See AlsoA section in the C++ SDK staging document virtual_list: 11. See Also. Documentation must be checked against the delivered package for each release.
11. `<script>` Tag ExecutionA section in the C++ SDK staging document lua: 11. `<script>` Tag Execution. Documentation must be checked against the delivered package for each release.
11.1 How `<script>` tags are runA section in the C++ SDK staging document lua: 11.1 How `<script>` tags are run. Documentation must be checked against the delivered package for each release.
11.1 MovementA section in the C++ SDK staging document kui-editor: 11.1 Movement. Documentation must be checked against the delivered package for each release.
11.1 Per-element stateA section in the C++ SDK staging document components: 11.1 Per-element state. Documentation must be checked against the delivered package for each release.
11.1 `kui_ext_editor` - Code editor (`<kui-editor>`)A section in the C++ SDK staging document extensions: 11.1 `kui_ext_editor` - Code editor (`<kui-editor>`). Documentation must be checked against the delivered package for each release.
11.2 DeletionA section in the C++ SDK staging document kui-editor: 11.2 Deletion. Documentation must be checked against the delivered package for each release.
11.2 Where to registerA section in the C++ SDK staging document components: 11.2 Where to register. Documentation must be checked against the delivered package for each release.
11.2 `kui_ext_pdf` - PDF viewer (`<kui-pdf>`)A section in the C++ SDK staging document extensions: 11.2 `kui_ext_pdf` - PDF viewer (`<kui-pdf>`). Documentation must be checked against the delivered package for each release.
11.2 `type` attribute filteringA section in the C++ SDK staging document lua: 11.2 `type` attribute filtering. Documentation must be checked against the delivered package for each release.
11.3 External scripts (`src`)A section in the C++ SDK staging document lua: 11.3 External scripts (`src`). Documentation must be checked against the delivered package for each release.
11.3 ViewportA section in the C++ SDK staging document kui-editor: 11.3 Viewport. Documentation must be checked against the delivered package for each release.
11.3 `kui_ext_hello` - Minimal example (`<kui-hello>`)A section in the C++ SDK staging document extensions: 11.3 `kui_ext_hello` - Minimal example (`<kui-hello>`). Documentation must be checked against the delivered package for each release.
11.4 `DOMContentLoaded`A section in the C++ SDK staging document lua: 11.4 `DOMContentLoaded`. Documentation must be checked against the delivered package for each release.
11.4 `kui_3d_render` - Filament 3D engine (`<kui-3d-view>`)A section in the C++ SDK staging document extensions: 11.4 `kui_3d_render` - Filament 3D engine (`<kui-3d-view>`). Documentation must be checked against the delivered package for each release.
11.5 Hot-loading scripts at runtimeA section in the C++ SDK staging document lua: 11.5 Hot-loading scripts at runtime. Documentation must be checked against the delivered package for each release.
11.5 Media pluginsA section in the C++ SDK staging document extensions: 11.5 Media plugins. Documentation must be checked against the delivered package for each release.
11.6 Loading bundled extensionsA section in the C++ SDK staging document extensions: 11.6 Loading bundled extensions. Documentation must be checked against the delivered package for each release.
12. Authoring GuideA section in the C++ SDK staging document extensions: 12. Authoring Guide. Documentation must be checked against the delivered package for each release.
12. Authoring in LuaA section in the C++ SDK staging document components: 12. Authoring in Lua. Documentation must be checked against the delivered package for each release.
12. C++ <-> Lua InteropA section in the C++ SDK staging document lua: 12. C++ <-> Lua Interop. Documentation must be checked against the delivered package for each release.
12. Lua API: Theme, Font, LanguageA section in the C++ SDK staging document kui-editor: 12. Lua API: Theme, Font, Language. Documentation must be checked against the delivered package for each release.
12.1 Adding methodsA section in the C++ SDK staging document components: 12.1 Adding methods. Documentation must be checked against the delivered package for each release.
12.1 Calling Lua from C++A section in the C++ SDK staging document lua: 12.1 Calling Lua from C++. Documentation must be checked against the delivered package for each release.
12.1 Project layoutA section in the C++ SDK staging document extensions: 12.1 Project layout. Documentation must be checked against the delivered package for each release.
12.2 CMakeLists.txt templateA section in the C++ SDK staging document extensions: 12.2 CMakeLists.txt template. Documentation must be checked against the delivered package for each release.
12.2 Calling C++ from LuaA section in the C++ SDK staging document lua: 12.2 Calling C++ from Lua. Documentation must be checked against the delivered package for each release.
12.2 Custom paint in LuaA section in the C++ SDK staging document components: 12.2 Custom paint in Lua. Documentation must be checked against the delivered package for each release.
12.3 Per-element state patternA section in the C++ SDK staging document extensions: 12.3 Per-element state pattern. Documentation must be checked against the delivered package for each release.
12.3 `setGlobal` / `getGlobal`A section in the C++ SDK staging document lua: 12.3 `setGlobal` / `getGlobal`. Documentation must be checked against the delivered package for each release.
12.4 Background thread patternA section in the C++ SDK staging document extensions: 12.4 Background thread pattern. Documentation must be checked against the delivered package for each release.
12.4 `print` redirectionA section in the C++ SDK staging document lua: 12.4 `print` redirection. Documentation must be checked against the delivered package for each release.
12.5 Distributing your extensionA section in the C++ SDK staging document extensions: 12.5 Distributing your extension. Documentation must be checked against the delivered package for each release.
12.5 InteropBridge (high-performance bidirectional calls)A section in the C++ SDK staging document lua: 12.5 InteropBridge (high-performance bidirectional calls). Documentation must be checked against the delivered package for each release.
12.6 Native functions that change what is paintedA section in the C++ SDK staging document lua: 12.6 Native functions that change what is painted. Documentation must be checked against the delivered package for each release.
13. Authoring as a DLL ExtensionA section in the C++ SDK staging document components: 13. Authoring as a DLL Extension. Documentation must be checked against the delivered package for each release.
13. Find / Replace / RegexA section in the C++ SDK staging document kui-editor: 13. Find / Replace / Regex. Documentation must be checked against the delivered package for each release.
13. Sandbox & SafetyA section in the C++ SDK staging document lua: 13. Sandbox & Safety. Documentation must be checked against the delivered package for each release.
13. TroubleshootingA section in the C++ SDK staging document extensions: 13. Troubleshooting. Documentation must be checked against the delivered package for each release.
13.1 Disabled stdlib modulesA section in the C++ SDK staging document lua: 13.1 Disabled stdlib modules. Documentation must be checked against the delivered package for each release.
13.1 Option flags (bitmask)A section in the C++ SDK staging document kui-editor: 13.1 Option flags (bitmask). Documentation must be checked against the delivered package for each release.
13.2 Memory capA section in the C++ SDK staging document lua: 13.2 Memory cap. Documentation must be checked against the delivered package for each release.
13.2 Search methodsA section in the C++ SDK staging document kui-editor: 13.2 Search methods. Documentation must be checked against the delivered package for each release.
13.3 Instruction-count capA section in the C++ SDK staging document lua: 13.3 Instruction-count cap. Documentation must be checked against the delivered package for each release.
13.3 Replace methodsA section in the C++ SDK staging document kui-editor: 13.3 Replace methods. Documentation must be checked against the delivered package for each release.
13.4 PCRE2 dialectA section in the C++ SDK staging document kui-editor: 13.4 PCRE2 dialect. Documentation must be checked against the delivered package for each release.
13.4 Sandboxed `pcall`A section in the C++ SDK staging document lua: 13.4 Sandboxed `pcall`. Documentation must be checked against the delivered package for each release.
14. Component Source ComparisonA section in the C++ SDK staging document components: 14. Component Source Comparison. Documentation must be checked against the delivered package for each release.
14. DevTools Debugger IntegrationA section in the C++ SDK staging document lua: 14. DevTools Debugger Integration. Documentation must be checked against the delivered package for each release.
14. FAQA section in the C++ SDK staging document extensions: 14. FAQ. Documentation must be checked against the delivered package for each release.
14. Multi-Cursor & Column SelectionA section in the C++ SDK staging document kui-editor: 14. Multi-Cursor & Column Selection. Documentation must be checked against the delivered package for each release.
14.1 Decision treeA section in the C++ SDK staging document components: 14.1 Decision tree. Documentation must be checked against the delivered package for each release.
14.1 Multi-cursor methodsA section in the C++ SDK staging document kui-editor: 14.1 Multi-cursor methods. Documentation must be checked against the delivered package for each release.
14.2 Column / block selection methodsA section in the C++ SDK staging document kui-editor: 14.2 Column / block selection methods. Documentation must be checked against the delivered package for each release.
14.3 Line-aware paste with multi-cursorA section in the C++ SDK staging document kui-editor: 14.3 Line-aware paste with multi-cursor. Documentation must be checked against the delivered package for each release.
14.4 Typing affordancesA section in the C++ SDK staging document kui-editor: 14.4 Typing affordances. Documentation must be checked against the delivered package for each release.
15. Best PracticesA section in the C++ SDK staging document components: 15. Best Practices. Documentation must be checked against the delivered package for each release.
15. Code FoldingA section in the C++ SDK staging document kui-editor: 15. Code Folding. Documentation must be checked against the delivered package for each release.
15. Examples ReferenceA section in the C++ SDK staging document lua: 15. Examples Reference. Documentation must be checked against the delivered package for each release.
15. See AlsoA section in the C++ SDK staging document extensions: 15. See Also. Documentation must be checked against the delivered package for each release.
15.1 Default styles in `connectedCallback`, not in HTMLA section in the C++ SDK staging document components: 15.1 Default styles in `connectedCallback`, not in HTML. Documentation must be checked against the delivered package for each release.
15.1 Folding behaviorA section in the C++ SDK staging document kui-editor: 15.1 Folding behavior. Documentation must be checked against the delivered package for each release.
15.2 Use `data-*` attributes for stateA section in the C++ SDK staging document components: 15.2 Use `data-*` attributes for state. Documentation must be checked against the delivered package for each release.
15.3 Prefix your tag namesA section in the C++ SDK staging document components: 15.3 Prefix your tag names. Documentation must be checked against the delivered package for each release.
15.4 Always pair tick with `needsTickCallback`A section in the C++ SDK staging document components: 15.4 Always pair tick with `needsTickCallback`. Documentation must be checked against the delivered package for each release.
15.5 Don't allocate in hot pathsA section in the C++ SDK staging document components: 15.5 Don't allocate in hot paths. Documentation must be checked against the delivered package for each release.
15.6 Mind thread safetyA section in the C++ SDK staging document components: 15.6 Mind thread safety. Documentation must be checked against the delivered package for each release.
15.7 Document your componentA section in the C++ SDK staging document components: 15.7 Document your component. Documentation must be checked against the delivered package for each release.
15.8 Test the lifecycleA section in the C++ SDK staging document components: 15.8 Test the lifecycle. Documentation must be checked against the delivered package for each release.
15.9 Keep paint deterministicA section in the C++ SDK staging document components: 15.9 Keep paint deterministic. Documentation must be checked against the delivered package for each release.
16. Find / Replace WidgetA section in the C++ SDK staging document kui-editor: 16. Find / Replace Widget. Documentation must be checked against the delivered package for each release.
16. TroubleshootingA section in the C++ SDK staging document components: 16. Troubleshooting. Documentation must be checked against the delivered package for each release.
16. TroubleshootingA section in the C++ SDK staging document lua: 16. Troubleshooting. Documentation must be checked against the delivered package for each release.
16.1 LifecycleA section in the C++ SDK staging document kui-editor: 16.1 Lifecycle. Documentation must be checked against the delivered package for each release.
16.1 `attempt to index a nil value (global 'document')`A section in the C++ SDK staging document lua: 16.1 `attempt to index a nil value (global 'document')`. Documentation must be checked against the delivered package for each release.
16.2 Input routingA section in the C++ SDK staging document kui-editor: 16.2 Input routing. Documentation must be checked against the delivered package for each release.
16.2 `attempt to call a nil value (method 'on')`A section in the C++ SDK staging document lua: 16.2 `attempt to call a nil value (method 'on')`. Documentation must be checked against the delivered package for each release.
16.3 Field stateA section in the C++ SDK staging document kui-editor: 16.3 Field state. Documentation must be checked against the delivered package for each release.
16.3 My event listener doesn't fireA section in the C++ SDK staging document lua: 16.3 My event listener doesn't fire. Documentation must be checked against the delivered package for each release.
16.4 `instruction limit exceeded`A section in the C++ SDK staging document lua: 16.4 `instruction limit exceeded`. Documentation must be checked against the delivered package for each release.
16.5 Out of memoryA section in the C++ SDK staging document lua: 16.5 Out of memory. Documentation must be checked against the delivered package for each release.
16.6 DevTools Console says "scripting unavailable"A section in the C++ SDK staging document lua: 16.6 DevTools Console says "scripting unavailable". Documentation must be checked against the delivered package for each release.
16.7 `print` output doesn't show in DevTools ConsoleA section in the C++ SDK staging document lua: 16.7 `print` output doesn't show in DevTools Console. Documentation must be checked against the delivered package for each release.
16.8 "Cannot upgrade element" for a custom elementA section in the C++ SDK staging document lua: 16.8 "Cannot upgrade element" for a custom element. Documentation must be checked against the delivered package for each release.
16.9 Memory grows with each event dispatchA section in the C++ SDK staging document lua: 16.9 Memory grows with each event dispatch. Documentation must be checked against the delivered package for each release.
17. FAQA section in the C++ SDK staging document lua: 17. FAQ. Documentation must be checked against the delivered package for each release.
17. MinimapA section in the C++ SDK staging document kui-editor: 17. Minimap. Documentation must be checked against the delivered package for each release.
17. See AlsoA section in the C++ SDK staging document components: 17. See Also. Documentation must be checked against the delivered package for each release.
17.1 Programmatic scrolling (KUI-033)A section in the C++ SDK staging document kui-editor: 17.1 Programmatic scrolling (KUI-033). Documentation must be checked against the delivered package for each release.
17.2 Scrollbar styles (KUI-034)A section in the C++ SDK staging document kui-editor: 17.2 Scrollbar styles (KUI-034). Documentation must be checked against the delivered package for each release.
18. LSP IntegrationA section in the C++ SDK staging document kui-editor: 18. LSP Integration. Documentation must be checked against the delivered package for each release.
18. See AlsoA section in the C++ SDK staging document lua: 18. See Also. Documentation must be checked against the delivered package for each release.
18.1 LifecycleA section in the C++ SDK staging document kui-editor: 18.1 Lifecycle. Documentation must be checked against the delivered package for each release.
18.2 Document syncA section in the C++ SDK staging document kui-editor: 18.2 Document sync. Documentation must be checked against the delivered package for each release.
18.3 Auto-attach (recommended)A section in the C++ SDK staging document kui-editor: 18.3 Auto-attach (recommended). Documentation must be checked against the delivered package for each release.
18.4 DiagnosticsA section in the C++ SDK staging document kui-editor: 18.4 Diagnostics. Documentation must be checked against the delivered package for each release.
18.5 Feature requests (polling API)A section in the C++ SDK staging document kui-editor: 18.5 Feature requests (polling API). Documentation must be checked against the delivered package for each release.
18.6 Poll APIA section in the C++ SDK staging document kui-editor: 18.6 Poll API. Documentation must be checked against the delivered package for each release.
18.7 Generic pass-through (`lspRequest`)A section in the C++ SDK staging document kui-editor: 18.7 Generic pass-through (`lspRequest`). Documentation must be checked against the delivered package for each release.
19. Git Diff Gutter & BlameA section in the C++ SDK staging document kui-editor: 19. Git Diff Gutter & Blame. Documentation must be checked against the delivered package for each release.
19.1 Git diff gutter (M3-01)A section in the C++ SDK staging document kui-editor: 19.1 Git diff gutter (M3-01). Documentation must be checked against the delivered package for each release.