Skip to content
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

[Feature Request]: 手机版长按聊天记录空白处会将文本复制黏贴到输入框占满屏幕 #4861

Open
skhyk opened this issue Jun 19, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@skhyk
Copy link

skhyk commented Jun 19, 2024

Problem Description

当gpt回复的文字足够长时,我需要拖拽屏幕上去看,经常会无意识稍微长按一个位置,输入框就出现了回答的文本,占满了整个屏幕。我再想看聊天记录就得把文本手动删除才能看到。

Solution Description

能否增加一个设置,长按回答空白处时选择是否自动复制黏贴回答到输入框,或者长按仅复制,或者长按弹出一排选项再选择如何操作呢?

Alternatives Considered

No response

Additional Context

No response

@skhyk skhyk added the enhancement New feature or request label Jun 19, 2024
@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


Title: [Feature Request]: Long pressing on the blank space of the chat history in the mobile version will copy and paste the text into the input box to fill the screen.

Problem Description

When the text replied by gpt is long enough, I need to drag it on the screen to read it. I often unconsciously press and hold a position for a while, and the text of the answer appears in the input box, occupying the entire screen. If I want to see the chat history again, I have to manually delete the text before I can see it.

Solution Description

Can you add an option to choose whether to automatically copy and paste the answer into the input box when you long press on the blank space of the answer, or just copy and paste it, or long press to pop up a row of options and then choose how to operate?

Alternatives Considered

No response

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants