P96 3.0.0 (and later) news and support

[hexaae]

Originally Posted by Thomas Richter

What's the problem with the mouse blanker commodity that comes with the Os? It uses the above code and works fine.

It doesn't work here... Mouse pointer never disappears on keypresses or waiting 30secs+. Should I do something special under WinUAE and uaegfx monitor?

Here are my TTypes for uaegfx:
(BorderBlank=System)
(MemoryClock=0)
(Quiet)
BigSprite=NO
BoardType=uaegfx
DisplayChain=Yes
FakeNativeModes=NO
FontsFix=NO
GrantDirectAccess=NO
IgnoreMask=NO
NoBlitter=NO
NoPlanar2ChunkyBlits=NO
OverClock=NO
SettingsFile=SYS:Devs/Picasso96Settings
SoftSprite=NO
System2ScreenBlits=NO

[Thomas Richter]

The version number of the commodity is helpful. Simply because the latest version is fine.

[tomcat666]

Thomas, I have also removed the Generic and PAL monitors from DEVS:Monitors, so only Native and PiGFX monitors are left. No difference. I think the Native monitor is the one that comes with P96 installation. Everything should match, but for some reason i cannot get the P96ScreenCX to work. Any help would be appretiated.

[Thomas Richter]

Please try to remove the brackets around the (MONITORS=DEVS:Monitors) tooltype and put it first in the tool types list. Apparently, it takes the "DONOTWAIT" argument as directory name (sigh).

[hexaae]

Originally Posted by Thomas Richter

The version number of the commodity is helpful. Simply because the latest version is fine.

Kickstart 47.96, Workbench 47.2 (10-Apr-2021)
5.OS32:> version FILE FULL OS32:Tools/Commodities/MouseBlanker  
mouseblanker 47.4 (31-Ago-2020)

[Thomas Richter]

This then goes to the Os team, not to P96. Apparently, there is a bug in the mouse blanker, it should not set the Viewport argument to NULL in which case it only blanks the mouse on the first viewport in the view chain, but it rather should transmit the viewport of the frontmost screen as such:

#define BlankMouse()   ChangeSprite(IntuitionBase->FirstScreen?(&IntuitionBase->FirstScreen->ViewPort):NULL,&blankMouse,(APTR)blankData);

but that is really beyond P96 possibilities to fix.

[tomcat666]

Originally Posted by Thomas Richter

Please try to remove the brackets around the (MONITORS=DEVS:Monitors) tooltype and put it first in the tool types list. Apparently, it takes the "DONOTWAIT" argument as directory name (sigh).

I did, both MONITORS and then also CX_PRIORITY... nothing happens. If I run the util from Workbench there is nothing happening in SnoopDOS (nothing happens in snoopdos), if I run it from CLI I always get the same output in Snoopdos as you see in the previous screenshot, just the list of the tooltypes.

[Thomas Richter]

If your monitor icons - the ones that are loaded on startup - are stored elsewhere, you need to adjust the path, obviously.

[tomcat666]

Originally Posted by Thomas Richter

If your monitor icons are stored elsewhere, you need to adjust the path, obviously.

They are not, they are in the standard DEVS:Monitors directory. I have the Native monitor and the PiGFX monitor :

[Thomas Richter]

The snoopdos output does not show what directory it is actually looking. I would need a more complete output then.

[tomcat666]

Originally Posted by Thomas Richter

The snoopdos output does not show what directory it is actually looking. I would need a more complete output then.

How would I get that ? I enabled all Functions in SnoopDOS, the same output. If I run the utility with the CLI and use the MONITORS=DEVS:Monitors all I get is this:

[Amiga68k]

It's in WBStartup/DONTSTART?

[tomcat666]

Originally Posted by Amiga68k

It's in WBStartup/DONTSTART?

I tried different locations, with and without the .icon file. Always the same result.
If I run it from the WB with double click on icon then snoopdos doesnt show ANY output.
If I run it from CLI, with the icon in same directory, without the icon, with the MONITORS=DEVS:Monitors command line option or without I always get the same snoop dos output as shown here.

I am running OS 3.2 btw.

[Thomas Richter]

You apparently enabled "show only fails", which is not helpful. You should also check whether "DISPLAYCHAIN=NO" is set in the monitor tool type you want to switch.

[Amiga68k]

Thomas, if it doesn't show anything in SnoopDos when starting from WB, might it be impacted the same way SnoopDos was impacted one version ago?

[Thomas Richter]

What doesn't show anything? P96ScreenCx never shows anything. Please remove brackets around the MONITORS=DEVS:Monitors tooltype and move that tooltype frontmost. Otherwise, this source and the snoopdos source are not related at all.

[Amiga68k]

No, not related ofcourse, but if P96ScreenCx is started from CLI there is some output seen in SnoopDos. When starting P96ScreenCx from WB, nothing is seen in SnoopDos... which makes me think it simply doesn't start, the same way SnoopDos didn't start from WB one version ago.

Would have expected more reports if that would be the case though, but just checking.

[tomcat666]

I am so sorry, did not see that I have "Show only Fails" enabled. Haven't used snoopdos in years..

Anyway, here is the output when starting from the CLI:



Everything looks OK, but the utility is still not working... When I go to either edge of the rtg/native screen nothing happens.

And here is the output when starting from WB:



I have removed brackets around MONITORS and it is the top most tool type in this case :



For some reason it is still trying to load the monitors from the same directory in which the utility is...

Also the DISPLAYCHAIN=No is enabled for the PiGFX monitor:

[Thomas Richter]

But there is another screen open on another monitor, right? And the Pi is not in the display chain, right? It does not make sense if there is only one monitor, and only one screen open.

[tomcat666]

Yes, there is IMP running on the native screen on the left and normal RTG workbench on the Pi RTG screen on the right (has the DISPLAYCHAIN=No set). It is the same if I start the utility before I start IMP (or anything else native) or after I start it...