-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback from READ-COM Partner (CTI) #264
Comments
When Cutting content of RootStoryItem in Edit mode (see #220) and when going back to Default story/document using the READ-COM icon in the left sidebar, a warning is shown to the user. See #96 When exiting the application no warning is shown, since application autosaves its current state and will reload with the content that the user was seeing before closing the app |
Greek text was referring to the icon (wrong autotranslation to English, named it as "picture" instead). Solved via #259 |
Undo (CTRL+Z) and other shortcut keys (CTRL+X/CTRL+C/CTRL+V for Cut/Copy/Paste respectively) are supported in the TextStoryItem's text editor and not stolen by the respective actions in the app itself: #97 Undo (editing history) is not currently supported for the story structure itself (needs memory/disk resources). For Cut action can use Paste to undo it (see #70) There is a bug in input prompts that have a text field (like the ActionURL or the Tag one) shown via StoryItemOptions regarding shortcut keys for Cut/Copy/Paste. The app catches them and does cut/copy/paste in the story instead. Have to right click there and use text editing actions from context menu (say to paste a URL in the ActionURL prompt). See #184 |
Version: OLDER/UNSPECIFIED
This is a collection of early feedback during first verisons of app development. Posted here so that entries in it can be matched to issue/enhancement entries in the issue tracking system, will do in comments below. Then this item will be closed
CTI_Feedback_Fani_20220401.pdf
CTI_Feedback_Fani_20220401_AutotranslationEnglish.pdf
The text was updated successfully, but these errors were encountered: