AmigaGuide/Multiview questions

So, i'm trying to pretty up my AmigaGuide and am stuck when it comes to place some options inside the Guide.

First a general question:
Is it possible to display pictures beside the text (without opening an extra window), e.g. a logo on top of the text (maybe even user placable)?

All of those options are taken out of the AutoDoc amigaguide_dtc.doc

1)
@{<label> <command>}
Indicate a textual link point. Can be anywhere in a line.
Starting with 3.0, AmigaGuide can can link to graphics,
sounds, animations and other DataTypes.

I tried something simple
@{"Text" "AppDir:Multiviewer text"}
with "text" being a file in the same directory as the Guide.
Then i tried it without the AppDir part, as the description indicates that a destination file is going to be handled by datatypes, but still nothing.

What am i doing wrong?

2)
@{AMIGAGUIDE}
Displays the word AmigaGuide in bold followed by the ® symbol.
New for V40.

I have yet to find the exact place where it displays that.
I placed it inside the main node but it never comes up.

3)
The whole PEN options and Background/Foreground.
They don't seem to do anything, or maybe i haven't understand the format of those options.

What would be the exact format to e.g. use @{BPEN}?

4) @HEIGHT <chars>
How high, in characters, the largest document is.
and
@WIDTH <chars>
How wide, in characters, the largest document is.

What is meant here?
How big the font used is or how many characters are there in the doc?
Why would that be important, given we have word wrapping available?

Thank you

@Raziel

Go HTML you'll never look back

Quote:

No, inlline display of anything is impossible, see above .

Quote:

Why are you specifying an app? Unless for some reason you want to load the multiview binary in with the binary datatype

Try

@{"Text" "PATH:To:my:textfile.txt"}

Quote:

Don't know, seams abit pointless any way.

Quote:

Really not sure either, I would say avoid it anyway, let the use define these via the system prefs, in case they have eyesight based needs, or like pink and purple or whatever....

Quote:

Perhaps to ensure a minimum window size?

As a general guideline for amigaguides, don't try and pretty it up, don't spevify fonts, don't specify colours.

Do use the dedicated colours, like text, shine etc but only sparingly. Use bold for heading perhaps.

Amigaguide is not supposed to be pretty it's supposed to be readable.

@broadblues

Thank you for the answers.

Quote:

Because the AutoDoc is pretty scarce on information or examples, so i had to try my way through the usage.

I have now changed it to

@{"AUTHORS" Path:to/AUTHORS"}

Nothing...
I don't believe the datatypes need a suffix to work, does it?

@Raziel

Try @{amigaguide}
The lower case seems to work. Maybe other uppercase commands in the autodoc need to actually be lower case too.

An example amigaguide I have uses @{"Amiga" link amiga.brush/main} to display an image on a seperate page. The amiga.brush file is an IFF image file in the same directory as the example amigaguide. It doesn't work without the /main after the filename. I edited the command to link to a text file and that worked too.

@xenic

The "link" and "/main" did the trick, thanks a bunch, also it doesn't like " in it's path.
But there is no info whatsoever given about that "link" part and the "/main" part either. AutoDocs are outdated :-/


I have a request though, since i think i found a bug in Multiviewer.
If you got Multiviewer, could you check if it crashes for you too, please?

Open up your guide with Multiviewer (changed to load a text file, it should display in the same incarnation of Multiviewer the guide was openend in).

Now close Multiviewer while still displaying the external file.

It crashes for me, but not when using multiview, only with Multiviewer.

@broadblues

Multiviewer


Multiviewer.debug