The Dink Network

Reply to Re: Martridge - The DMOD Wizard

If you don't have an account, just leave the password field blank.
Username:
Password:
Subject:
Antispam: Enter Dink Smallwood's last name (surname) below.
Formatting: :) :( ;( :P ;) :D >( : :s :O evil cat blood
Bold font Italic font hyperlink Code tags
Message:
 
 
April 22nd, 04:18 AM
peasantmb.gif
yeoldetoast
Peasant They/Them Australia
LOOK UPON MY DEFORMED FACE! 
I would just go for typical install/mod paths on Windows such as program files (x86) as well as AppData and $HOME/dmods, and search for freedink/yeoldedink.exe while it's doing that and never touch the registry were it me. On GNU/Linux it would be simple enough to test $PATH, and then search for an AppImage locally. I'd also be interested in seeing if symlinks work for launching mods with 1.08 that are installed outside of where it's hard-coded to look.

Another feature request would be categories perhaps by path, as lumping everything together is a leftover from <=1.08 releases which were path-locked. I've always thought it was really dumb to have stuff like dev files and Skeleton B alongside finished products in the same list with no way around it.

Also I will reiterate my suggestion for implementing command-line params per engine variant. Of course I know which boxes to select , however for the average user it's basically guesswork, and the tooltips say something like "may be good for some engines" which is too vague to assist, and may mislead them into thinking RTDink has a 1.07 mode or 8-bit support, not that it really needs a frontend to begin with.

As an aside, I may stop making AppImages altogether soon due to the libfuse2 conspiracy that seems to be plaguing Ubuntu and perhaps other distros, depending on how serious it is.