hi.

two bugs when using transparent pngs:

i wanted to try out the new feature of alpha channel support. so i
created a *simple* png picture with a transparent background.
when importing it into pagestream it it displayed "reversed" - means
the originally transparent parts are now visible and the visible parts
are actually transparent... funny. so i have a green box on the screen
with a transparent flower in it

and if i now output it to a postscript file the transparency is not
respected at all.

byebye...

--
Michael Merkel (MiMe@IRC)
Michael.Merkel@gmx.net
http://www.mirime.de/Michael

<Michael.Merkel@gmx.net> wrote at 22 Jun 2006 20:27:15 +0200
about <[PageStreamAmigaBeta] using alpha channel pngs>:

> hi.
>
> two bugs when using transparent pngs:
>
> i wanted to try out the new feature of alpha channel support. so i
> created a *simple* png picture with a transparent background.
> when importing it into pagestream it it displayed "reversed" - means
> the originally transparent parts are now visible and the visible parts
> are actually transparent... funny. so i have a green box on the screen
> with a transparent flower in it
>
> and if i now output it to a postscript file the transparency is not
> respected at all.

i tried another one and with that the screen display looks fine.
(http://de.wikipedia.org/wiki/BildNG_transparency_demonstration_1.png)

but postscript and pdf both don't work.

byebye...

--
Michael Merkel (MiMe@IRC)
Michael.Merkel@gmx.net
http://www.mirime.de/Michael

>hi.
>
>two bugs when using transparent pngs:
>
>i wanted to try out the new feature of alpha channel support. so i
>created a *simple* png picture with a transparent background.
>when importing it into pagestream it it displayed "reversed" - means
>the originally transparent parts are now visible and the visible parts
>are actually transparent... funny. so i have a green box on the screen
>with a transparent flower in it

I was just testing this, and it works fine for me. Obviously png must have
several methods of storing this information as someone else had a similar
problem on Windows. Can you send me a sample at dan@pagestream.org and I
can try it out here? If it doesn't work, I can get it in the bug queue.

>and if i now output it to a postscript file the transparency is not
>respected at all.
>
>byebye...
>
>--
>Michael Merkel (MiMe@IRC)
>Michael.Merkel@gmx.net
>http://www.mirime.de/Michael

We appreciate your business!

Dan Kilroy - Sales <sales@pagestream.org>

Grasshopper LLC
N5750 Langlade Price Road
Bryant WI 54418 USA
http://www.pagestream.org
PageStream DTP for Amiga, Linux, Macintosh, and Windows

Ok, here are some things not mentioned in the readme:

Initial piracy warning: Box at left is all gray
Prefs: Serious object layout errors (just like before):
- Selecting File/Preferences and then Type, causes a garbled layout. The
Conversion group and the Charset cyclegadget are displayed on top of the
Items lister. Resizing the window, all groups move around in wrong ways,
sometimes moving outside the right window border. Several other selections
in the Items list have similar layout problems. For example, the Toolbar
settings are wrong both because the listers can move out of the window to
the right, and because they do not grow vertically when the window is made
taller, making it very awkward to select among the many options.

Text and button labels: Text and images doesn't have gray background all of
the time now, but it often does, as mentioned in the readme.
Font substitution: Still does not work, just like before:
- The cyclegadget where a font to substitute with stays whatever I have
selected, regardless if I click on another font
(which I, perhaps, selected another font for). But it seems that only one
font will actually be substitued for what has been selected, the other ones
(I believe) are substituted with the first font in the font list.

Fonts: No fonts exist, not even the ones used in the demo.. unsure how to
install, it's a bit of a mystery how to get any fonts to display at all.
Main window scrolling: Causes garbage - but resizing seems to work (it's
slow, though).
Edit palette: No contents unless hidden/re-shown.
Edit palette: Top pixels filled with garbage when text tool selected.
Edit palette: Paragraph styles cannot be displayed in any way.

Good to see a new version, not that much of an improvement over the last one
though (but it looks prettier now that a good deal of the weird text
backgrounds are fixed .

--
/Johan Rönnblom

<johan@ronnblom.net> wrote at Wed, 12 Jul 2006 13:48:48 +0100
about <[PageStreamAmigaBeta] New MorphOS beta report>:

> Ok, here are some things not mentioned in the readme:

i'll add the stuff which differs or is the same using the os4 version (5pro)

> Initial piracy warning: Box at left is all gray

same here

> Prefs: Serious object layout errors (just like before):
> - Selecting File/Preferences and then Type, causes a garbled layout. The
> Conversion group and the Charset cyclegadget are displayed on top of the
> Items lister. Resizing the window, all groups move around in wrong ways,
> sometimes moving outside the right window border.

that one works ok here. but the window is only resizeable horizontally.

> Several other selections
> in the Items list have similar layout problems. For example, the Toolbar
> settings are wrong both because the listers can move out of the window to
> the right, and because they do not grow vertically when the window is made
> taller, making it very awkward to select among the many options.

also works ok here. but the window itself constantly resizes vertically when changing the lister entries. resulting in making some entries very hard to select.

> Text and button labels: Text and images doesn't have gray background all of
> the time now, but it often does, as mentioned in the readme.

yes. this works now ways better than ever before but still not perfect. some labels still behave wrong.

one thing about windows and requesters:
the "ok" and "cancel" buttons are misplaced. the amiga style is:
"ok" (or positive) is left and "cancel" (or negative) is right...

> Font substitution: Still does not work, just like before:
> - The cyclegadget where a font to substitute with stays whatever I have
> selected, regardless if I click on another font
> (which I, perhaps, selected another font for). But it seems that only one
> font will actually be substitued for what has been selected, the other ones
> (I believe) are substituted with the first font in the font list.

the font substitution window on os4 works (almost) perfect.
the "remember" checkbox does sometimes not show it's current state correctly when defining one substitution and then going to the next one.

the substitution window does not show the target fonts inside the list - only in the cycle. please add this. also the "convert/display as"and "remember" state. this should all be part of the listview.

> Fonts: No fonts exist, not even the ones used in the demo.. unsure how to
> install, it's a bit of a mystery how to get any fonts to display at all.

? using the menu "file -> system preferences -> fonts" you can add your font path (e.g. sys:fonts/_truetype/)...

but there is one bug left:
all font pathes show up twice afer restarting... one with a trailing "/" and one without...

> Main window scrolling: Causes garbage - but resizing seems to work (it's
> slow, though).

same here! scrolling using the scroolbars or the middle mouse button still produces garbage.
when resizing slowly i sometimes get a black window.

> Edit palette: No contents unless hidden/re-shown.

seems ok here.

> Edit palette: Top pixels filled with garbage when text tool selected.

don't see it here.

> Edit palette: Paragraph styles cannot be displayed in any way.

work ok here selecting the "P"aragraph symbol i get the paragraph edit toolbox.

> Good to see a new version, not that much of an improvement over the last one
> though (but it looks prettier now that a good deal of the weird text
> backgrounds are fixed .

absolutely! almost usable.
i was a little bit disappointed about the fey improvements of the amiga version(s) but well, actually it is not so much left.

it seems that some problems seem to be system specific although at the first glance they just sound like gui problems...

one big thing left:
postscript output does *not* include fonts currently which makes it unuseable to me. don't know if this is mentioned in the readme.

byebye...

--
Michael Merkel (MiMe@IRC)
Michael.Merkel@gmx.net
http://www.mirime.de/Michael