Subject:
|
Re: Program Interfacing
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Tue, 1 Oct 2002 02:09:43 GMT
|
Viewed:
|
700 times
|
| |
|
|
In lugnet.cad.dev, Orion Pobursky wrote:
> Can someone give me the quick and dirty lowdown on how to interface a file
> editor to L3Lab? (e.g. how LDAO and LDDesignPad do it)
You should grab the LDAO source code, it's all handled in one class
file. Of course, it's overcomplicated (I never do anything simply).
What I did in LDAO was to write the DAT code to a temporary file, then
write another temporary LDR/DAT file that referenced the the first
temporary file. This two-file approach allows LDAO to control various
rendering options by writing high-level control information (like 'main
color' and scaling) to the second file.
After the files are created, LDAO launches copy of L3Lab, with the path
to the second temp file on the command line (actually, in the command
parameters). This exec call also includes the command flags needed to
tell L3Lab to (a) watch the temp file, and redraw when it's updated (aka
'polling mode') and (b) not cache subfiles (so when the 1st temp file is
redrawn. Sorry, I don't remember what those flags are right now. It
should all be in the source code.
Steve
|
|
Message is in Reply To:
 | | Program Interfacing
|
| Can someone give me the quick and dirty lowdown on how to interface a file editor to L3Lab? (e.g. how LDAO and LDDesignPad do it) -Orion (22 years ago, 28-Sep-02, to lugnet.cad.dev)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
