RE: [vtcl-user] Separating GUI/Processing Code

2002-03-01 Thread Techentin, Robert W.
> -Original Message- > From: Kenneth Jacker [mailto:[EMAIL PROTECTED]] > > damon> The main and init procedures are there as guidelines, but you > damon> can replace them with any content you wish. I do exactly > damon> what you're talking about all the time. I put all of my GUI >

Re: [vtcl-user] Separating GUI/Processing Code

2002-02-22 Thread Jorge . Lehner
Hello Kenneth! On Fri, Feb 22, 2002 at 08:58:46AM -0500, Kenneth Jacker wrote: ... > When I opened the project, I got a "file 'applprocs.tcl' not found" > error message since I didn't start /vtcl/ from within the project I use a patched version of Vtcl, which identifies the project directory at

Re: [vtcl-user] Separating GUI/Processing Code

2002-02-22 Thread Christian_Gavin
| |Fax to: | | Subject: Re: [vtcl-user] Separating

Re: [vtcl-user] Separating GUI/Processing Code

2002-02-22 Thread Kenneth Jacker
Thanks Bob and Damon for your continuing help! Here was my first attempt at a revised /init/ proc within the standard /vtcl/ project file: proc {init} {argc argv} { uplevel #0 source applprocs.tcl } When I opened the project, I got a "file 'applprocs.tcl' not

RE: [vtcl-user] Separating GUI/Processing Code

2002-02-21 Thread Damon Courtney
> > You place the "source" command *within* the "init" proc? > > > > Seems like you'd do it outside of all proc bodies (like a > > "#include" in C/C++), otherwise the "scoping" would be weird, no? > > Yes, exactly. > > In C/C++, scoping is a compiler-per-file thing. You can hide functions f

Re: [vtcl-user] Separating GUI/Processing Code

2002-02-21 Thread Kenneth Jacker
damon> You should easily be able to separate the code. Good! damon> The main and init procedures are there as guidelines, but you damon> can replace them with any content you wish. I do exactly damon> what you're talking about all the time. I put all of my GUI damon> code into a fil

Re: [vtcl-user] Separating GUI/Processing Code

2002-02-20 Thread Damon Courtney
> First, thanks for all those that have contributed to /vtcl/ ... useful! > > How much of the source code in the /vtcl/-managed file is "sacred". > (I would guess that portions are assumed to always be there so that > changes can be merged in, etc.) > > For example, can I replace the current "ma

[vtcl-user] Separating GUI/Processing Code

2002-02-20 Thread Kenneth Jacker
First, thanks for all those that have contributed to /vtcl/ ... useful! How much of the source code in the /vtcl/-managed file is "sacred". (I would guess that portions are assumed to always be there so that changes can be merged in, etc.) For example, can I replace the current "main" proc with: