Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: gaula92 on October 06, 2011, 09:58:11 PM
-
Hello there
I'm sure some of you remember the killptr tsr that ran in some scene cracks back in the day: it hides the mouse pointer, but it only works in kS 1.x and 2.x systems.
I'm looking for a version/replacement/equivalent for KS 3.X systems. It must me a CLI program, just like killptr was.
Searched all over aminet, but I had no luck.
thanks in advance!
-
Hello there
I'm sure some of you remember the killptr tsr that ran in some scene cracks back in the day: it hides the mouse pointer, but it only works in kS 1.x and 2.x systems.
I'm looking for a version/replacement/equivalent for KS 3.X systems. It must me a CLI program, just like killptr was.
Searched all over aminet, but I had no luck.
thanks in advance!
Create an empty pointer in the pointer preferences tool and save the .prefs file under a name, eg, hiddenpointer.prefs.
Then use SYS:Prefs/Pointer <>/hiddenpointer.prefs USE in your CLI script or whatever.
That'll hide your pointer for you without opening the preferences GUI. Use a similar tactic to restore the one from ENVARC:Sys once you are done hiding it.
-
Wow, works! Thanks, Karlos!
Anyway, if you happen to know about a killptr replacement (i.e., a single commandline tool to do it), please tell me.
For now, Karlos's solution is what I will use :D
-
@Karlos: your solution DOES work but it doesn't totally fit my needs: it needs ipfrefs, wich is not in my minimal startup-sequence, and fails when executed from a shellscript (or creates a confirmation menu..)
Isn't there a simple killptr equivalent for 3.X?
-
@Karlos: your solution DOES work but it doesn't totally fit my needs: it needs ipfrefs, wich is not in my minimal startup-sequence, and fails when executed from a shellscript (or creates a confirmation menu..)
Isn't there a simple killptr equivalent for 3.X?
Dunno, never had a need for such a thing. I'm pretty sure you could write one easily enough though as there are graphics/intuition functions for setting the pointer's BitMap.