How to drag selected text to area currently off screen
-
@guy038 said in How to drag selected text to area currently off screen:
Hello @speedy-mercer, @alan-kilborn, and All,
@speedy-mercer, why didn’t you add a new issue directly at the official N++ issues tracker ?
https://github.com/notepad-plus-plus/notepad-plus-plus/issues
Simply, click on the green
New issuebutton, on the right !I wasn’t aware of it. Once I went there, the instructions were easy to follow.
-
@Alan-Kilborn said in How to drag selected text to area currently off screen:
@Speedy-Mercer said in How to drag selected text to area currently off screen:
Where did that statement come from? I can’t find it in this thread yet Ekopalypse seems to think it was from me.
No, Eko doesn’t think it was from you. It’s from this link: https://sourceforge.net/p/scintilla/feature-requests/497/
Stupid question time, What IS “scintilla”? I noticed a reference to it in Notepad++'s settings. (sorry if “stupid newbie” question but, if the shoe fits…)
-
The underlying control used by notepad++ to color your code.
-
Issue entered here: https://github.com/notepad-plus-plus/notepad-plus-plus/issues/8110
-
@Alan-Kilborn said in How to drag selected text to area currently off screen:
@Speedy-Mercer said in How to drag selected text to area currently off screen:
Where did that statement come from? I can’t find it in this thread yet Ekopalypse seems to think it was from me.
No, Eko doesn’t think it was from you. It’s from this link: https://sourceforge.net/p/scintilla/feature-requests/497/
Ok, more stupid question time, when does scintilla version 4.3.1 get incorporated into Notepad++?
-
It’s hard to say, in the past it wasn’t really like that,
that a new scintilla version resulted in a new Npp version.
Furthermore, as far as I understand, updates to scintilla
are @Don-HO 's tasks - exclusively. -
Okay, so… where do I go from here?
-
where do I go
You’re already there. You wait. :-)
But in the meantime, how bad is ctrl+x … ctrl+v ?
Apparently the thousands(?) of Notepad++ users have been using the keyboard way of doing it for 17 years and you are the first person to notice the mouse-drag-and-drop thing, so I don’t see it as a fatal-flaw-gotta-address-immediately kind of thing. -
@Alan-Kilborn No, It’s not a “fatal flaw” but when you have been used to doing it that way for several decades, ya tend to notice and miss it. ;-)
-
@Alan-Kilborn that is not true, 3 of ~10 people I recommended N++, noticed it. I noticed it right after switching, but I thought, that ovious bug will be fixed in 1-2 minor versions. That was more than 10 years ago and almost nobody of the non-nerds will create an issue or a ticket, and developers all over the world are happy, that normal people won’t get to places like here that often, right? Thanks to @Speedy-Mercer to write this down here! By the way, it is still not fixed and ctrl+x … ctrl+v is not the solution. Is it fixed in “scintilla” right now? I have no idea.
-
My earlier comment was based upon my efforts to “keep current” with reported bugs and user complaints for a number of years on this site.
If “3 of 10” people notice it and no one complains, that’s like 0 of 10. :-)
But, regardless, the situation hasn’t changed from the above.
ctrl+x … ctrl+v is not the solution
Well, it is if you want to move a bit of text to a destination when you can’t see both the source and destination points at the same time.
Or, you can just decide you aren’t going to edit your document the way you need to.
-
I wanted to say: it’s a workaround ;-) solution would be a fix. I’m using ctrl+x … ctrl+v every day in N++, but to be honest: it really sucks. And it’s not, that people didn’t complain, but I (that was the joke) said “yeah, I know, but except that, it’s a great software, they will fix it.”
-
@mario-ahner said in How to drag selected text to area currently off screen:
And it’s not, that people didn’t complain
The point isn’t that no one complained to each other. It’s that no one informed the development team there was a problem.
From your anecdotal evidence, N% of Notepad++ users did notice; but from the measurable data available in the issues tracker, 0% of those N% cared enough to report the problem to someone who could do anything about it: thus, there were 0%. If no one cares enough to report the problem, the problem cannot be fixed, because no one officially knows about it.
Just keep that in mind for the future: when you find a problem, you can ask about it here, and we can confirm or contradict your findings; but once you know it’s a real issue, if you don’t report it to the official issues tracker, the issue will remain unfixed.
-
I’m just glad, it is fixed. :-)
Next time I will cry louder and earlier.
