One can change the textSize of the script section in the LC preferences, which allows one to see more lines of code at one extreme, or to make that area easier to read at the other.
Is there a way to change the variable pane as well? I have the upper section set to size 8. It looks like the lower section is 18. I would love to see more lines down there as well. Saves a lot of scrolling.
I would have thought that changing one would also change the other.
Craig Newman
Change the textSize in the variable pane of the SE
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- VIP Livecode Opensource Backer
- Posts: 9665
- Joined: Wed May 06, 2009 2:28 pm
- Location: New York, NY
Change the textSize in the variable pane of the SE
Last edited by dunbarx on Sat Feb 24, 2018 8:19 pm, edited 1 time in total.
-
- Livecode Opensource Backer
- Posts: 9388
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: Change the textSize in the variable pane of the SE
Well, it took me a few minutes to think about that one:
If you open any old stack you have to hand and open the scriptEditor for any object,
and then open the properties palettes you should be
able to select the stack "revNewScriptEditor 1" and then
the group "Variables"; and then you can mess around with the textSize, font, and so to your
heart's content.
Once you have what you want, save the thing via the Message Box:
save stack "revNewScriptEditor 1"
HOWEVER this won't 'stick' beyond that instance of the scriptEditor.
Neither will doing the same via script:
Trying to do that to the stack "revNewScriptEditor" just throws a "bluey".
If you open any old stack you have to hand and open the scriptEditor for any object,
and then open the properties palettes you should be
able to select the stack "revNewScriptEditor 1" and then
the group "Variables"; and then you can mess around with the textSize, font, and so to your
heart's content.
Once you have what you want, save the thing via the Message Box:
save stack "revNewScriptEditor 1"
HOWEVER this won't 'stick' beyond that instance of the scriptEditor.
Neither will doing the same via script:
Trying to do that to the stack "revNewScriptEditor" just throws a "bluey".
-
- VIP Livecode Opensource Backer
- Posts: 9665
- Joined: Wed May 06, 2009 2:28 pm
- Location: New York, NY
Re: Change the textSize in the variable pane of the SE
Richmond.
This is similar to the thread about changing the textColor of the various elements in the SE, such as comments, keywords, etc.
The changes do not stick. I still have not played with Bogs' recipe for that, but when I do, I bet the same procedure will be applicable to this as well.
Craig
This is similar to the thread about changing the textColor of the various elements in the SE, such as comments, keywords, etc.
The changes do not stick. I still have not played with Bogs' recipe for that, but when I do, I bet the same procedure will be applicable to this as well.
Craig
Re: Change the textSize in the variable pane of the SE
That is probably true Craig, although honestly I haven't messed with it much at this point.
Funny thing I found, since (through the generosity of many, including Richmond there) I now have an almost complete history set of RR-Lc IDEs from the start, the earliest of them have exactly what you are talking about in that thread about coloring text, right from the script editor preferences. You could not only color text that is colored now (commands, keywords, functions, etc.), but you could literally add words you wanted colored.
Of course, that doesn't help with this topic, since the debugger wasn't integrated with the script editor until the later 2.x part of the run, and when it was apparently a lot of other nice features got thrown out for some reason.
Funny thing I found, since (through the generosity of many, including Richmond there) I now have an almost complete history set of RR-Lc IDEs from the start, the earliest of them have exactly what you are talking about in that thread about coloring text, right from the script editor preferences. You could not only color text that is colored now (commands, keywords, functions, etc.), but you could literally add words you wanted colored.
Of course, that doesn't help with this topic, since the debugger wasn't integrated with the script editor until the later 2.x part of the run, and when it was apparently a lot of other nice features got thrown out for some reason.