Hi there,
Can't find any previous posts about this but i'm sure there must be
When holding down left mouse button and selecting text in PL Editor, it extends the text selection/highlight beyond user selection in certain scenarios. So you can't precisely select/copy/extract code segments from a line of code to be used elsewhere in pogram.
e.g. sample code
fileappend( "c:\" + "History" + ".html"
, "<!doctype html>" + newline
+ "<html>" + newline
if say i try to precisely copy the text 'html' from the 3rd line, the highlighted selection bleeds over the greater than and less than signs and the speech marks
Is there something that can be set to prevent this from happening ?
Mark
PL Editor - Text Select Assumptions [SOLVED]
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
Re: PL Editor - Text Select Assumptions
Why don't you double click on it?Hi there,
Can't find any previous posts about this but i'm sure there must be
When holding down left mouse button and selecting text in PL Editor, it extends the text selection/highlight beyond user selection in certain scenarios. So you can't precisely select/copy/extract code segments from a line of code to be used elsewhere in pogram.
e.g. sample code
fileappend( "c:\" + "History" + ".html"
, "<!doctype html>" + newline
+ "<html>" + newline
if say i try to precisely copy the text 'html' from the 3rd line, the highlighted selection bleeds over the greater than and less than signs and the speech marks
Is there something that can be set to prevent this from happening ?
Mark
- Attachments
-
- highlight.png
- (3.61 KiB) Downloaded 853 times
Re: PL Editor - Text Select Assumptions
Thank you for taking the time to reply
It's good to know i'm not creating extra support for an issue that's already been dealt with previously.
Tried your suggestion and i can see what your saying but it's still fiddly and doesn't work consistently.
Try this example
"</body>"
select all "</body>"
then select only part /body
whether you single click or double click it selects more than /body
Because i'm programming with this everyday it's become a real pain, find myself having to code in EL TSDE and when finished copying it all over to PL editor. But you still run into it when making quick mods at the end.
The ideal fix would be an option to switch off any highlighting assumptions.
A user is quite capable of determining what they want to copy and paste.
Other than maybe microsoft word, copy and pasting of text works from where the user first places the cursor, holds down left mouse button, drags to the end of their selection, right click, copy. No other app i regularly use exceeds user selection or highlights more than what user selected to be copied.
Mark
It's good to know i'm not creating extra support for an issue that's already been dealt with previously.
Tried your suggestion and i can see what your saying but it's still fiddly and doesn't work consistently.
Try this example
"</body>"
select all "</body>"
then select only part /body
whether you single click or double click it selects more than /body
Because i'm programming with this everyday it's become a real pain, find myself having to code in EL TSDE and when finished copying it all over to PL editor. But you still run into it when making quick mods at the end.
The ideal fix would be an option to switch off any highlighting assumptions.
A user is quite capable of determining what they want to copy and paste.
Other than maybe microsoft word, copy and pasting of text works from where the user first places the cursor, holds down left mouse button, drags to the end of their selection, right click, copy. No other app i regularly use exceeds user selection or highlights more than what user selected to be copied.
Mark
- Henry MultiСharts
- Posts: 9165
- Joined: 25 Aug 2011
- Has thanked: 1264 times
- Been thanked: 2957 times
Re: PL Editor - Text Select Assumptions
Hello Mark,
We will check what can be done with this behavior.
We will check what can be done with this behavior.
Re: PL Editor - Text Select Assumptions
Ah that's brilliant news
If they go ahead which i really really hope they do, can you ensure they account for text selection right to left aswell as left to right. Noticed over time they behave differently and for whatever reason i find myself mostly using right to left to copy and paste bits of code around the place.
Mark
If they go ahead which i really really hope they do, can you ensure they account for text selection right to left aswell as left to right. Noticed over time they behave differently and for whatever reason i find myself mostly using right to left to copy and paste bits of code around the place.
Mark
- JoshM
- Posts: 2195
- Joined: 20 May 2011
- Location: The Netherlands
- Has thanked: 1544 times
- Been thanked: 1565 times
- Contact:
Re: PL Editor - Text Select Assumptions
Any update on better selection features for the PowerLanguage Editor?We will check what can be done with this behavior.
* * * * *
Edit:
Speaking of the Editor and improved productivity tweaks, can the "Intellisense" feature also not pop-up when I type a number?
I don't see the sense in this (there is no function that begins with a "9"), but does increase the chances of making an error:
- Attachments
-
- scr.06-09-2014 15.07.46.png
- (2.27 KiB) Downloaded 807 times
-
- Posts: 55
- Joined: 10 Jul 2014
- Has thanked: 10 times
- Been thanked: 18 times
Re: PL Editor - Text Select Assumptions
This slight thought seems to fit here nicely and never felt deserving of a request...
I sure would love a little option to select whether to use [Tab] or [Enter] for auto-complete in the editor. For those of us that use Visual Studio having that small consistency to use [Tab] would certainly make sense and be quite welcome.
I sure would love a little option to select whether to use [Tab] or [Enter] for auto-complete in the editor. For those of us that use Visual Studio having that small consistency to use [Tab] would certainly make sense and be quite welcome.
- Henry MultiСharts
- Posts: 9165
- Joined: 25 Aug 2011
- Has thanked: 1264 times
- Been thanked: 2957 times
Re: PL Editor - Text Select Assumptions [SOLVED]
Ah that's brilliant news. If they go ahead which i really really hope they do, can you ensure they account for text selection right to left aswell as left to right. Noticed over time they behave differently and for whatever reason i find myself mostly using right to left to copy and paste bits of code around the place. Mark
This behavior will be improved in MultiCharts 9.0 Release Candidate.Any update on better selection features for the PowerLanguage Editor?
- Henry MultiСharts
- Posts: 9165
- Joined: 25 Aug 2011
- Has thanked: 1264 times
- Been thanked: 2957 times
Re: PL Editor - Text Select Assumptions
It does not happen on my end. Are you able to replicate it on a constant basis?* * * * *
Edit:
Speaking of the Editor and improved productivity tweaks, can the "Intellisense" feature also not pop-up when I type a number?
I don't see the sense in this (there is no function that begins with a "9"), but does increase the chances of making an error:
- TJ
- Posts: 7745
- Joined: 29 Aug 2006
- Location: Global Citizen
- Has thanked: 1033 times
- Been thanked: 2224 times
Re: PL Editor - Text Select Assumptions
It also happens on my MultiCharts64 Version 8.8 Release (Build 8967).It does not happen on my end. Are you able to replicate it on a constant basis?* * * * *
Edit:
Speaking of the Editor and improved productivity tweaks, can the "Intellisense" feature also not pop-up when I type a number?
I don't see the sense in this (there is no function that begins with a "9"), but does increase the chances of making an error:
When I type a number, the drop down list would pop up, which makes coding in the PLE a pain.
ps. This is with Auto-Complete enabled. Previously Auto-Complete does not detect numbers.
- arnie
- Posts: 1594
- Joined: 11 Feb 2009
- Location: Portugal
- Has thanked: 481 times
- Been thanked: 514 times
Re: PL Editor - Text Select Assumptions
It does not happen on my end. Are you able to replicate it on a constant basis?* * * * *
Edit:
Speaking of the Editor and improved productivity tweaks, can the "Intellisense" feature also not pop-up when I type a number?
I don't see the sense in this (there is no function that begins with a "9"), but does increase the chances of making an error:
If I'm not mistaken this is something that always happened in MC.
I can't remember any version where this wouldn't happened.
Definitely a pain since if you write the number and hit Enter key it will assume the selected function/keyword and not the number. To surpass this one need always to move the cursor down/up so the box disappears
- Henry MultiСharts
- Posts: 9165
- Joined: 25 Aug 2011
- Has thanked: 1264 times
- Been thanked: 2957 times
Re: PL Editor - Text Select Assumptions
It also happens on my MultiCharts64 Version 8.8 Release (Build 8967).
When I type a number, the drop down list would pop up, which makes coding in the PLE a pain.
ps. This is with Auto-Complete enabled. Previously Auto-Complete does not detect numbers.
It turns out that only signals are affected. We will analyze this behavior in more details.If I'm not mistaken this is something that always happened in MC.
I can't remember any version where this wouldn't happened.
Definitely a pain since if you write the number and hit Enter key it will assume the selected function/keyword and not the number. To surpass this one need always to move the cursor down/up so the box disappears
- TJ
- Posts: 7745
- Joined: 29 Aug 2006
- Location: Global Citizen
- Has thanked: 1033 times
- Been thanked: 2224 times
Re: PL Editor - Text Select Assumptions
It is affecting my indicators as well.It turns out that only signals are affected. We will analyze this behavior in more details.
- JoshM
- Posts: 2195
- Joined: 20 May 2011
- Location: The Netherlands
- Has thanked: 1544 times
- Been thanked: 1565 times
- Contact:
Re: PL Editor - Text Select Assumptions
Yes, it always happens, in signals, functions, and indicators. I'm using MultiCharts64 Version 8.8 Release (Build 8967) with PowerLanguage Editor 1.6.8967.400.It does not happen on my end. Are you able to replicate it on a constant basis?
This issue does not only occur when assigning a value to a variable. It also happens when declaring an input (in this case, in an indicator):
Or when declaring a variable:
It does not happen when entering a numeric value in a function:
As far as I know, this has indeed always happened.If I'm not mistaken this is something that always happened in MC.
I can't remember any version where this wouldn't happened.
This is from MultiCharts Version 7.4 (Build 4953) and PowerLanguage Editor 1.6.4953.0:
Indicator:
Signal:
(It also happens with functions on MC 7.4, but it's probably clear by now).
- Attachments
-
- scr.09-09-2014 10.52.35.png
- (1.63 KiB) Downloaded 728 times
-
- scr.09-09-2014 10.49.39.png
- (2.2 KiB) Downloaded 729 times
-
- scr.09-09-2014 10.46.50.png
- (2 KiB) Downloaded 731 times
-
- scr.09-09-2014 10.45.01.png
- (2.29 KiB) Downloaded 736 times
-
- scr.09-09-2014 10.43.40.png
- (2.58 KiB) Downloaded 733 times
- Henry MultiСharts
- Posts: 9165
- Joined: 25 Aug 2011
- Has thanked: 1264 times
- Been thanked: 2957 times
Re: PL Editor - Text Select Assumptions
It also happens on my MultiCharts64 Version 8.8 Release (Build 8967).
When I type a number, the drop down list would pop up, which makes coding in the PLE a pain. ps. This is with Auto-Complete enabled. Previously Auto-Complete does not detect numbers.
If I'm not mistaken this is something that always happened in MC.
I can't remember any version where this wouldn't happened.
Definitely a pain since if you write the number and hit Enter key it will assume the selected function/keyword and not the number. To surpass this one need always to move the cursor down/up so the box disappears
This behavior has been improved and the issue does not happen since MultiCharts 9.0 beta 1.Yes, it always happens, in signals, functions, and indicators. I'm using MultiCharts64 Version 8.8 Release (Build 8967) with PowerLanguage Editor 1.6.8967.400.
This issue does not only occur when assigning a value to a variable. It also happens when declaring an input (in this case, in an indicator):
Or when declaring a variable:
It does not happen when entering a numeric value in a function:
As far as I know, this has indeed always happened.If I'm not mistaken this is something that always happened in MC.
I can't remember any version where this wouldn't happened.
This is from MultiCharts Version 7.4 (Build 4953) and PowerLanguage Editor 1.6.4953.0:
Indicator:
Signal:
(It also happens with functions on MC 7.4, but it's probably clear by now).