changing the editor's behaviour

How do I change the size of the font in the editor interface, not in the game

and

how do I stop the editor from erasing the text if there's a compiler error? I'm getting tired of trying to fix bugs by retyping everything in and then figuring out where the bug is.


The GUI/Editor is a bit clunky unfortunately with its scripting controls... if interested in learning to code, it makes everything much easier/faster, as you're typing in everything, letting you copy-paste, saving what you've done, and etc.

Trouble-shooting / bug-fixing, is a "fact of life" of programming / game making... just get used to it... laughs


I'm a very experienced programmer. I was building MUDS from the UNIX command line when the internet was still AARPA net, and everyone was on 2400 baud dial up.

If there's no way to stop the text from being erased, that needs to be implemented and instead, the error needs to be highlighted in red.


By "editor", do you mean the normal GUI view or the code view? And are using the Windows desktop version or the online editor? And can you describe when the text is being erased? I'd like to try to reproduce it, so I can know what the problem is.


using the windows desktop version and I mean any interface that isn't the game play testing interface.

At the moment the only compiler errors I've had have been when I've been trying to write an expression for a command. In the script ->expression field, any error (missing " marks or whatever), I'll get a compiler error (expected) and the text will vanish, to be replaced with the previous text (if there was any).

And because the font is so tiny (for me), I have had to resort to working in wordpad then copying the text and pasting it into the expression field.


I see. So my best answers:

  1. I don't see a way to do that via the interface. It's built into the forms for the program. I don't know what it would take to make that switchable. (It depends on how VB is set up for that sort of thing.)
  2. Regarding the clearing, I did see that happen. I don't know if it would be easier, but if when editing an expression, you click the Code View icon (either the rightmost or second rightmost one above your text, depending on where you are), then you can enter your expression there. And when you try to switch back, if there is an error in the expression, it will just show you the expression in red without throwing it away. If you have experience programming, the Code View might make more sense anyway, and it's convenient in Quest that you can switch to it on a per-line basis as opposed to the global switch on the main toolbar, which takes you completely out of GUI-land.

I'll switch to Code View, thank you.

Not sure how VB is set up for font size, but it would make it much easier on probably a lot of us older folks with failing eyesight if it would be resized.


This topic is now closed. Topics are closed after 60 days of inactivity.

Support

Forums