Fix #2458 Unexpected server delete behavior #2459
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
嗯，这样是可以删掉正确的条目，但是还是会跳到最后一项。你试一下4.1.6的效果 |
|
忽然发现，复制也应该是差不多的逻辑。4.1.6就在下一个地方生成重复的条目，现在4.1.7变成了在最后生成。 |
|
删除可以考虑保留当前位置，复制的话由于会定位到复制的位置，倒是没什么关系。 你觉得呢？ @imba-tjd |
|
我个人意见是和4.1.6的行为保持一致…… |
celeron533
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please follow the guide below
You will be asked some questions, please read them carefully and answer honestly
Put an
xinto all the boxes [ ] relevant to your pull request (like that [x])Use Preview tab to see how your pull request will actually look like
Searched for similar pull requests
Compiled the code with Visual Studio
What is the purpose of your pull request?
Description of your pull request and other information
修复删除时事件触发导致，错误的删除。
修改服务器列表位置调整逻辑，与
4.16版本保持一致。Explanation of your pull request in arbitrary form goes here. Please make sure the description explains the purpose and effect of your pull request and is worded well enough to be understood. Provide as much context and examples as possible.