This is not supported right now, the other elements will not be part of
the layout, and two `for` will be in the same listview, creating bad
situation with the scrollbar.
This is a warning since it would be a breaking change to make it an
error.
For example, we used a FocusScope in the StandardListView implementation so
I had to go trough one level of indirection
CC: #860
After checking if the instance field is null, we await the promise that
would guarantee DOM attachment. While we await, the browser processes
other microtasks, and we might end up in render() again. This time the
instance field is also null, but the ensure_attached_to_dom promise is
already resolved, so we would create the first slint component and the
associated window. Later we would return from the first await. At this
point the instance field is already set, so we should re-use the
existing window, but since we're not checking anymore, we'll go ahead
and create a second window on the same canvas element.
Fixes#1926
This patch has no effect on the currently generated output (apart from a
dummy few lines in out/extension.js), but may help to avoid issues in
the future like we had last week, where esbuild processed an import from
"vscode-languageclient" and due to browser mode it picked the browser
version of the languageclient for out/extension.js that's running in the
node environment.
The previous code did not remove two ways binding that were between two
globals. Now we do the remove_aliases pass over the whole document at
once which allos to simplify aliases between globals.
By using a persistent WebGL context for reach (small) preview, we hit
the browser imposed limits on the number of GL contexts quickly. This
change add support to pt out of the automatic enabling of the preview
via no-auto-preview, that's selected for recipes.
- re-order the ChangedSection by "impact"
- Add missing periods.
- For the element highlight, explain when a highlight is shown.
- Elaborate on some entries.
Do not interact with the language server directly in vscode, but use
vscode.commands.executeCommand(...) instead. The online_editor will of
course need to continue to interact with the language server directy, so
this unshares a bit of code. It is not too much and straight forward
code, so that is not too bad.
* Tools: trigger updates for properties view more often
So far you had to move the cursor to refresh the properties view after
start-up. This is no longer necessary.
When doing builds that require image embedding (such as for WASM), it's crucial
to also visit the globals (after they've been collected) to catch all image references.
We need to continue propagating the release event to other element (eg
other flickable)
Fix the flickable flicking even though the mouse is released if there are
several Flickable in the component.
Put the shared code into an NPM package. This makes especially vscode
much happier as it does not need to build code outside its project root
anymore:-)
