-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Selection is very slow [$5 awarded] #406
Comments
Isn't that the problem because of the millions of print outs, which are currently in the qml code? Didn't tested it without them yet, but always thought that they are slowing the gui down. |
I've not seen slow selection, but I have seen it freeze/hang completely after selecting a bit of text. Though I haven't had a chance to look into that yet. |
I've seen the same thing. Text selection bogs down a bit, until it hangs / white screens completely. To add a bit to that, it looks to flatline a core to 100% CPU, and will not respond until I kill the proccess. |
Yes, the cursor movement in general is unusably slow for me. |
I know with selection at the moment there is possible issue with reverse selection and selecting outside the window causes a hang |
I can confirm that Selection fluidity seems improved since last time I tried it. However, there are still a number of other selection and performance bugs. For example, double clicking on a word frequently doesn't select what I expect it to. And performance wise the editor takes quite a while to display the text with the correct indentation when it starts. |
@pwaller, yes, it's very early days still and we need more people helping out with tweaking all those bits (and many more). Please help us by keeping discussions about specific issues in separate issue numbers |
I just compiled this (on arch linux), and selection is still slow for |
For that, the culprit is onSelectionModified in LimeView.qml as it takes longer and longer to complete the more lines are selected. It could be improved quite a bit by instead of completely re-creating all the selection regions for all selected lines, to just tweak the lines that have changed between the last selection and the new one. Marking as enhancement |
Or perhaps more correct, selection should be handled in the backend which has knowledge of color schemes etc. The frontend then only needs to track and render cursor positions seperately. |
Selection & editing a selection are quite slow in the qt gui (when editing
main.go
in the lime source).I understand that the qt gui is in early alpha and am not familiar with the code base, but just wanted to raise my concern as I think making the gui reasonably fast up front is rather important.
--- The **[$5 bounty](https://www.bountysource.com/issues/5225519-selection-is-very-slow?utm_campaign=plugin&utm_content=tracker%2F282001&utm_medium=issues&utm_source=github)** on this issue has been claimed at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282001&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: