Because of the particular configuration of my system I end up with a
super-tiny font in many vtcl windows. I can live with most of these except
for the function editing window. Somtimes I can't even tell what a
particular character is... for example it is almost impossible to
distinguish parenthesis () from curly braces {}.
So... until Stewart adds a font preferences option I am looking for an
alternative for coding most of the procedures within the vtcl application. I
have two ideas and I was wondering if anyone could comment on what some of
the pitfalls that I might run into would be... I'd also be open to hearing
any other suggested solutions.
Here are my two ideas:
1) Put the procedures in an separate "procedures" file and then have this
file source the vtcl-generated file. I could then use any editor I want to
edit the "procedures" file. The one problem that comes to mind is that
vtcl's test mode will probably not work.
2) Edit the vtcl-generated file with another editor. If I just stick to
editing the bodies of the user defined procedures will I be ok? I would
need to be able to read this file back in to vtcl... is there anything that
vtcl requires about the format of the source? I tried this once but vtcl
would no longer see most of the functions or any of the windows... I think
this might have been caused by an extra close-brace in the body of one
function.
Thanks in advance...
Troy
---
R. Troy Monaghen | Alliance Systems Incorporated
[EMAIL PROTECTED] | [EMAIL PROTECTED]
http://www.mcs.net/~troy | http://www.alli.com
