slint/internal/compiler/tests/syntax/focus/focus_not_called.slint
Simon Hausmann 6fefe75a1c Don't require components that use forward-focus to be inlined
Achieve this by generating a `focus()` function for such components
and call it from the outside.

This replaces the previous focus handling with what should be cleaner:

- Any `forward-focus: some-element;` is basically syntactic sugar for
 `public function focus() { some-element.focus(); }`.
- The init code gets simplified to calling focus() on the root, if it's
  available.

Since the `focus()` functions are now generated in the imports pass,
they become visible in the style checker. That means the checker
requires consistent focus handling between the styles.
2024-01-26 12:16:09 +01:00

42 lines
1.1 KiB
Text

// Copyright © SixtyFPS GmbH <info@slint.dev>
// SPDX-License-Identifier: GPL-3.0-only OR LicenseRef-Slint-Royalty-free-1.1 OR LicenseRef-Slint-commercial
component BadOne {
function focus() {
// ^error{Cannot override 'focus'}
}
TextInput {
function focus() {
// ^error{Cannot override 'focus'}
}
}
}
component SecondBadOne {
forward-focus: ti;
function focus() {
// ^error{Cannot override 'focus'}
}
ti := TextInput {}
}
export X := Rectangle {
edit := TextInput { }
TouchArea {
clicked => {
(edit.focus)();
// ^error{'edit.focus' must be called. Did you forgot the '\(\)'\?}
edit.focus;
// ^error{'edit.focus' must be called. Did you forgot the '\(\)'\?}
}
}
x: edit.focus;
// ^error{Cannot convert function\(element ref\) -> void to length}
// ^^error{'edit.focus' must be called. Did you forgot the '\(\)'\?}
// ^^^warning{Call of impure function}
BadOne {}
SecondBadOne {}
}