Hello everyone.
There is a wee bit of snow up here, not enough to lock the town up
tight, but enough to make me say "hey, lets play on the computer".
I've been refining my job queue code - I still have to work out the
kinks in the 'parameterized command' code, and there is an assignment to
dirNameForExecute within the execute code I have to remove.
I have eliminated the flag 'isBuilding' by adding a job flag
jobIsBuilding. This is working fine, though I want to keep the output
of the first job on the screen when the second job runs. The
SciTEBase::Execute() method clears the output pane between, so I'm
trying to find an optimum solution.
However that is not the point of this email. I think the 'isBuilt' flag
needs to be looked at a little. The flag is only used when the GO
command does not need to rebuild the file. I'm using the example of a
.c file. I understand this flag, however there is a problem if there
are two .c files open at the same time.
Using GO on the first sets a global flag so that when you select the
other buffer and use GO, it is not (re)built and either fails because
the EXE does not exist, or runs the outdated EXE.
I'd like to remove the flag and replace it with a query against the
buffer IsDirty flag, but the existing implementation, when a file is
loaded, builds before the first GO, even though the buffer is not
dirty. Most times the 'isBuilt' flag and 'IsDirty' flag are opposite of
each other except when the buffer is first loaded
Maybe instead of a boolean flag a tri-value flag?
Any suggestions, including that I'm wasting a lot of time of a trivial
issue, is welcome.
April
--
I'm not from outer space, I only work there.
Star Trek
_______________________________________________
Scite-interest mailing list
Scite-interest@lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest
