The Meaning of Life, the Universe, and Everything.
Location:
NY
Join Date:
8/25/2012
Posts:
49
Member Details
Every fourth or fifth launch of the Java launcher, the launcher will start my default browser and start a download of Minecraft.dmg (I do not use the native Mac OSX launcher; it's ugly and clumsy.) How can I stop the Java launcher from doing this? It's annoying and, for me, inappropriate for how I use Minecraft.
The Meaning of Life, the Universe, and Everything.
Location:
NY
Join Date:
8/25/2012
Posts:
49
Member Details
Inappropriate for me; I wrap the client launcher with some custom code. I cannot do this with the "new launcher." (Yes, I realize the "new launcher" is just "the launcher" and I'm using the "old launcher.") Other than this technical hurdle, I find the new launcher aesthetically unappealing. Sure, the old launcher is no beauty but it doesn't have that gimmicky look.
I suppose I could rework my custom stuff to wrap ~/Library/Application Support/minecraft/launcher.jar and just "get over it," RE: the new launcher's UX. As you said, ... I'll have to [use it] at some point in the future ...
Still, regarding my initial question: I find it annoying and "bad form" when one application automatically launches another w/o warning or consent. This is also a (minor but present) security risk. At this point, I'd rather put investigative and coding effort into stopping the launcher from kicking off a browser than rewriting my wrapper code to work with launcher.jar --- Sounds petulant, I know, but my brain won't let me look yet again at my wrapper code for a good while.
Every fourth or fifth launch of the Java launcher, the launcher will start my default browser and start a download of Minecraft.dmg (I do not use the native Mac OSX launcher; it's ugly and clumsy.) How can I stop the Java launcher from doing this? It's annoying and, for me, inappropriate for how I use Minecraft.
Thanks.
Inappropriate for me; I wrap the client launcher with some custom code. I cannot do this with the "new launcher." (Yes, I realize the "new launcher" is just "the launcher" and I'm using the "old launcher.") Other than this technical hurdle, I find the new launcher aesthetically unappealing. Sure, the old launcher is no beauty but it doesn't have that gimmicky look.
I suppose I could rework my custom stuff to wrap ~/Library/Application Support/minecraft/launcher.jar and just "get over it," RE: the new launcher's UX. As you said, ... I'll have to [use it] at some point in the future ...
Still, regarding my initial question: I find it annoying and "bad form" when one application automatically launches another w/o warning or consent. This is also a (minor but present) security risk. At this point, I'd rather put investigative and coding effort into stopping the launcher from kicking off a browser than rewriting my wrapper code to work with launcher.jar --- Sounds petulant, I know, but my brain won't let me look yet again at my wrapper code for a good while.