| Title: | DOCUMENT T1.0 |
| Notice: | **New notesfile (DOCUMENT.NOTE) now available (see note 897)** |
| Moderator: | CLOSET::ADLER |
| Created: | Mon Feb 09 1987 |
| Last Modified: | Thu Oct 31 1991 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 897 |
| Total number of notes: | 4397 |
I want to create a figure where two sixel graphics are printed right on
top of each other.
I appended two sixel files together, and between them I put an escape
sequence (<ESC>[30k) to cause a vertical shift on the page. When I
printed this file by itself everything was just like I wanted, the two
graphics were superimposed. When I called this file into Document the
two graphics were printed one above the other (the second one
overlapped the text that followed the figure).
Could someone 'in the know' give a thumbnail explaination of how
Document handles graphics that it calls in, and possibly suggest how I
might superimpose two images? I know that I can call the two figures
separately one right after the other in the .SDML file and give a very
small figurespace for the first to superimpose them, but I would rather
not do that.
Lance
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 741.1 | It's a change in environment | VAXUUM::DEVRIES | M.D. -- your Device Doctor | Tue Aug 04 1987 13:32 | 28 |
> I appended two sixel files together, and between them I put an escape
> sequence (<ESC>[30k) to cause a vertical shift on the page.
That sequence says "go back 30 size-units". Within a DOCUMENT file,
the size unit is set to "pixel" and position unit mode is enabled.
In the standalone context, the size unit is probably "character
cells". If you want to continue to use that command as is, you'll
have to play with select size unit (SSU) command (at least).
> Could someone 'in the know' give a thumbnail explaination of how
> Document handles graphics that it calls in
With LN03 files, the device converter reads the sixel file, throwing
away everything except SSU, until it finds the device control string
(DCS) for sixels. It passes along the SSU, if any, plus the DCS
as supplied, plus one graphic newline, and copies the rest of the file
without further inspection.
After the copy is complete, VAX DOCUMENT appends the terminator
(<ESC>\) and SSU to select the pixel as size-unit. And when that
is all done, it will put out absolute-positioning commands to move
to the place where the text formatter calculated the next text should
go. So if your graphic is deeper than you told <FIGURE_FILE> it
would be, the text may overwrite your graphic.
I hope this helps.
--Mark
| |||||
| 741.2 | Did the trick! | GNUVAX::LIBRARIAN | Looking at the big sky | Tue Aug 04 1987 17:28 | 10 |
Mark,
It did help (a lot). Rather than try and fool around with Size Units,
I just changed <ESC>[30k to <ESC>[850k to make up for the smaller
units. It came out just like I wanted. Thanks also for the brief
explaination of how it works.
Lance
| |||||