qiurui
/
qtdeclarative
mirror of https://github.com/qt/qtdeclarative.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
qtdeclarative/examples/quickcontrols/texteditor/qml/texteditor.qml

560 lines
16 KiB
QML
Raw Normal View History

Use SPDX license identifiers Replace the current license disclaimer in files by a SPDX-License-Identifier. Files that have to be modified by hand are modified. License files are organized under LICENSES directory. Pick-to: 6.4 Task-number: QTBUG-67283 Change-Id: I63563bbeb6f60f89d2c99660400dca7fab78a294 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
2022-05-13 13:12:05 +00:00
// Copyright (C) 2021 The Qt Company Ltd.
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR BSD-3-Clause
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
import QtCore
Improve QML in Controls TextEditor example Pick-to: 6.8 Task-number: QTBUG-119988 Change-Id: Iffc7df85f25024301efef591eb3fbfb1cfbe2f17 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io> (cherry picked from commit 9cd4e29afd680972d7531ec4bfff12661b71c81f) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
2023-12-13 18:11:57 +00:00
import QtQuick
Remove all version numbers from QML imports As of Qt 6, the latest version will be used by default. This saves us a lot of effort in terms of version bumps. Task-number: QTBUG-82922 Change-Id: I74eba8185ec3ccc75bc293d4b2ea87d59e2d9928 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
2020-03-26 16:01:51 +00:00
import QtQuick.Controls
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
import QtQuick.Dialogs
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
// TODO:
// - make designer-friendly
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
ApplicationWindow {
id: window
width: 1024
height: 600
visible: true
Add load/save functionality to QQuickTextDocument (Tech Preview) Since QTBUG-92155 is not done, we need an easy way to load and save text into and out of a QTextDocument in QML. This patch follows the pattern from Image and other types: add a `source` property, a URL from which the file is to be loaded. When it comes to saving, the pattern is not set: so far the only file writing that has been available from QML is ItemGrabResult.saveToFile(). Since we need to save in specific formats, it makes sense to continue that pattern: the text document knows how to do its own serialization, so this is not suitable for generic data file I/O, even if we did have a QML API for that. We add invokable functions save() and saveAs() for the usual use cases in word processors and such. The URL extension determines the file format. Setting QQuickTextDocument's source is not allowed if the document has unsaved changes. The user (app author) needs to call save() or override modified to false first. [ChangeLog][QtQuick][TextEdit] TextEdit.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. Change-Id: I687318523c7a520e02244e47224d067da55318b5 Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-06 14:14:06 +00:00
title: textArea.textDocument.source +
" - Text Editor Example" + (textArea.textDocument.modified ? " *" : "")
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
Action {
id: openAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("&Open")
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
shortcut: StandardKey.Open
Add load/save functionality to QQuickTextDocument (Tech Preview) Since QTBUG-92155 is not done, we need an easy way to load and save text into and out of a QTextDocument in QML. This patch follows the pattern from Image and other types: add a `source` property, a URL from which the file is to be loaded. When it comes to saving, the pattern is not set: so far the only file writing that has been available from QML is ItemGrabResult.saveToFile(). Since we need to save in specific formats, it makes sense to continue that pattern: the text document knows how to do its own serialization, so this is not suitable for generic data file I/O, even if we did have a QML API for that. We add invokable functions save() and saveAs() for the usual use cases in word processors and such. The URL extension determines the file format. Setting QQuickTextDocument's source is not allowed if the document has unsaved changes. The user (app author) needs to call save() or override modified to false first. [ChangeLog][QtQuick][TextEdit] TextEdit.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. Change-Id: I687318523c7a520e02244e47224d067da55318b5 Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-06 14:14:06 +00:00
onTriggered: {
if (textArea.textDocument.modified)
discardDialog.open()
else
openDialog.open()
}
}
Action {
id: saveAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("&Save…")
Add load/save functionality to QQuickTextDocument (Tech Preview) Since QTBUG-92155 is not done, we need an easy way to load and save text into and out of a QTextDocument in QML. This patch follows the pattern from Image and other types: add a `source` property, a URL from which the file is to be loaded. When it comes to saving, the pattern is not set: so far the only file writing that has been available from QML is ItemGrabResult.saveToFile(). Since we need to save in specific formats, it makes sense to continue that pattern: the text document knows how to do its own serialization, so this is not suitable for generic data file I/O, even if we did have a QML API for that. We add invokable functions save() and saveAs() for the usual use cases in word processors and such. The URL extension determines the file format. Setting QQuickTextDocument's source is not allowed if the document has unsaved changes. The user (app author) needs to call save() or override modified to false first. [ChangeLog][QtQuick][TextEdit] TextEdit.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. Change-Id: I687318523c7a520e02244e47224d067da55318b5 Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-06 14:14:06 +00:00
shortcut: StandardKey.Save
Get rid of DocumentHandler in the Text Editor example ...and fix a couple of minor issues that remained. Fixes: QTBUG-81022 Change-Id: I5fc1547fb09caef5a9e24d95c2ca7b8d78ee104a Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-22 20:45:46 +00:00
enabled: textArea.textDocument.modified
Add load/save functionality to QQuickTextDocument (Tech Preview) Since QTBUG-92155 is not done, we need an easy way to load and save text into and out of a QTextDocument in QML. This patch follows the pattern from Image and other types: add a `source` property, a URL from which the file is to be loaded. When it comes to saving, the pattern is not set: so far the only file writing that has been available from QML is ItemGrabResult.saveToFile(). Since we need to save in specific formats, it makes sense to continue that pattern: the text document knows how to do its own serialization, so this is not suitable for generic data file I/O, even if we did have a QML API for that. We add invokable functions save() and saveAs() for the usual use cases in word processors and such. The URL extension determines the file format. Setting QQuickTextDocument's source is not allowed if the document has unsaved changes. The user (app author) needs to call save() or override modified to false first. [ChangeLog][QtQuick][TextEdit] TextEdit.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. Change-Id: I687318523c7a520e02244e47224d067da55318b5 Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-06 14:14:06 +00:00
onTriggered: textArea.textDocument.save()
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
Action {
id: saveAsAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("Save &As…")
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
shortcut: StandardKey.SaveAs
onTriggered: saveDialog.open()
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
Action {
id: quitAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("&Quit")
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
shortcut: StandardKey.Quit
onTriggered: close()
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
Action {
id: copyAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("&Copy")
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
shortcut: StandardKey.Copy
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
enabled: textArea.selectedText
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
onTriggered: textArea.copy()
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
Action {
id: cutAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("Cu&t")
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
shortcut: StandardKey.Cut
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
enabled: textArea.selectedText
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
onTriggered: textArea.cut()
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
Action {
id: pasteAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("&Paste")
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
shortcut: StandardKey.Paste
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
enabled: textArea.canPaste
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
onTriggered: textArea.paste()
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
Action {
id: boldAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("&Bold")
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
shortcut: StandardKey.Bold
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
checkable: true
checked: textArea.cursorSelection.font.bold
TextEditor example: allow setting multiple font attributes When a user activates the boldAction for example, the code was replacing QTextCharFormat's font with a default-constructed font that has the bold attribute set, which meant that it could not be bold, italic, underlined struck out, and with a custom size and color at the same time. On the other hand, when we do it the current way: textArea.cursorSelection.font.bold = checked we call QQuickTextSelection::font(), QFont::setBold(), and then QQuickTextSelection::setFont(). (QFont is a QML value type, so it's the only way.) Perhaps at some point, something was going wrong with that, but it seems to work now. Amends 045f9ce192d841f3cc36d514b5f238b46488b41e Fixes: QTBUG-136250 Pick-to: 6.8 Change-Id: I268e5814e7aa52aeb5aaec2d1a8fbfbc0d670236 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io> (cherry picked from commit 17a225f09ac5ec7ebd065197917ddd9586571ec1) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
2025-04-25 12:37:27 +00:00
onTriggered: textArea.cursorSelection.font.bold = checked
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
Action {
id: italicAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("&Italic")
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
shortcut: StandardKey.Italic
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
checkable: true
checked: textArea.cursorSelection.font.italic
TextEditor example: allow setting multiple font attributes When a user activates the boldAction for example, the code was replacing QTextCharFormat's font with a default-constructed font that has the bold attribute set, which meant that it could not be bold, italic, underlined struck out, and with a custom size and color at the same time. On the other hand, when we do it the current way: textArea.cursorSelection.font.bold = checked we call QQuickTextSelection::font(), QFont::setBold(), and then QQuickTextSelection::setFont(). (QFont is a QML value type, so it's the only way.) Perhaps at some point, something was going wrong with that, but it seems to work now. Amends 045f9ce192d841f3cc36d514b5f238b46488b41e Fixes: QTBUG-136250 Pick-to: 6.8 Change-Id: I268e5814e7aa52aeb5aaec2d1a8fbfbc0d670236 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io> (cherry picked from commit 17a225f09ac5ec7ebd065197917ddd9586571ec1) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
2025-04-25 12:37:27 +00:00
onTriggered: textArea.cursorSelection.font.italic = checked
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
Action {
id: underlineAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("&Underline")
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
shortcut: StandardKey.Underline
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
checkable: true
checked: textArea.cursorSelection.font.underline
TextEditor example: allow setting multiple font attributes When a user activates the boldAction for example, the code was replacing QTextCharFormat's font with a default-constructed font that has the bold attribute set, which meant that it could not be bold, italic, underlined struck out, and with a custom size and color at the same time. On the other hand, when we do it the current way: textArea.cursorSelection.font.bold = checked we call QQuickTextSelection::font(), QFont::setBold(), and then QQuickTextSelection::setFont(). (QFont is a QML value type, so it's the only way.) Perhaps at some point, something was going wrong with that, but it seems to work now. Amends 045f9ce192d841f3cc36d514b5f238b46488b41e Fixes: QTBUG-136250 Pick-to: 6.8 Change-Id: I268e5814e7aa52aeb5aaec2d1a8fbfbc0d670236 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io> (cherry picked from commit 17a225f09ac5ec7ebd065197917ddd9586571ec1) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
2025-04-25 12:37:27 +00:00
onTriggered: textArea.cursorSelection.font.underline = checked
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
}
Action {
id: strikeoutAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("&Strikeout")
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
checkable: true
checked: textArea.cursorSelection.font.strikeout
TextEditor example: allow setting multiple font attributes When a user activates the boldAction for example, the code was replacing QTextCharFormat's font with a default-constructed font that has the bold attribute set, which meant that it could not be bold, italic, underlined struck out, and with a custom size and color at the same time. On the other hand, when we do it the current way: textArea.cursorSelection.font.bold = checked we call QQuickTextSelection::font(), QFont::setBold(), and then QQuickTextSelection::setFont(). (QFont is a QML value type, so it's the only way.) Perhaps at some point, something was going wrong with that, but it seems to work now. Amends 045f9ce192d841f3cc36d514b5f238b46488b41e Fixes: QTBUG-136250 Pick-to: 6.8 Change-Id: I268e5814e7aa52aeb5aaec2d1a8fbfbc0d670236 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io> (cherry picked from commit 17a225f09ac5ec7ebd065197917ddd9586571ec1) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
2025-04-25 12:37:27 +00:00
onTriggered: textArea.cursorSelection.font.strikeout = checked
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
}
Action {
id: alignLeftAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("Align &Left")
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
shortcut: "Ctrl+{"
checkable: true
checked: textArea.cursorSelection.alignment === Qt.AlignLeft
onTriggered: textArea.cursorSelection.alignment = Qt.AlignLeft
}
Action {
id: alignCenterAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("&Center")
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
shortcut: "Ctrl+|"
checkable: true
checked: textArea.cursorSelection.alignment === Qt.AlignCenter
onTriggered: textArea.cursorSelection.alignment = Qt.AlignCenter
}
Action {
id: alignRightAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("Align &Right")
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
shortcut: "Ctrl+}"
checkable: true
checked: textArea.cursorSelection.alignment === Qt.AlignRight
onTriggered: textArea.cursorSelection.alignment = Qt.AlignRight
}
Action {
id: alignJustifyAction
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
text: qsTr("&Justify")
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
shortcut: "Ctrl+Alt+}"
checkable: true
checked: textArea.cursorSelection.alignment === Qt.AlignJustify
onTriggered: textArea.cursorSelection.alignment = Qt.AlignJustify
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
TextEditor example: add actions to built-in context menu, remove custom menu Since 3b598b6f7509f57e198e7de1f04e4333555e7227 TextArea comes with a built-in context menu. Here we demonstrate how to add extra menu items to the end. Task-number: QTBUG-35598 Task-number: QTBUG-134903 Change-Id: I1e3d8c044939521aaa076486630e3b879130dfd1 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io> (cherry picked from commit 64063946db1760ec33d5329148ee14a816e6db38) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
2025-03-19 18:55:46 +00:00
Action {
id: fontDialogAction
text: qsTr("Fon&t…")
shortcut: "Ctrl+T"
onTriggered: {
fontDialog.selectedFont = textArea.cursorSelection.font
fontDialog.open()
}
}
Action {
id: colorDialogAction
text: qsTr("Color…")
shortcut: "Ctrl+Shift+C"
onTriggered: {
colorDialog.selectedColor = textArea.cursorSelection.color
colorDialog.open()
}
}
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
menuBar: MenuBar {
Menu {
texteditor: add mnemonics Change-Id: Id11f2ab1ec9b11962e5ca3c5c5982709d9b2dac2 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-09-07 15:19:43 +00:00
title: qsTr("&File")
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: openAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: saveAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: saveAsAction
}
MenuItem {
action: quitAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
}
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
Menu {
texteditor: add mnemonics Change-Id: Id11f2ab1ec9b11962e5ca3c5c5982709d9b2dac2 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-09-07 15:19:43 +00:00
title: qsTr("&Edit")
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: copyAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: cutAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: pasteAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
}
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
Menu {
texteditor: add mnemonics Change-Id: Id11f2ab1ec9b11962e5ca3c5c5982709d9b2dac2 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-09-07 15:19:43 +00:00
title: qsTr("F&ormat")
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: boldAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: italicAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: underlineAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: strikeoutAction
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
}
TextEditor example: Add font and color dialog actions to Format menu Task-number: QTBUG-136251 Pick-to: 6.8 Change-Id: I64d7a406d4acff5395cfc18c201888c17a44e10f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io> (cherry picked from commit 5e8fba77156623d9de7b686d09aa35ff9e15e571) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
2025-04-25 18:03:10 +00:00
MenuItem {
action: fontDialogAction
}
MenuItem {
action: colorDialogAction
}
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuSeparator {}
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: alignLeftAction
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
}
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: alignCenterAction
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
}
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: alignJustifyAction
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
}
Controls TextEditor example: remove Qt.labs and the widget dependency This depends on the plan to have the Controls MenuBar and context Menu "go native" on platforms that support it. Task-number: QTBUG-119988 Task-number: QTBUG-106782 Change-Id: Ib8354b44bde385717431534d0260182715d66f16 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
2023-12-13 17:38:28 +00:00
MenuItem {
TextEditor example: use Actions in a DRY way; TapHandler I'm not sure why the example was written with so much repetition, but there must have been limitations back then. It's better to have Action as the encapsulation for an operation, and simply bind it to all the places where it's used (menubar, toolbar and context menu). It would be even better if an Action could be added directly to a Menu or ToolBar, but so far there's not a declarative way to do that (only by using addAction(), which is only in Menu, not ToolBar). We now use TapHandler instead of MouseArea to open the context menu. It works fine either way, but at least we don't need anchors.fill. Pick-to: 6.7 6.7.0 Change-Id: I74900ec49b57b616ffacddcf81c5aea12d4fefe6 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-11 22:59:46 +00:00
action: alignRightAction
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
}
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
}
FileDialog {
id: openDialog
fileMode: FileDialog.OpenFile
texteditor: fix selectedNameFilter usage texteditor.qml:165 Invalid property assignment: "selectedNameFilter" is a read-only property Change-Id: I691142ea0d3ed62a4041fb13916c251446ccea0d Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-10-04 11:48:45 +00:00
selectedNameFilter.index: 1
Support Markdown in the TextEditor example, including local paths The example still loads an HTML file from resources by default, but now it's possible to give either a relative or absolute file path on the command line to load an html, markdown or plain text file. Alternatively you can use the file dialog to load any of these types. We assume that any resources (such as images) with relative paths are to be loaded from the directory where the source text file is. Pick-to: 5.15 Change-Id: I37bc2d6aa2306016453770dc2fd66efa41a16618 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2020-08-10 10:35:25 +00:00
nameFilters: ["Text files (*.txt)", "HTML files (*.html *.htm)", "Markdown files (*.md *.markdown)"]
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
currentFolder: StandardPaths.writableLocation(StandardPaths.DocumentsLocation)
Add load/save functionality to QQuickTextDocument (Tech Preview) Since QTBUG-92155 is not done, we need an easy way to load and save text into and out of a QTextDocument in QML. This patch follows the pattern from Image and other types: add a `source` property, a URL from which the file is to be loaded. When it comes to saving, the pattern is not set: so far the only file writing that has been available from QML is ItemGrabResult.saveToFile(). Since we need to save in specific formats, it makes sense to continue that pattern: the text document knows how to do its own serialization, so this is not suitable for generic data file I/O, even if we did have a QML API for that. We add invokable functions save() and saveAs() for the usual use cases in word processors and such. The URL extension determines the file format. Setting QQuickTextDocument's source is not allowed if the document has unsaved changes. The user (app author) needs to call save() or override modified to false first. [ChangeLog][QtQuick][TextEdit] TextEdit.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. Change-Id: I687318523c7a520e02244e47224d067da55318b5 Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-06 14:14:06 +00:00
onAccepted: {
textArea.textDocument.modified = false // we asked earlier, if necessary
textArea.textDocument.source = selectedFile
}
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
FileDialog {
id: saveDialog
fileMode: FileDialog.SaveFile
nameFilters: openDialog.nameFilters
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
currentFolder: StandardPaths.writableLocation(StandardPaths.DocumentsLocation)
Add load/save functionality to QQuickTextDocument (Tech Preview) Since QTBUG-92155 is not done, we need an easy way to load and save text into and out of a QTextDocument in QML. This patch follows the pattern from Image and other types: add a `source` property, a URL from which the file is to be loaded. When it comes to saving, the pattern is not set: so far the only file writing that has been available from QML is ItemGrabResult.saveToFile(). Since we need to save in specific formats, it makes sense to continue that pattern: the text document knows how to do its own serialization, so this is not suitable for generic data file I/O, even if we did have a QML API for that. We add invokable functions save() and saveAs() for the usual use cases in word processors and such. The URL extension determines the file format. Setting QQuickTextDocument's source is not allowed if the document has unsaved changes. The user (app author) needs to call save() or override modified to false first. [ChangeLog][QtQuick][TextEdit] TextEdit.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. Change-Id: I687318523c7a520e02244e47224d067da55318b5 Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-06 14:14:06 +00:00
onAccepted: textArea.textDocument.saveAs(selectedFile)
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
FontDialog {
id: fontDialog
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
onAccepted: textArea.cursorSelection.font = selectedFont
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
TextEditor example: use the ColorDialog from qt quick dialogs In 6.4 we're introducing the ColorDialog in the qt quick dialogs module. This was the final dialog, that was missing from the module in previous versions of qt. This change will make use of the new dialog, instead of the qt labs platform version, which is using the widgets color dialog as a fallback. The eventual goal for this example should be to eliminate the need for the qt labs platform module entirely. Note that I am also making a small change to how the font dialog is being used, since we deprecated the currentFont property in the 6.3 release, but I forgot to update this example along with it. Pick-to: 6.4 Change-Id: Ib99ca7cbf110d3084ff96dfadfa1cd8c8af8815e Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2022-08-10 17:57:26 +00:00
ColorDialog {
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
id: colorDialog
Improve QML in Controls TextEditor example Pick-to: 6.8 Task-number: QTBUG-119988 Change-Id: Iffc7df85f25024301efef591eb3fbfb1cfbe2f17 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io> (cherry picked from commit 9cd4e29afd680972d7531ec4bfff12661b71c81f) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
2023-12-13 18:11:57 +00:00
selectedColor: textArea.cursorSelection.color
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
onAccepted: textArea.cursorSelection.color = selectedColor
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
Update the text editor to use the MessageDialog in qt quick dialogs Our goal is to eventually remove the dependency for the qt labs platform module. This patch will replace one of the labs platform MessageDialogs, with a MessageDialog from qt quick dialogs. All of the dialogs that are used in this example will eventually be from the qt quick dialogs module. Change-Id: I19f97948bf04d0fa5b265e057bbf49374bb51472 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2022-05-09 21:16:05 +00:00
MessageDialog {
title: qsTr("Error")
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
id: errorDialog
}
Update the text editor to use the MessageDialog in qt quick dialogs Our goal is to eventually remove the dependency for the qt labs platform module. This patch will replace one of the labs platform MessageDialogs, with a MessageDialog from qt quick dialogs. All of the dialogs that are used in this example will eventually be from the qt quick dialogs module. Change-Id: I19f97948bf04d0fa5b265e057bbf49374bb51472 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2022-05-09 21:16:05 +00:00
MessageDialog {
TextEditor: Add modified handling Add a modified property to the document and add handling in onClosing(). Connect the actions to call close() instead of Qt.quit() for it to become active. Change-Id: I0fec75629db64e91508ed8ba45d4fb60be146b1b Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2019-08-19 14:01:05 +00:00
id : quitDialog
title: qsTr("Quit?")
text: qsTr("The file has been modified. Quit anyway?")
Update the text editor to use the MessageDialog in qt quick dialogs Our goal is to eventually remove the dependency for the qt labs platform module. This patch will replace one of the labs platform MessageDialogs, with a MessageDialog from qt quick dialogs. All of the dialogs that are used in this example will eventually be from the qt quick dialogs module. Change-Id: I19f97948bf04d0fa5b265e057bbf49374bb51472 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2022-05-09 21:16:05 +00:00
buttons: MessageDialog.Yes | MessageDialog.No
Get rid of DocumentHandler in the Text Editor example ...and fix a couple of minor issues that remained. Fixes: QTBUG-81022 Change-Id: I5fc1547fb09caef5a9e24d95c2ca7b8d78ee104a Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-22 20:45:46 +00:00
onButtonClicked: function (button, role) {
if (role === MessageDialog.YesRole) {
textArea.textDocument.modified = false
Qt.quit()
}
}
TextEditor: Add modified handling Add a modified property to the document and add handling in onClosing(). Connect the actions to call close() instead of Qt.quit() for it to become active. Change-Id: I0fec75629db64e91508ed8ba45d4fb60be146b1b Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2019-08-19 14:01:05 +00:00
}
Add load/save functionality to QQuickTextDocument (Tech Preview) Since QTBUG-92155 is not done, we need an easy way to load and save text into and out of a QTextDocument in QML. This patch follows the pattern from Image and other types: add a `source` property, a URL from which the file is to be loaded. When it comes to saving, the pattern is not set: so far the only file writing that has been available from QML is ItemGrabResult.saveToFile(). Since we need to save in specific formats, it makes sense to continue that pattern: the text document knows how to do its own serialization, so this is not suitable for generic data file I/O, even if we did have a QML API for that. We add invokable functions save() and saveAs() for the usual use cases in word processors and such. The URL extension determines the file format. Setting QQuickTextDocument's source is not allowed if the document has unsaved changes. The user (app author) needs to call save() or override modified to false first. [ChangeLog][QtQuick][TextEdit] TextEdit.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. Change-Id: I687318523c7a520e02244e47224d067da55318b5 Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-06 14:14:06 +00:00
MessageDialog {
id : discardDialog
title: qsTr("Discard changes?")
text: qsTr("The file has been modified. Open a new file anyway?")
buttons: MessageDialog.Yes | MessageDialog.No
onButtonClicked: function (button, role) {
if (role === MessageDialog.YesRole)
openDialog.open()
}
}
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
header: ToolBar {
texteditor: use a wrapping Flow for the toolbar A proper toolbar extension would be better, but this is a workaround to make the window scalable/resizable until we have a better solution available. The font button was moved together with the other formatting buttons, because it looked a bit awkward when it was wrapping alone on the second row, and in general it caused things looking somehow mis-aligned when actions were wrapped on multiple rows. Change-Id: I0c1f432e81d5fde6aa763c13ea9efbb8af68ad50 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-08-12 08:45:17 +00:00
Flow {
width: parent.width
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
texteditor: use a wrapping Flow for the toolbar A proper toolbar extension would be better, but this is a workaround to make the window scalable/resizable until we have a better solution available. The font button was moved together with the other formatting buttons, because it looked a bit awkward when it was wrapping alone on the second row, and in general it caused things looking somehow mis-aligned when actions were wrapped on multiple rows. Change-Id: I0c1f432e81d5fde6aa763c13ea9efbb8af68ad50 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-08-12 08:45:17 +00:00
Row {
id: fileRow
ToolButton {
id: openButton
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
text: "\uF115" // icon-folder-open-empty
texteditor: use a wrapping Flow for the toolbar A proper toolbar extension would be better, but this is a workaround to make the window scalable/resizable until we have a better solution available. The font button was moved together with the other formatting buttons, because it looked a bit awkward when it was wrapping alone on the second row, and in general it caused things looking somehow mis-aligned when actions were wrapped on multiple rows. Change-Id: I0c1f432e81d5fde6aa763c13ea9efbb8af68ad50 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-08-12 08:45:17 +00:00
font.family: "fontello"
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
action: openAction
focusPolicy: Qt.TabFocus
texteditor: use a wrapping Flow for the toolbar A proper toolbar extension would be better, but this is a workaround to make the window scalable/resizable until we have a better solution available. The font button was moved together with the other formatting buttons, because it looked a bit awkward when it was wrapping alone on the second row, and in general it caused things looking somehow mis-aligned when actions were wrapped on multiple rows. Change-Id: I0c1f432e81d5fde6aa763c13ea9efbb8af68ad50 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-08-12 08:45:17 +00:00
}
Add load/save functionality to QQuickTextDocument (Tech Preview) Since QTBUG-92155 is not done, we need an easy way to load and save text into and out of a QTextDocument in QML. This patch follows the pattern from Image and other types: add a `source` property, a URL from which the file is to be loaded. When it comes to saving, the pattern is not set: so far the only file writing that has been available from QML is ItemGrabResult.saveToFile(). Since we need to save in specific formats, it makes sense to continue that pattern: the text document knows how to do its own serialization, so this is not suitable for generic data file I/O, even if we did have a QML API for that. We add invokable functions save() and saveAs() for the usual use cases in word processors and such. The URL extension determines the file format. Setting QQuickTextDocument's source is not allowed if the document has unsaved changes. The user (app author) needs to call save() or override modified to false first. [ChangeLog][QtQuick][TextEdit] TextEdit.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. Change-Id: I687318523c7a520e02244e47224d067da55318b5 Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-06 14:14:06 +00:00
ToolButton {
id: saveButton
text: "\uE80A" // icon-floppy-disk
font.family: "fontello"
action: saveAction
focusPolicy: Qt.TabFocus
}
texteditor: use a wrapping Flow for the toolbar A proper toolbar extension would be better, but this is a workaround to make the window scalable/resizable until we have a better solution available. The font button was moved together with the other formatting buttons, because it looked a bit awkward when it was wrapping alone on the second row, and in general it caused things looking somehow mis-aligned when actions were wrapped on multiple rows. Change-Id: I0c1f432e81d5fde6aa763c13ea9efbb8af68ad50 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-08-12 08:45:17 +00:00
ToolSeparator {
contentItem.visible: fileRow.y === editRow.y
}
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
Row {
texteditor: use a wrapping Flow for the toolbar A proper toolbar extension would be better, but this is a workaround to make the window scalable/resizable until we have a better solution available. The font button was moved together with the other formatting buttons, because it looked a bit awkward when it was wrapping alone on the second row, and in general it caused things looking somehow mis-aligned when actions were wrapped on multiple rows. Change-Id: I0c1f432e81d5fde6aa763c13ea9efbb8af68ad50 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-08-12 08:45:17 +00:00
id: editRow
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
ToolButton {
id: copyButton
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
text: "\uF0C5" // icon-docs
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
font.family: "fontello"
focusPolicy: Qt.TabFocus
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
action: copyAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
ToolButton {
id: cutButton
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
text: "\uE802" // icon-scissors
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
font.family: "fontello"
focusPolicy: Qt.TabFocus
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
action: cutAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
ToolButton {
id: pasteButton
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
text: "\uF0EA" // icon-paste
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
font.family: "fontello"
focusPolicy: Qt.TabFocus
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
action: pasteAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
texteditor: use a wrapping Flow for the toolbar A proper toolbar extension would be better, but this is a workaround to make the window scalable/resizable until we have a better solution available. The font button was moved together with the other formatting buttons, because it looked a bit awkward when it was wrapping alone on the second row, and in general it caused things looking somehow mis-aligned when actions were wrapped on multiple rows. Change-Id: I0c1f432e81d5fde6aa763c13ea9efbb8af68ad50 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-08-12 08:45:17 +00:00
ToolSeparator {
contentItem.visible: editRow.y === formatRow.y
}
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
Row {
texteditor: use a wrapping Flow for the toolbar A proper toolbar extension would be better, but this is a workaround to make the window scalable/resizable until we have a better solution available. The font button was moved together with the other formatting buttons, because it looked a bit awkward when it was wrapping alone on the second row, and in general it caused things looking somehow mis-aligned when actions were wrapped on multiple rows. Change-Id: I0c1f432e81d5fde6aa763c13ea9efbb8af68ad50 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-08-12 08:45:17 +00:00
id: formatRow
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
ToolButton {
id: boldButton
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
text: "\uE800" // icon-bold
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
font.family: "fontello"
focusPolicy: Qt.TabFocus
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
action: boldAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
ToolButton {
id: italicButton
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
text: "\uE801" // icon-italic
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
font.family: "fontello"
focusPolicy: Qt.TabFocus
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
action: italicAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
ToolButton {
id: underlineButton
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
text: "\uF0CD" // icon-underline
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
font.family: "fontello"
focusPolicy: Qt.TabFocus
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
action: underlineAction
}
ToolButton {
id: strikeoutButton
text: "\uF0CC"
font.family: "fontello"
focusPolicy: Qt.TabFocus
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
action: strikeoutAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
texteditor: use "brush" icon for text color and "A" for font "F" looks a bit silly. Even though most word processing applications seem to use the "A" icon with a bar underneath it for the text color, we want to use it to represent the button that opens the font dialog, since we don't use comboboxes for that. Change-Id: I3cc60ffbe388644cdcbd9e8ec0dcffbc041aa124 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-08-12 12:22:07 +00:00
ToolButton {
id: fontFamilyToolButton
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
text: qsTr("\uE808") // icon-font
texteditor: use "brush" icon for text color and "A" for font "F" looks a bit silly. Even though most word processing applications seem to use the "A" icon with a bar underneath it for the text color, we want to use it to represent the button that opens the font dialog, since we don't use comboboxes for that. Change-Id: I3cc60ffbe388644cdcbd9e8ec0dcffbc041aa124 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-08-12 12:22:07 +00:00
font.family: "fontello"
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
font.bold: textArea.cursorSelection.font.bold
font.italic: textArea.cursorSelection.font.italic
font.underline: textArea.cursorSelection.font.underline
font.strikeout: textArea.cursorSelection.font.strikeout
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
focusPolicy: Qt.TabFocus
TextEditor example: use the ColorDialog from qt quick dialogs In 6.4 we're introducing the ColorDialog in the qt quick dialogs module. This was the final dialog, that was missing from the module in previous versions of qt. This change will make use of the new dialog, instead of the qt labs platform version, which is using the widgets color dialog as a fallback. The eventual goal for this example should be to eliminate the need for the qt labs platform module entirely. Note that I am also making a small change to how the font dialog is being used, since we deprecated the currentFont property in the 6.3 release, but I forgot to update this example along with it. Pick-to: 6.4 Change-Id: Ib99ca7cbf110d3084ff96dfadfa1cd8c8af8815e Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2022-08-10 17:57:26 +00:00
onClicked: function () {
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
fontDialog.selectedFont = textArea.cursorSelection.font
TextEditor example: use the ColorDialog from qt quick dialogs In 6.4 we're introducing the ColorDialog in the qt quick dialogs module. This was the final dialog, that was missing from the module in previous versions of qt. This change will make use of the new dialog, instead of the qt labs platform version, which is using the widgets color dialog as a fallback. The eventual goal for this example should be to eliminate the need for the qt labs platform module entirely. Note that I am also making a small change to how the font dialog is being used, since we deprecated the currentFont property in the 6.3 release, but I forgot to update this example along with it. Pick-to: 6.4 Change-Id: Ib99ca7cbf110d3084ff96dfadfa1cd8c8af8815e Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2022-08-10 17:57:26 +00:00
fontDialog.open()
}
texteditor: use "brush" icon for text color and "A" for font "F" looks a bit silly. Even though most word processing applications seem to use the "A" icon with a bar underneath it for the text color, we want to use it to represent the button that opens the font dialog, since we don't use comboboxes for that. Change-Id: I3cc60ffbe388644cdcbd9e8ec0dcffbc041aa124 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-08-12 12:22:07 +00:00
}
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
ToolButton {
id: textColorButton
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
text: "\uF1FC" // icon-brush
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
font.family: "fontello"
focusPolicy: Qt.TabFocus
TextEditor example: use the ColorDialog from qt quick dialogs In 6.4 we're introducing the ColorDialog in the qt quick dialogs module. This was the final dialog, that was missing from the module in previous versions of qt. This change will make use of the new dialog, instead of the qt labs platform version, which is using the widgets color dialog as a fallback. The eventual goal for this example should be to eliminate the need for the qt labs platform module entirely. Note that I am also making a small change to how the font dialog is being used, since we deprecated the currentFont property in the 6.3 release, but I forgot to update this example along with it. Pick-to: 6.4 Change-Id: Ib99ca7cbf110d3084ff96dfadfa1cd8c8af8815e Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2022-08-10 17:57:26 +00:00
onClicked: function () {
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
colorDialog.selectedColor = textArea.cursorSelection.color
TextEditor example: use the ColorDialog from qt quick dialogs In 6.4 we're introducing the ColorDialog in the qt quick dialogs module. This was the final dialog, that was missing from the module in previous versions of qt. This change will make use of the new dialog, instead of the qt labs platform version, which is using the widgets color dialog as a fallback. The eventual goal for this example should be to eliminate the need for the qt labs platform module entirely. Note that I am also making a small change to how the font dialog is being used, since we deprecated the currentFont property in the 6.3 release, but I forgot to update this example along with it. Pick-to: 6.4 Change-Id: Ib99ca7cbf110d3084ff96dfadfa1cd8c8af8815e Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2022-08-10 17:57:26 +00:00
colorDialog.open()
}
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
Rectangle {
width: aFontMetrics.width + 3
height: 2
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
color: textArea.cursorSelection.color
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
parent: textColorButton.contentItem
anchors.horizontalCenter: parent.horizontalCenter
anchors.baseline: parent.baseline
texteditor: use "brush" icon for text color and "A" for font "F" looks a bit silly. Even though most word processing applications seem to use the "A" icon with a bar underneath it for the text color, we want to use it to represent the button that opens the font dialog, since we don't use comboboxes for that. Change-Id: I3cc60ffbe388644cdcbd9e8ec0dcffbc041aa124 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-08-12 12:22:07 +00:00
anchors.baselineOffset: 6
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
TextMetrics {
id: aFontMetrics
font: textColorButton.font
text: textColorButton.text
}
}
}
texteditor: use a wrapping Flow for the toolbar A proper toolbar extension would be better, but this is a workaround to make the window scalable/resizable until we have a better solution available. The font button was moved together with the other formatting buttons, because it looked a bit awkward when it was wrapping alone on the second row, and in general it caused things looking somehow mis-aligned when actions were wrapped on multiple rows. Change-Id: I0c1f432e81d5fde6aa763c13ea9efbb8af68ad50 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-08-12 08:45:17 +00:00
ToolSeparator {
contentItem.visible: formatRow.y === alignRow.y
}
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
Row {
texteditor: use a wrapping Flow for the toolbar A proper toolbar extension would be better, but this is a workaround to make the window scalable/resizable until we have a better solution available. The font button was moved together with the other formatting buttons, because it looked a bit awkward when it was wrapping alone on the second row, and in general it caused things looking somehow mis-aligned when actions were wrapped on multiple rows. Change-Id: I0c1f432e81d5fde6aa763c13ea9efbb8af68ad50 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2016-08-12 08:45:17 +00:00
id: alignRow
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
ToolButton {
id: alignLeftButton
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
text: "\uE803" // icon-align-left
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
font.family: "fontello"
focusPolicy: Qt.TabFocus
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
action: alignLeftAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
ToolButton {
id: alignCenterButton
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
text: "\uE804" // icon-align-center
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
font.family: "fontello"
focusPolicy: Qt.TabFocus
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
action: alignCenterAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
ToolButton {
id: alignRightButton
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
text: "\uE805" // icon-align-right
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
font.family: "fontello"
focusPolicy: Qt.TabFocus
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
action: alignRightAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
ToolButton {
id: alignJustifyButton
texteditor: add touch UI Task-number: QTBUG-54952 Change-Id: I14fe95608c4393b928edc80fc93ebaa843ce478f Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-26 12:15:31 +00:00
text: "\uE806" // icon-align-justify
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
font.family: "fontello"
focusPolicy: Qt.TabFocus
Add TextSelection (Tech Preview) In the Controls text editor example, DocumentHandler always sounded like a hack, just by its name. We don't expect to be able to handle multiple selections anytime soon; but if we realistically expect to have multi-seat support in Qt some day, then probably the multi-user experience should include support for multiple text cursors and selections. So we shouldn't paint ourselves into a corner. QQuickTextControl works with only one QTextCursor most of the time (but it's private, thus modifiable); and TextEdit has properties like selectionStart, selectionEnd, selectedText, etc. which seem to assume that there is only one selection. So probably if we needed to support multiple selections, we could add Q_PROPERTY(QQmlListProperty<QQuickTextSelection> selections ...), document that those legacy properties just work with the first selection, and/or deprecate them. So with that in mind, let's get started with a QQuickTextSelection object. We add TextEdit.cursorSelection which holds the single selection near the text cursor. It provides API needed for tracking and manipulating often-used properties of selected rich text (such as QTextCharFormat properties) so that DocumentHandler can be removed. The example now uses TextArea.cursorSelection to manipulate the selected text's format. It's not possible to be fully declarative with this API though; we need to call setFont (by assigning a font), but QFont is a value type, and is not as mergeable as QTextCharFormat is, for example. If we used a binding rather than Action.onTriggered, it would trigger reading the font for an entire span of selected text (which may have had multiple fonts), setting one attribute (like bold), then applying the font to the whole span. What we do now is almost like that; but instead of reading the font first, we start with a default-constructed QFont, set one attribute, and call QTextCursor::mergeCharFormat(), in the hope that it can merge only the features of QFont that have actually been set. Unfortunately this is not quite true either: if you toggle the bold button, it might change the font size too, and so on; so maybe we really need QTextCharFormat in QML (as a value type, presumably) to implement those feature-toggling toolbar buttons correctly. This API is in tech preview, because of such issues as described above; because we're just scratching the surface of what might be possible; because we should perhaps compare popular JavaScript text-editing APIs that might be found elsewhere, in the meantime get feedback from users during the tech preview phase, and keep iterating. [ChangeLog][QtQuick][TextEdit] TextEdit.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.cursorSelection is a TextSelection object, which provides properties to inspect and modify the formatting of the single selection that is currently supported. This API is in Tech Preview. Task-number: QTBUG-36521 Task-number: QTBUG-38830 Task-number: QTBUG-81022 Change-Id: Icea99f633694aa712d0b4730b77369077288540f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2023-11-03 03:10:40 +00:00
action: alignJustifyAction
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
}
}
}
Flickable {
id: flickable
flickableDirection: Flickable.VerticalFlick
anchors.fill: parent
doc: Update Controls Text Editor example docs We also move ScrollBar to make explanation easier. Pick-to: 6.7 6.7.0 Change-Id: If65de335f840382b5e236d8a04db382b0b7aee6a Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-06 05:15:44 +00:00
ScrollBar.vertical: ScrollBar {}
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
TextArea.flickable: TextArea {
id: textArea
doc: Update TextEdit.textFormat, text and TextDocument.source Update docs after b46d6a75ac16089de1a29c773e7594a82ffea13e, fdbacf2d5c0a04925bcb3aecd7bf47da5fb69227 etc. Pick-to: 6.7 Change-Id: Ieb49d6876f0a86031fb0ffe970f695e5acbe4c43 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
2024-03-05 21:26:06 +00:00
textFormat: Qt.AutoText
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
wrapMode: TextArea.Wrap
focus: true
selectByMouse: true
texteditor: enable persistent selection We want to keep the selection even if the editor loses focus when a color or font dialog is opened. The selected color or font should naturally apply to the whole text selection that was there before the dialog was opened. Change-Id: I76e6b95f979a090533b028be76e7b2cf1fd53e99 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-08-12 19:18:17 +00:00
persistentSelection: true
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
// Different styles have different padding and background
// decorations, but since this editor is almost taking up the
// entire window, we don't need them.
leftPadding: 6
rightPadding: 6
topPadding: 0
bottomPadding: 0
background: null
Revert "TextEditor example: add actions to built-in context menu, remove custom menu" This reverts commit e5824ea91bde8d361ca5e1a2939a892870db0622. Reason for revert: dfcde3ea4d8a81d511cce5fb5eccdbb47e92d2c7, which this requires, causes a regression: QTBUG-134903. The feature will be post-poned to 6.10 instead. Also amends da064518e463128a75f7dfaba23cda0c1961ca55 in order to keep it working after a small conflict. Change-Id: I339e1afc77b11bf446d04aad5aae933c8c1f6b45 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
2025-05-13 04:08:24 +00:00
TapHandler {
acceptedButtons: Qt.RightButton
onTapped: contextMenu.popup()
}
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
onLinkActivated: function (link) {
Qt.openUrlExternally(link)
}
Add load/save functionality to QQuickTextDocument (Tech Preview) Since QTBUG-92155 is not done, we need an easy way to load and save text into and out of a QTextDocument in QML. This patch follows the pattern from Image and other types: add a `source` property, a URL from which the file is to be loaded. When it comes to saving, the pattern is not set: so far the only file writing that has been available from QML is ItemGrabResult.saveToFile(). Since we need to save in specific formats, it makes sense to continue that pattern: the text document knows how to do its own serialization, so this is not suitable for generic data file I/O, even if we did have a QML API for that. We add invokable functions save() and saveAs() for the usual use cases in word processors and such. The URL extension determines the file format. Setting QQuickTextDocument's source is not allowed if the document has unsaved changes. The user (app author) needs to call save() or override modified to false first. [ChangeLog][QtQuick][TextEdit] TextEdit.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. Change-Id: I687318523c7a520e02244e47224d067da55318b5 Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-06 14:14:06 +00:00
Get rid of DocumentHandler in the Text Editor example ...and fix a couple of minor issues that remained. Fixes: QTBUG-81022 Change-Id: I5fc1547fb09caef5a9e24d95c2ca7b8d78ee104a Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-22 20:45:46 +00:00
Component.onCompleted: {
if (Qt.application.arguments.length === 2)
Use lookup table to show TextDocument status in texteditor example Computed properties make it possible to use scoped enum values as object property names. Amends bec8df96b7615c6ce419867254027773ea7fd6b1 Also remove semicolons for consistency. Pick-to: 6.7 Task-number: QTBUG-121946 Change-Id: I1ee354722d9f0e065637731d1b535389a9cb0032 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
2024-02-05 21:59:57 +00:00
textDocument.source = "file:" + Qt.application.arguments[1]
Get rid of DocumentHandler in the Text Editor example ...and fix a couple of minor issues that remained. Fixes: QTBUG-81022 Change-Id: I5fc1547fb09caef5a9e24d95c2ca7b8d78ee104a Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-22 20:45:46 +00:00
else
Use lookup table to show TextDocument status in texteditor example Computed properties make it possible to use scoped enum values as object property names. Amends bec8df96b7615c6ce419867254027773ea7fd6b1 Also remove semicolons for consistency. Pick-to: 6.7 Task-number: QTBUG-121946 Change-Id: I1ee354722d9f0e065637731d1b535389a9cb0032 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
2024-02-05 21:59:57 +00:00
textDocument.source = "qrc:/texteditor.html"
Get rid of DocumentHandler in the Text Editor example ...and fix a couple of minor issues that remained. Fixes: QTBUG-81022 Change-Id: I5fc1547fb09caef5a9e24d95c2ca7b8d78ee104a Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-22 20:45:46 +00:00
}
texteditor example: use TextDocument status rather than error signal Amends 5647b6900b2ecc291022143176b545b933eca3a8 in which the error signal was removed and replaced with a status property. Pick-to: 6.7 Change-Id: I433987fe4c480c910c98c8fd3714c2e426e49c0f Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2024-02-02 22:47:14 +00:00
textDocument.onStatusChanged: {
Use lookup table to show TextDocument status in texteditor example Computed properties make it possible to use scoped enum values as object property names. Amends bec8df96b7615c6ce419867254027773ea7fd6b1 Also remove semicolons for consistency. Pick-to: 6.7 Task-number: QTBUG-121946 Change-Id: I1ee354722d9f0e065637731d1b535389a9cb0032 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
2024-02-05 21:59:57 +00:00
// a message lookup table using computed properties:
// https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Object_initializer
const statusMessages = {
[ TextDocument.ReadError ]: qsTr("Failed to load “%1”"),
[ TextDocument.WriteError ]: qsTr("Failed to save “%1”"),
[ TextDocument.NonLocalFileError ]: qsTr("Not a local file: “%1”"),
texteditor example: use TextDocument status rather than error signal Amends 5647b6900b2ecc291022143176b545b933eca3a8 in which the error signal was removed and replaced with a status property. Pick-to: 6.7 Change-Id: I433987fe4c480c910c98c8fd3714c2e426e49c0f Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2024-02-02 22:47:14 +00:00
}
Use lookup table to show TextDocument status in texteditor example Computed properties make it possible to use scoped enum values as object property names. Amends bec8df96b7615c6ce419867254027773ea7fd6b1 Also remove semicolons for consistency. Pick-to: 6.7 Task-number: QTBUG-121946 Change-Id: I1ee354722d9f0e065637731d1b535389a9cb0032 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
2024-02-05 21:59:57 +00:00
const err = statusMessages[textDocument.status]
if (err) {
errorDialog.text = err.arg(textDocument.source)
texteditor example: use TextDocument status rather than error signal Amends 5647b6900b2ecc291022143176b545b933eca3a8 in which the error signal was removed and replaced with a status property. Pick-to: 6.7 Change-Id: I433987fe4c480c910c98c8fd3714c2e426e49c0f Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2024-02-02 22:47:14 +00:00
errorDialog.open()
}
Add load/save functionality to QQuickTextDocument (Tech Preview) Since QTBUG-92155 is not done, we need an easy way to load and save text into and out of a QTextDocument in QML. This patch follows the pattern from Image and other types: add a `source` property, a URL from which the file is to be loaded. When it comes to saving, the pattern is not set: so far the only file writing that has been available from QML is ItemGrabResult.saveToFile(). Since we need to save in specific formats, it makes sense to continue that pattern: the text document knows how to do its own serialization, so this is not suitable for generic data file I/O, even if we did have a QML API for that. We add invokable functions save() and saveAs() for the usual use cases in word processors and such. The URL extension determines the file format. Setting QQuickTextDocument's source is not allowed if the document has unsaved changes. The user (app author) needs to call save() or override modified to false first. [ChangeLog][QtQuick][TextEdit] TextEdit.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. Change-Id: I687318523c7a520e02244e47224d067da55318b5 Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-06 14:14:06 +00:00
}
Revert "TextEditor example: add actions to built-in context menu, remove custom menu" This reverts commit e5824ea91bde8d361ca5e1a2939a892870db0622. Reason for revert: dfcde3ea4d8a81d511cce5fb5eccdbb47e92d2c7, which this requires, causes a regression: QTBUG-134903. The feature will be post-poned to 6.10 instead. Also amends da064518e463128a75f7dfaba23cda0c1961ca55 in order to keep it working after a small conflict. Change-Id: I339e1afc77b11bf446d04aad5aae933c8c1f6b45 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
2025-05-13 04:08:24 +00:00
}
}
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
Revert "TextEditor example: add actions to built-in context menu, remove custom menu" This reverts commit e5824ea91bde8d361ca5e1a2939a892870db0622. Reason for revert: dfcde3ea4d8a81d511cce5fb5eccdbb47e92d2c7, which this requires, causes a regression: QTBUG-134903. The feature will be post-poned to 6.10 instead. Also amends da064518e463128a75f7dfaba23cda0c1961ca55 in order to keep it working after a small conflict. Change-Id: I339e1afc77b11bf446d04aad5aae933c8c1f6b45 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
2025-05-13 04:08:24 +00:00
Menu {
id: contextMenu
MenuItem {
text: qsTr("Copy")
action: copyAction
}
MenuItem {
text: qsTr("Cut")
action: cutAction
}
MenuItem {
text: qsTr("Paste")
action: pasteAction
}
MenuSeparator {}
MenuItem {
text: qsTr("Font...")
onTriggered: function () {
fontDialog.selectedFont = textArea.cursorSelection.font
fontDialog.open()
}
}
MenuItem {
text: qsTr("Color...")
onTriggered: function () {
colorDialog.selectedColor = textArea.cursorSelection.color
colorDialog.open()
}
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}
}
TextEditor: Add modified handling Add a modified property to the document and add handling in onClosing(). Connect the actions to call close() instead of Qt.quit() for it to become active. Change-Id: I0fec75629db64e91508ed8ba45d4fb60be146b1b Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2019-08-19 14:01:05 +00:00
TextEditor: Clean up example and use quick dialogs The text editor example is dependent on Qt.labs for its dialogs and native menus. The long term goal is to remove the Qt.labs dependency, and replace it with components from QtQuick. Currently we have a file and a font dialog, that should be used instead of the Qt.labs dialogs. I'm also replacing some of the properties in the DocumentHandler, since I don't think it makes sense for the font to be limited to only a few font weights and styles (which can be selected through the font dialog). Selecting the most common font weight and style is still possible using the bold and italic shortcuts and toolbar buttons. Some more features includes: * An additional toolbar button, which can be used to strikeout the selected font. This required adding an additional glyph to fontello.ttf. * When coupled with the fix for QTBUG-96934, the font for the current selection should automatically update the listviews in the font dialog to select the correct family, style, sizes and effects for what is selected in the document handler. Fixes: QTBUG-95976 Pick-to: 6.2 Change-Id: I2907a2270e2a139b1ccb3fcb3ce3a788306a42e3 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2021-09-23 15:45:44 +00:00
onClosing: function (close) {
Add load/save functionality to QQuickTextDocument (Tech Preview) Since QTBUG-92155 is not done, we need an easy way to load and save text into and out of a QTextDocument in QML. This patch follows the pattern from Image and other types: add a `source` property, a URL from which the file is to be loaded. When it comes to saving, the pattern is not set: so far the only file writing that has been available from QML is ItemGrabResult.saveToFile(). Since we need to save in specific formats, it makes sense to continue that pattern: the text document knows how to do its own serialization, so this is not suitable for generic data file I/O, even if we did have a QML API for that. We add invokable functions save() and saveAs() for the usual use cases in word processors and such. The URL extension determines the file format. Setting QQuickTextDocument's source is not allowed if the document has unsaved changes. The user (app author) needs to call save() or override modified to false first. [ChangeLog][QtQuick][TextEdit] TextEdit.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. [ChangeLog][Controls][TextArea] TextArea.textDocument now has a source property for loading files; save() and saveAs() functions for writing; a modified property which tracks QTextDocument::modified; and an error signal in case any of these operations fail. Setting the source property is allowed only if the document is in unmodified state. This API is in Tech Preview. Change-Id: I687318523c7a520e02244e47224d067da55318b5 Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
2023-11-06 14:14:06 +00:00
if (textArea.textDocument.modified) {
TextEditor: Add modified handling Add a modified property to the document and add handling in onClosing(). Connect the actions to call close() instead of Qt.quit() for it to become active. Change-Id: I0fec75629db64e91508ed8ba45d4fb60be146b1b Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
2019-08-19 14:01:05 +00:00
quitDialog.open()
close.accepted = false
}
}
Add Text Editor example A follow up commit will contain the touch UI. Change-Id: I26275fdd31294506821fa3e3e4a4bb63329665b9 Task-number: QTBUG-54952 Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
2016-07-06 11:04:07 +00:00
}