On 07-Jun-00, Lamee Wouter wrote:
> That's a really major major major major - did I say major? - bummer: I'm
> used to 1280x1024 in 16 bits or higher on my 21" screen. Anyway, I'll
> give the 68000 version a go, and check the MUI toolbar settings.
I can't vouch for stability on graphics cards. All I know is that with AGA
DBL scan modes it was really unstable. Try just changing to the 68000
version first and see if that makes a difference. The problems I had with
DBL Pal and Super 72 may have been low chipmem related.
The toolbar seems to be unable to load the button images. It sounds like
your setting may already be for Text Only as it causes a crash on startup.
Hopefully this will be ironed out in the next update.
>
> Ouch, that sort of removes the purpose of having the WYSIWYG window
> then. If I wanted to edit source directly, I would not have bought
> MetalWeb.
>
Yes well thats true. However it is shareware and if no one bought it the
authors would be unlikely to go on improving it. Given that it seems to be
the only real WYSIWYG package in development for the Amiga at the moment
I'm quite happy to support it.
Even worse, if I change the source code in a two-frame page from "12%,88%"
to something like "100, *" (100 pixels for the first frame and the
remainder for the other frame) and then load and save it in MetalWeb, it
will have changed the values back to percentages again. This means that
whatever I make in MetalWeb, there is a point where I have to make manual
changes. If I want to make another change using MetalWeb, I have to apply
all these
manual changes again.
>
The next update promises an advanced mode to stop MetalWeb trying to
autocorrect your code. This was requested by a few people on the list.
>
> I sure hope so. Thanks for the 68000/MUI tip, I'll give it a try.
>
>
> W.
>
Regards
Mike
