If working as expected, with two screensavers, either on should activate in the shortest timeout set.
Both on set to the same time should always activate at that time.
This isn't how pupX and SSC work together. They're incompatible.
pupX and SSC are incompatible screensavers
Moderator: Forum moderators
-
bigpup
- Moderator
- Posts: 7517
- Joined: Tue Jul 14, 2020 11:19 pm
- Location: Earth, South Eastern U.S.
- Has thanked: 1022 times
- Been thanked: 1682 times
Re: pupX and SSC are incompatible screensavers
Depends on the Puppy version and what version of the programs are being used.
Use only the SSC GUI to do any setting changes and it will give the best results.
Mainly because the PupX set properties of X one is only effective for this specific boot.
It has to be re-setup on next boot.
Settings are not saved.
Both of these are doing the same thing.
They are two different GUI to set the X screen saver.
The last one used is what made the settings that will be used.
The SSC GUI gives you a little better control.
What you do with one should make the same settings show in the other for screen saver only.
Key word should.
If properly setup and installed in the Puppy version they will.
The version of the two programs does affect this.
There have been some bug fixes.
In Fossapup64 9.5
What I do with The SSC GUI shows up in the PupX set properties of X.
What I do with PupX set properties of X shows up in SSC GuI.
The SSC GUI is suppose to make settings that will still be in affect on reboot. (if you save on shutdown)
It puts a exec script in startup that should activate the settings when computer boots.
PupX set properties of X settings are lost on computer shutdown and have to be redone on boot up.
Note:
If you make settings using the SSC GUI.
This SSC startup script is in startup and it's settings will be shown in the PupX set properties of X on reboot.
SSC GUI also is suppose to make DPMS settings that will work with a monitor that has DPMS (Display Power Management Signaling) active.
However, xset can't override the settings set with my monitor's on-screen display.
This depends on the hardware (monitor and graphics card)
Really, this is all a very basic low tech screen saver. So do not expect it to do much.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected 
-
JASpup
- Posts: 1653
- Joined: Sun Oct 04, 2020 10:52 am
- Location: U.S.A.
- Has thanked: 70 times
- Been thanked: 89 times
Re: pupX and SSC are incompatible screensavers
bigpup wrote: Mon Oct 25, 2021 3:00 amUse only the SSC GUI to do any setting changes and it will give the best results.
I've noticed. My comments are less of an adjust to it understanding and more of a duh moment for future consideration, presuming creators aren't working in silos.
Both of these are doing the same thing.
They are two different GUI to set the X screen saver.
The last one used is what made the settings that will be used.
I noticed this too, except that sometimes the last setting might not trigger.
The SSC GUI gives you a little better control.
In any scale scenario, if 5-minute intervals are insufficient you'd revert to seconds even though you only need minutes, but as you just noted the seconds tool doesn't work as well in newer pups.
In Fossapup64 9.5
What I do with The SSC GUI shows up in the PupX set properties of X.
What I do with PupX set properties of X shows up in SSC GuI.
I just posted about my 64 Fossa experience: http://forum.puppylinux.com/viewtopic.p ... 038#p40038
Really, this is all a very basic low tech screen saver. So do not expect it to do much.
This isn't gymnastics but basic functioning. I would guess it too boring for developers who like challenges.
On the Whiz-Neophyte Bridge
Linux Über Alles
Disclaimer: You may not be reading my words as posted.