AutoRun LWMenu
Re: AutoRun LWMenu
That's cool. Fantastic.
Re: AutoRun LWMenu
Thanks! In that case, I've released a couple of other features, if you like to check the latest beta.
- The first feature I'm not sure you can check since it seems you're always admin anyway. It lets you relaunch admin-only buttons as admin, if you tried to click them not as admin (i.e. buttons involving netaccess and symlinks).
- The second feature is the new command line parameters /skiptobutton=X (e.g. /skiptobutton=5) and /?, so you can make one central menu with all buttons, but each time call a different one. If there are more options you like to see as command line parameters, now's your chance. Although remember file extension associations don't support command line parameters anyway, so it's not for one of your favorite use cases.
Last edited by lwc on Fri Apr 19, 2024 12:03 pm, edited 1 time in total.
Re: AutoRun LWMenu
You can give an example of an inf file in which the function "/skiptobutton=X" is written. I couldn't figure it out.
Re: AutoRun LWMenu
No, inf files already had the ability to have:
The new feature is that your launcher's shortcut can now run launcher.exe /skiptobutton=X (or launcher.exe /skiptobutton=X "path-to-folder-with-INF") which will be used even if the INF has something else.
So imagine you can have just 1 single INF file, but 10 shortcuts, saving you the trouble of having to create and maintain 10 INF files. It doesn't replace anything, just adds an alternate way to skip to buttons.
Internally I use it when you try to click a button that requires admin permissions (due to netaccess or symlinks). It then asks you if you like to relaunch as admin and if you choose yes it will skip right to the button that previously failed you for not being an admin.
Code: Select all
[CUSTOM CD MENU]
skiptobutton=X
So imagine you can have just 1 single INF file, but 10 shortcuts, saving you the trouble of having to create and maintain 10 INF files. It doesn't replace anything, just adds an alternate way to skip to buttons.
Internally I use it when you try to click a button that requires admin permissions (due to netaccess or symlinks). It then asks you if you like to relaunch as admin and if you choose yes it will skip right to the button that previously failed you for not being an admin.
Re: AutoRun LWMenu
Ok. The desired function. Overall, everything is great. I don't even know what else to offer.
Re: AutoRun LWMenu
In that case, finally released the new version, and while at it also added a feature of focusbutton=X (or /focusbutton=X via the command line) so the menu will focus on button X instead of the first button.
Re: AutoRun LWMenu
On github.com version 1.5.6. And in the file properties - version 1.5.5.8. Fix it.
Re: AutoRun LWMenu
Wow, thanks, re-uploaded, is it okay now?
It seems I've originally uploaded like 2 minutes before the new compilation was over. Well, at least the link remains the same.
It seems I've originally uploaded like 2 minutes before the new compilation was over. Well, at least the link remains the same.
Re: AutoRun LWMenu
Created two portable Media Player Classic - Black Edition programs. The first is through your program, the second is through Yap. Next, watch the video. First, I drag the folder to your launcher, then to the Yap.
Video https://streamable.com/au2s1f
Video https://streamable.com/au2s1f
Re: AutoRun LWMenu
I guess this means everything else is well?
Do you mean you ask to be able to associate/pass folders and not just files?
Correct me if I'm wrong, but yaP doesn't support opening an alternate INI file through a command line parameter, right?
For example, running c:\test\launcher.com c:\something:
Possible ways to solve it:
Do you mean you ask to be able to associate/pass folders and not just files?
Correct me if I'm wrong, but yaP doesn't support opening an alternate INI file through a command line parameter, right?
For example, running c:\test\launcher.com c:\something:
- In my case will open c:\something\Autorun.inf instead of c:\test\Autorun.inf.
- But if c:\test\Autorun.inf doesn't exist, like in your case, it will - per one of your previous features - extract a default Autorun.inf there first, which means opening up the default menu.
- In yaP's case will still open c:\test\laucher.ini, while passing c:\something into a {PARAMETERS} macro.
Possible ways to solve it:
- Force everyone (including myself) to use -ini to still get the present behavior, while the new default will be what you want.
I don't know how many pass an alternate folder, but for those that do it will break what they had for years, unless they will add -ini, but they won't understand what happened unless they read such an announcement. - Any other suggestions? Keep in mind all this logic happens before loading Autorun.inf so the solution can't be to add something to it.
Re: AutoRun LWMenu
I think we should leave it as it is. I came across this behavior by accident, and I don't use this method. I was just stating a fact. Everything else is fine and working fine. Version 1.5.6 is what you need.
Re: AutoRun LWMenu
Nevertheless, I've made a beta attempt at it, care to try? Folders should now pass to launched programs just like any other association (plus you can use -ini= to choose an alternate folder to grab autorun.inf from).
Re: AutoRun LWMenu
Now, when dragging the folder to the launcher, it says "file not found". Also when dragging through files.
Video https://streamable.com/4cuf3h
Video https://streamable.com/4cuf3h
Re: AutoRun LWMenu
It's probably because you have spaces in your folders and files, so added support for it, plus the ability to pass multiple parameters (although it's not relevant to this specific use case).
Also added a new feature admin=1 to be able to launch programs an admin (showed it on the default's menu CMD button).
Can you try the latest beta?
Also added a new feature admin=1 to be able to launch programs an admin (showed it on the default's menu CMD button).
Can you try the latest beta?
Re: AutoRun LWMenu
Thanks, everything is working as it should. Aren't you tired of me yet?