-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Disable selecting content on the top bar of the left panel on the iPhone #9096
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
Comments
There is no context menu on the iPhone, so we will disable the select event |
Hello, thanks for fixing that! And here are the answers referring to your question: I
i apologize for my expressing, but what I was referring is the issue that: I can't move these buttons (shows in the image below) on iPad, because moving these buttons need to right-click the mouse to call the and i was just saying maybe long press to call the context menu (AKA "more" menu or "right-click" menu is a designing option) II
i meant this button: on iOS / iPad and android, when long press a note or notebook in thank you again! |
for the question 2, it's a vid that how obsidian does when long press a note. RPReplay_Final1693837041.mov |
oh and sorry I found another issue that I can't seem to delete a workspace on iPad once it's created. |
|
thank you again! I
yes thank you! and just to be more clear, what I meant is that since iPad doesn't have a mouse, so all the operate which need right-clicking the mouse, is not able to do on iPad. II
yes, indeed, thank you so much! III
i apologize for my misunderstood, is this a TODO or an instruction? cuz if it's an instruction, i can't find any element/button related to " workspace" or similar thing in about Thank you! |
yes, thank you for your helping! but it seems as i said, that button in your screenshot can't delete a profile/workspace either. On iPad i can only remove a workspace/profile from the list by touch the "X" icon, the entire workspace/profile hadn't been deleted, still exist, because I can open it later again by "open" button even after I removed it. Also as you mentioned, i tested the iPhone client too, and it turns out I can't completely delete a workspace on iPhone either. (the "-" button just remove it from list, too, because after i removed it i can still open again with "open" button) on android, i can delete a workspace using root permission + file manager, but can't delete it within siyuan app itself. sorry if it's just because i didn't find it, but it's at least not that obvious. |
It used to be physically deleted, but some users often deleted it by mistake, so it was later changed to remove it from the workspace list. |
Thank you for your answer! Maybe it's a nice design, however personally I think it's also important to be able to physically delete a workspace (maybe it could be located deeply in settings or something to prevent accident), since on iOS devices, the user can't really use file manager to manage files. |
@STMRabbit We will implement it in the next version, thanks #9134 |
Thank you so much for the quick fix! In case I expressed myself incorrectly last time, the term "uninstall SiYuan and install it again" was meant to describe the procedure for clearing data. It's not intended as a threat, like "if you don't implement it, the user will uninstall and leave." :) |
In what scenarios do you need this feature?
Not supporting long press caused these issues on mobile:
For now, long press elements on mobile devices is calling "select text", which doesn't make sense, it should be like:
Describe the optimal solution
Maybe long press also should be supported on desktop app as well, considering there are desktop devices which support touch screen like Microsoft Surface or Pinetab. But I don't have those devices, so I can't give a clear suggestion.
Describe the candidate solution
At least disable long press calling on non-editor elements because that feature is useless and even disturbing.
Other information
mobile note taking app with same tec stack (for reference)
joplin
obsidian
The text was updated successfully, but these errors were encountered: