Hi,

I have a problem with PageStream 4.1.5.6 when X-Dock is running... the sreen is unreadable.

http://pages.infinit.net/pgx/PageStream_Without_X-Dock.jpg

http://pages.infinit.net/pgx/PageStream_With_X-Dock.jpg

Is there a way to fix that?

Thank you.

@Pierre55

Is PageStreamer available somewhere to reproduce this problem ?

Thanks

_________________
http://apps.amistore.net/zTools

@zzd10h


You can have a demo of version 5.x but can't say if that version have the same problem.

http://www.pagestream.org/

PageStream not PageStreamer!

Bye!

@Pierre55

Probably the easiest way is to run pagestream on a custom screen.

If you use screens prefs you can also set up a custom gui prefs file which is basically the same as OS3.x and tell it to load that for your pagestream screen.

To create the 3.x gui file, open gui prefs, reset to defaults (ramiga-d) and saveas (ramiga-a). I'd save it as sys:prefs/presets/GUI-OS3.prefs


If you get any old software that doesn't look right with OS4 try the screens prefs trick.

_________________
OS4 Rocks
X1000 beta tester, Sam440 Flex (733)

Visit the Official OS4 Support Site for more help.

It may be that your sole purpose is to serve as a warning to others.

Quote:

Nonsense. Amiga is GREAT at multitasking *IF* the user uses the Amiga feature known as "multiple screens". I can quickly & easily switch between my web browser, news reader, email, Workbench, etc by cycling through them (or if really necessary, right-clicking the depth gadget to get a list of screens).

I'm a big fan of the depth to front commodity that enables much easier depeth arranging of windows by right clicking on the window or screen depth gadget.

Quote:

however using them on AmigaOS4 is not easy as it ought to be, because you have to manually create named public screens first, and then they look ugly unless you manually set them to use a duplicate of your GUI prefs file (and set it to duplicate Workbench screen settings, etc).

Errm there's a Like Workbench drop down chooser in the GUI presf and Palette prefs tab. So setting up a screen that look like the workbench is trivial.

Quote:

Still, once you've worked out how to do it once, it's fairly easy to do it for further public screens.

Yes it will be wont it

Quote:

Maybe you could create a new Sys:Prefs/Screens program that makes it trivial to set-up new public screens with the same settings as your Workbench screen?

See above

Quote:

And perhaps a system patch that automagically does this when a program tries to use a named public screen that doesn't exist? (The patch could possible open a requester asking if it should create a new public screen of the given name.)

Eeek no! The point of screen prefs is that it automatically promotes / opens / setups pre exiting named screens and leaves other alone.


Quote:

As a kludgey alternative, some kind of patch to give a special "Like Workbench" screenmode (with a fixed modeid), so that any programs which support creating their own screen can get one like Workbench. I imagine the patch would automagically add SA_LikeWorkbench to any such screens that were opened.

It's relatively trivial to open a screen that's lile the workbench already just use SA_LikeWorkbench so a special like workbench mode is hardly needed

You can also set the defaults in the screen so that they will be inherited by old programs, this is not always good some don;t like the OS4 window layout and end up glitching.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@Trixie
Quote:

Looks like the already reported "infowindow crashes when no background texture is set in system GUI prefs" bug. I tried to isolate the problem by no luck so far.

There are numerous texture settings in GUI prefs. Can you tell me specifically which texture setting you are referring to?? (Tab & title)

_________________
X1000 with 2GB memory & OS4.1FE

@XyPsy

Quote:

1. Adding .LRC files datatype (for playing downloadable mp3 lyrics in mutiviewer)

Not really sure how that would work in a datatype context and lrc file is just text.

Quote:

2. A new TuneNet plugin that play LRC lyrics as an animated scroller text in Workbench backdrop (maybe it is time for a new interactive CANDI)? this could make OS 4.1 more desirable for nostalgic demosceners and retro fans who like watching classic A500 intros with sine scroller text on a reflecting surface.

I don't think messing with the workbench backdrop is good idea, we already have one horrid hack doing this (CANDI) we don't need another.... lyrics could be displayed in a ringhio notification though perhaps, or scroll in the skinned / Reaction GUI.


To be quite honest, scrolling lyrics is pain, as someone who might want to read lyrics whilst learning a song I want to read ahead , reread what was just sung etc etc....

Quote:

3. New interactive CANDI with classic Amiga demos effects like 3D starfield pixels, plasma effects, mandelbrot fractals zooming, etc...How about a boing ball interactive backdrop (or other 3D geometric) that bounce & dance in harmony with MP3 music?

Sounds like you want a CANDI based scope for TuneNet, TuneNet already supports scopes so all that would be needed is for CANDI to listen to the tunenet scope plugin API, but bear in mind that runs at 25Hz / 50Hz I don't think candi runs at anywhere near that kind of frame rate except on the fastest HDRadeon cards.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

Quote:

Quote: Quote: But it does not make clear which components are replacements of existing components Yes if it finds an existing version (either old Hyperion version or previous release Enhancer Software version), it warns user and they can Skip or Proceed.

I think ChrisH's point is that it doesn't specifically highlight replacements of OS components, the most important being SFS2 Format and the diskcache kickstart component.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

Quote:

(And yes, I realise there's the possibility of Enhancer Software's replacement components not working well with a future OS4 update, simply because they haven't been tested with such an update before release. I'm not sure what the solution is there, apart from dealing with any such problem if it arises.)

There is some overlap between testers and devs so that isn't that likely to be an issue.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@broadblues

Quote:

I'm a big fan of the depth to front commodity that enables much easier depeth arranging of windows by right clicking on the window or screen depth gadget.

Depth2front is nice commodity, but some way to distinguish between WB Windows and applications would help in cluttered WB.

@Severin
Quote:

Probably the easiest way is to run pagestream on a custom screen.

Personally, I used Pagestream on it's own screen and it would probably be an effective workaround for the X-Dock bug that Pierre55 has reported. However, the best solution is to fix X-Dock (and any other Enhancer bugs) and release an Enhancer bug-fix update as soon as possible.

_________________
X1000 with 2GB memory & OS4.1FE

@Pierre
No sorry, impossible to download the demo

http://www.pagestream.org/?action=Downloads&showid=327

"It has just been over a week since the last release, but I did get a few bugs with the font selector and lists in general and a few other minor pains. Just trying to make it easier to test for those folks who can fire it up.

To download this file, you must be a registered owner of this product and be signed in to your account.
Otherwise, you may purchase this product to download it."


Is somebody have the demo and send me it, please ?

_________________
http://apps.amistore.net/zTools

@Trixie

Quote:

And I understand this is without the background texture set for gadgets in the GUI prefs? That would be very reassuring - my hair's begun to turn grey because I can't spot where the bug is

The bug was triggered by subclassing window.class which is why it affected DiskImageGUI as well as InfoWindow.class. As broadblues said it should be fixed in the latest beta version of window.class.

@xenic
Quote:

However, the best solution is to fix X-Dock (and any other Enhancer bugs) and release an Enhancer bug-fix update as soon as possible.

Of course that's the best solution, but the workaround will do until the bug is fixed.

Edit: I've tried pagestream 4.1.5.6 on workbench with x-dock running and I don't see the error.

Last edited by Severin on 02-Sep-2016 at 06:29 PM.

_________________
OS4 Rocks
X1000 beta tester, Sam440 Flex (733)

Visit the Official OS4 Support Site for more help.

It may be that your sole purpose is to serve as a warning to others.

@pavlor

Quote:

Depth2front is nice commodity, but some way to distinguish between WB Windows and applications would help in cluttered WB.

That's what AppManager or Exchanger is for. Hmm, Exchanger doesn't seem to support the "Window to front" functionality of AppManager/application.library - can that be added @amigakit?

Of course it only helps if the program in question has registered with (preferably) application.library or (at a pinch) commodities.library.

@zzd10h

I don't know where that link came from, but there aren't any Amiga demos of Pagestream, even when logged in.

You can see and download all the available demos whilst logged out.

Last edited by Chris_Y on 02-Sep-2016 at 06:40 PM.
Last edited by Chris_Y on 02-Sep-2016 at 06:36 PM.

_________________
"Miracles we do at once, the impossible takes a little longer" - AJS on Hyperion
Avatar is Tabitha by Eric W Schwartz

@Chris_Y

Maybe opposite approach would be easier: identify WB windows (eg. by some sign). I like that I can use depth2front for all windows on WB (both applications and WB windows).

@Pavlor

Yes I agree a W: before workbench windows or some similar visual sign might be useful, though to be honest as the window titles are clearly given it isn'y that hard to tell.

@Chris_Y

Starting another app like exchanger just to depth arrange windows is a bit ermm Windows like

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

I've just been testing the new Enhancer sound datatype and found some serious flaws. When the SDTA_SignalTask & SDTA_SignalBitMask tags are used for datatype sound play, the new sound datatype never sends the signal when the sound is finished playing. So far I've found that this affects OS4 Dopus4 internal sound play, sound notification by my usbsound commodity at OS4Depot, Jabberwocky and some minor datatype based sound players. The programs wait for the sound datatype signal but never return because the signal is never received.

OS4 sound datatype plays mono sounds through both speakers but the new Enhancer sound datatype only plays mono sounds through the left speaker.

The new sound datatype is therefore NOT backward compatable with the current OS4 sound datatype.

_________________
X1000 with 2GB memory & OS4.1FE

@Xenic

Quote:

the new sound datatype never sends the signal when the sound is finished playing

Hmm, curious. It should be sending the signal - it's definitely wired up to do so. I'll investigate.

Quote:

OS4 sound datatype plays mono sounds through both speakers but the new Enhancer sound datatype only plays mono sounds through the left speaker

Yep, it does, primarily because of the multi-channel support and the default being 1 channel with a channel mask/layout of left speaker only. It's not too difficult to force a pan or upmix to 2+ channels but that's highly inconvenient if you are explicitly targeting only the front left channel. In a 3.1, 5.1 or 7.1 set up you would typically expect a mono sample to play through the front centre speaker and not to the front left and front right (because that makes it stereo and we already know it's not stereo!) This leads directly into decisions about how and when to upmix both mono and stereo (play to centre, mix to centre, mix to surround, mix to rear, straight reproduction of left/right on surround left/right etc.) not to mention the reversal of these for downmixing and/or headphone use. All of these issues are on the "phase 2" list with a TON of other features to at least be looked at if not addressed in some fashion, so please bear with us :)

Quote:

The new sound datatype is therefore NOT backward compatable

Respectfully, I disagree - although I suspect it may depend on what you define "compatible" to mean. The new dtc is compatible as applications and older subclasses of sound datatypes may work unaffected through the same API. It's the behaviour that's different but that's because the original datatype presumed either one or two speakers, which was fine 25+ years ago when it was imagined on the classic hardware. Things are somewhat different today.

My personal opinion is that there's a larger discussion to be had one the state of AHI and the audio subsystem as a whole with respect to modern expectations, but that's not for this thread. I'll check the bug you reported as it shouldn't be a huge deal to fix because the logic is already there.

Last edited by Drule on 02-Sep-2016 at 10:42 PM.

_________________
Karma: Positive

@Drule
Quote:

Hmm, curious. It should be sending the signal - it's definitely wired up to do so. I'll investigate.

Both of the issues I mentioned existed in OS3 sound datatype but were fixed for OS3.5/9 and OS4. The new version may be wired to send the signal but my programs aren't receiving the "requested" signal bit. A problem with the signal bit was mentioned in the OS3 Dev CD and in OS4 SDK:Include/include_h/datatypes/soundclass.h under SDTA_SignalTask. That may not be the problem but it might be worth looking at the OS4 include file if you can't locate the problem.

Quote:

Yep, it does, primarily because of the multi-channel support and the default being 1 channel with a channel mask/layout of left speaker only.

Personally, I can't imagine why anyone would invest in a complete surround sound system for a computer when most available music is stereo and it's easy to copy music to a flash drive an plug it into a modern surroundsound receiver. However, it certainly can't hurt to add that capability. An environmental variable to determine how for mono samples are played might be a good idea (center, left, right or all 3).

Quote:

Respectfully, I disagree - although I suspect it may depend on what you define "compatible" to mean.

By backward compatable I mean that OS4 programs written in compliance with the OS4 autodocs and includes should continue to work properly with the new sound datatype.

EDIT: I've reverted to the OS4 sound datatype for now. Do I need to remove the mod.datatype, mpega.datatype, & wav.datatype included with Enhancer or will they also work with the OS4 sound datatype??

Last edited by Xenic on 03-Sep-2016 at 12:17 AM.

_________________
X1000 with 2GB memory & OS4.1FE