How to detect CMD-V in the SE

[dunbarx]

I have a little tool that sets the backColor of selected portions of the SE so I can find those areas again while debugging. Has worked fine for many years.

Code: Select all

   ...get the selectedLines
            put word 2 of it into startLine ; put word 4 of it into endLine ; put word 7 of it into tField --tField is the SE
            set the backColor of line startline to endLine of fld tField to "255,255,215"

The colored portions are robust in that if I add or delete lines within such a colored portion, the backColor adjusts to the extent of the new lines. But if I paste anything anywhere, the backColor of the entire SE reverts to the default empty.

I guess I can store the current text portions in a custom property somewhere and reColor every time the SE is in front and I paste something, but does anyone have a better idea? I am a little skittish about lightly hacking the SE in the first place.

The point of this query is really this: Dammit, why does pasting change the backColor of an SE field? It does not do so in an "ordinary" field, and isn't the SE just a stack with fields on it? What sort of baggage does this stack carry, and how can I bypass it instead of recoloring each time I paste?

Craig

[richmond62]

That 'SE' was not very helpful: took me a while to work out you mean the Script Editor . . .

And, I must be missing something, as this:
-

-
doesn't do anything.

[FourthWorld]

Exercise for the brave reader: start in the SE's File menu, and manually trace out the chain of calls from the case block in menuPick for the Save item.

[dunbarx]

@ Richmond.

And I also did not, though years ago, know right away what the "SE" was when I first saw it.

But what on earth could that line of code of yours possibly do? The SE is a stack, and contains one or more fields for each control that one is working with. The "scriptEditor" is not, as you wrote it, a custom property of some button.

The "selectedLines" function returns a string that can be decomposed as I posted. It contains all the information I (or anyone) need to color a block of lines. Try it.

@ Richard.

I will try to dig though that. I assume, since you mentioned it, that there are perhaps front or back scripts that might do things to the properties of SE fields upon dealing with a paste. If I cannot safely work that, I will do plan B, save the selected lines in a custom property and recolor after each paste, trapping "rawKeyDown 118" with commandKey .

Craig

[jacque]

My guess is that a paste requires the SE to recalculate the red dot breakpoints, the formatting, and the text coloration; basically the entire display, so it reverts to LC native script styling.

[bn]

@Dunbarx,

You would probably like to look at handler

actionPaste in stack "com.livecode.scripteditor.behavior.editorcommon"
For me the easiest is to open the stack via the Properties Inspector with "Show IDE Stacks in Lists" turned on.
Whatever you do it will probably confuse the Script Editor.

Kind regards
Bernd

[dunbarx]

Bernd.

I am used to confusing my betters.

I think I will do plan B. the reColorizing thing. I can do that in ten minutes in the plug-in I use for all my tools, including testing to see why it does not work.

Craig

[bn]

Craig,

in case you want to try to change 'actionPaste':

Code: Select all

   
   -- more code
   textEndGroup
   set the backColor of char tFrom to tFrom + length(the clipboardData["text"]) of field "Script" of me to "yellow" ## add this line
   unlock screen
end actionPaste

It sets the backColor, if you want to paste repeatedly you will have to turn "Auto Format" in Preferences off.

If you reformat the script your colorization will be gone but you know that already.

Saving stack "com.livecode.scripteditor.behavior.editorcommon" will make the changes permanent for that copy of LC.

I just wanted to know what it takes to implement your colorization when pasting in Script Editor.

Kind regards
Bernd

[dunbarx]

Bernd.

I have not looked into any of the innards of the SE stack. My tool tallies up any tracts of selected lines and colorizes them, all from a keyboard shortcut.

I will just store the line data in a custom property of the SE every time I invoke the code that colorizes in the first place. Then upon CMD-V restore those lines.

Craig