You could just open https://github.com/lwcorp/lwmenu/releases/ and see if you can find it...sl23 wrote: ↑NOTE: Not really important as it's a beta, but that link gave a 404 error for some reason, despite it being the same as the previous link you posted, but with the updated version number.
AutoRun LWMenu
Re: AutoRun LWMenu
Re: AutoRun LWMenu
Thanks, I did find it by going to the previous beta link. Just thought I'd point it out as it was a bit odd.
Latest X-Launcher_x64 update - Compiled with Aut2exe_x64.exe v3.3.16.1
Latest X-Launcher_x64 v1.5.4 update - Compiled with Aut2exe_x64.exe v3.2.12.1
Latest X-Launcher_x64 v1.5.4 update - Compiled with Aut2exe_x64.exe v3.2.12.1
Re: AutoRun LWMenu
Link fixed, thanks! I've accidentally released the beta with an unneeded dot in there and now it seems too late to change, so I've edited the post to add that now needed dot.
Regarding shortcuts, now it makes more sense. Not mentioning /skiptobutton=X made me think you wanted auto shortcuts for relativepathandfilename, while you meant for the launcher itself. I'll try to add it soon enough.
Regarding donation, thanks! I've just signed up for GitHub Sponsors...only to find out they will probably force your dollar money (the only currency they accept) into being converted to my local currency, and they have zero documentation of exchanges rates and possible related fees.
There's now a Sponsor link in the program's homepage which you can try out. You can choose monthly or one time and enter a custom amount.
Meanwhile, I'll try to find a provider that lets me choose to accept money in dollars too and spare the exchange.
Anyone reading this is welcome to look at GitHub's known providers and tell me if one of them fits the bill.
Regarding shortcuts, now it makes more sense. Not mentioning /skiptobutton=X made me think you wanted auto shortcuts for relativepathandfilename, while you meant for the launcher itself. I'll try to add it soon enough.
Regarding donation, thanks! I've just signed up for GitHub Sponsors...only to find out they will probably force your dollar money (the only currency they accept) into being converted to my local currency, and they have zero documentation of exchanges rates and possible related fees.
There's now a Sponsor link in the program's homepage which you can try out. You can choose monthly or one time and enter a custom amount.
Meanwhile, I'll try to find a provider that lets me choose to accept money in dollars too and spare the exchange.
Anyone reading this is welcome to look at GitHub's known providers and tell me if one of them fits the bill.
Re: AutoRun LWMenu
Ah glad you understand the purpose now. I'm really looking forward to trying that one out!!!
Ok, sure just pop a link as your signature or something when you get it sorted.
Thanks for everything you've done, it's greatly appreciated.
Ok, sure just pop a link as your signature or something when you get it sorted.
Thanks for everything you've done, it's greatly appreciated.
Latest X-Launcher_x64 update - Compiled with Aut2exe_x64.exe v3.3.16.1
Latest X-Launcher_x64 v1.5.4 update - Compiled with Aut2exe_x64.exe v3.2.12.1
Latest X-Launcher_x64 v1.5.4 update - Compiled with Aut2exe_x64.exe v3.2.12.1
Re: AutoRun LWMenu
Shortcut generator was added, enjoy.
Please review it in the latest beta.
As for donations, the other providers are full of fees and hardships, so I might as well stick to GitHub's own one, which is displayed in the app's homepage.
Alternatively, I guess I can create a gift wishlist, probably in Amazon.
Please review it in the latest beta.
As for donations, the other providers are full of fees and hardships, so I might as well stick to GitHub's own one, which is displayed in the app's homepage.
Alternatively, I guess I can create a gift wishlist, probably in Amazon.
- Attachments
-
- Generate Shortcuts - menu.png (3.43 KiB) Viewed 2196 times
-
- Generate Shortcuts - prompt.png (3.62 KiB) Viewed 2196 times
-
- Generate Shortcuts - summary.png (3.66 KiB) Viewed 2196 times
Re: AutoRun LWMenu
You're a genius! Works great, needs more testing, but is working ok with a small menu of four buttons.
Could we leave out the AutoRun_x64 and (Button X) parts of the file name when generated? I Use an app called Renamer to bulk edit file names, but would prefer not to need to do this, if that's ok with you? I mean, perhaps you have some reason for it?
Thanks so much for this!
Send me a pm when you get the donation thing sorted as I'll get notified by email and can get back to you straight away with it! All the best to you buddy!
I have been looking at the AutoIT code and trying to learn by reading the PDF, I understand what I'm reading, so far, only on chapter 6 about Loops. It's interesting stuff!
EDIT: Tested with a menu containing 55 buttons, all good!
Could we leave out the AutoRun_x64 and (Button X) parts of the file name when generated? I Use an app called Renamer to bulk edit file names, but would prefer not to need to do this, if that's ok with you? I mean, perhaps you have some reason for it?
Thanks so much for this!
Send me a pm when you get the donation thing sorted as I'll get notified by email and can get back to you straight away with it! All the best to you buddy!
I have been looking at the AutoIT code and trying to learn by reading the PDF, I understand what I'm reading, so far, only on chapter 6 about Loops. It's interesting stuff!
EDIT: Tested with a menu containing 55 buttons, all good!
Latest X-Launcher_x64 update - Compiled with Aut2exe_x64.exe v3.3.16.1
Latest X-Launcher_x64 v1.5.4 update - Compiled with Aut2exe_x64.exe v3.2.12.1
Latest X-Launcher_x64 v1.5.4 update - Compiled with Aut2exe_x64.exe v3.2.12.1
Re: AutoRun LWMenu
Thanks!I do have reasons for both:
What do you think?
- (Button X) - What if you have multiple buttons with the same buttontext? Unlike my buttons, filenames must be unique. Besides, it makes it easy for you to track which button the shortcut goes for.
- AutoRun_x64 - What if you have other types of shortcuts in that folder? This way the launcher's shortcuts are grouped. Besides, if it's called, for example, "AutoRun_x64 Notepad", it doesn't mislead you to think it's a direct shortcut for Notepad.
What do you think?
Re: AutoRun LWMenu
Makes sense,
Latest X-Launcher_x64 update - Compiled with Aut2exe_x64.exe v3.3.16.1
Latest X-Launcher_x64 v1.5.4 update - Compiled with Aut2exe_x64.exe v3.2.12.1
Latest X-Launcher_x64 v1.5.4 update - Compiled with Aut2exe_x64.exe v3.2.12.1
Re: AutoRun LWMenu
Since all requests seem to have been fulfilled for now, new version released!
Re: AutoRun LWMenu
Excellent, thank you for everything. It's made it so much easier to manage shortcuts now!
Latest X-Launcher_x64 update - Compiled with Aut2exe_x64.exe v3.3.16.1
Latest X-Launcher_x64 v1.5.4 update - Compiled with Aut2exe_x64.exe v3.2.12.1
Latest X-Launcher_x64 v1.5.4 update - Compiled with Aut2exe_x64.exe v3.2.12.1
Re: AutoRun LWMenu
The examples are for buttons, while the new features are for global options and a toolbar command, as well as handling overloaded menus.Update the examples for each function in autorun.inf
Which examples do you feel should be updated?
Re: AutoRun LWMenu
Not sure if I mentioned this previously, but here's an instruction manual I created for myself.
All I did was try to combine the original examples into a more cohesive and easier to understand document that explains everything in situ.
I'm not sure now if everything is included, and it may need to be corrected or expanded. My attempt was to keep it simple and concise, while explaining everything I needed for my own usage, as I found the online github docs very confusing in places. This is likely due to translation issues?
Anyway, here's my personal version of the manual:
Maybe this could be useful to others?
All I did was try to combine the original examples into a more cohesive and easier to understand document that explains everything in situ.
I'm not sure now if everything is included, and it may need to be corrected or expanded. My attempt was to keep it simple and concise, while explaining everything I needed for my own usage, as I found the online github docs very confusing in places. This is likely due to translation issues?
Anyway, here's my personal version of the manual:
Code: Select all
; Portable Freeware forum: https://www.portablefreeware.com/forums/viewtopic.php?t=20583
; GitHub and download: https://github.com/lwcorp/lwmenu
; General Rules of use:
; Everything after a semicolon is ignored by the program.
; Text inside brackets is case sensitive, use Uppercase.
; Text on left side of "=" is case sensitive, use lowercase.
; Your text can be mixed case.
; Example: 'lowercase=MixedCase(UPPERCASE)'
; Wherever there is an X change that to your chosen button number.
; Path names do NOT need quotes around them if they contain spaces. But quotes are needed for the other commands because they support multiple values (multiple registry keys/folders/files), and without quotes the launcher will treat a space like a separator even if it isn't.
; Relative and absolute path names are accepted.
; If absolute paths don't work on APPDATA, it seems to indicate the author looks for %USERPROFILE%\AppData\Roaming\ so use: 'setenv=USERPROFILE|your.appdata.path' instead.
; The [AutoRun] section is only used if you need to launch an app when running from a USB device as it is plugged in. See https://en.wikipedia.org/wiki/Autorun.inf
; Unused [sections] and 'keys=' can be removed if you want to make it even more minimal.
==========================================================================
; The following is only used for [AutoRun]:
[AutoRun]
open=AutoRun.exe ; Absolute path to your app to be started on device plug in.
icon=AutoRun.exe, 0 ; The ", 0 " tells Windows to use the icon embedded in YourApp.exe.
; If you do not want an icon shown in 'ThisPC', put a semicolon in front of the icon line.
; If using your own icon file, use icon=MyIcon.ico instead.
; The following is only used globally for [CUSTOM MENU]:
[CUSTOM MENU]
hidetrayicon=1 ; Remove line or comment out with ; to show.
skiptobutton=X ; Run a pre-defined button instead of opening the menu. Can also use command line parameter '/skiptobutton=X' meaning you can keep all settings in 1 file, but use multiple shortcuts, each for another button.
clickbutton=X ; Tells the menu to click [BUTTONX] on launch.
kiosk=1 ; No window so remains in middle of screen and can't be moved.
theme= ; dark/light - Leave commented to use system theme.
fontface=helvetica
fontsize=10
textcolor=orange
buttoncolor=#fefee0
menucolor=white
buttonwidth=470 ; Comment out to make it automatic.
buttonheight=50
titletext=AutoRun LWMenu
maxbuttons=X ; So you can quickly test with and without lots of buttons.
button_browse= ; blocked/hidden
button_edit= ; blocked/hidden
button_close= ; blocked/hidden
; The following can be used both globally or for individual buttons:
admin=1 ; Run as administrator.
closemenuonclick=1 ; to close the menu after a launch.
blinktaskbarwhendone=1 ; Blink the taskbar after program launch.
focusbutton=X ; (e.g. focusbutton=3) Force menu focus on a specific button.
netaccess=0 ; Or netaccess=1 - Block/allow Windows Firewall net access.
simulate=1 ; Doesn't run, create or delete anything, only simulates operation.
singlerun=1 ; Launch the filename just once.
singleclick=1 ; Prevent clicking already clicked buttons.
; The following is only for invidiual buttons:
[BUTTONX]
buttontext=Dummy;
relativepathandfilename= ; Blank will display as a dummy button. Specifying a system filename will try to launch through the OS path. eg: cmd or notepad. SubMenu: Each menu displays a link to its parent menu (if it exists). Also, each menu can detect menus in its sub-folders. Alternatively, specify 'relativepathandfilename=folder' to load that folder's menu (if it lacks a menu, the folder would be launched regularly).
optionalcommandlineparams= ; Pass parameters to exe files, otherwise leave blank.
closemenuonclick=1 ; Closes the menu after a launch.
programpath= ; Accepts relative path. Define an alternative starting folder than the launched EXE. See below for more info.
registry= ; Delete registry keys on program close or use a + prefix to create before launch. You can also create basic entries like: (+HKCU\Software\Test,accept,1).
deletefolders= ; Delete folders on program close. Create before launch using + prefix.
deletefiles= ; Delete files on program close. Create before launch using + prefix.
backuppath= ; Backup of registry/folders/files to restore before launching program. Use . for current folder, but preferably a standalone folder to avoid clashes. backuppath=User ; should be automatically replaced with an absolute folder.
hidefrommenu=1 ; Hide a button from the menu. Preferably used with buttonafter.
buttonafter= ; Run another button (e.g. 4) after a previous button.
show= ; Launch app hidden/minimized/maximized.
setenv= ; Define temporary environment variable|value (e.g. APPDATA|c:\alternative_appdata) - Can have multiple lines of entries.
symlink= ; Create this folder/path as a symlink|target to another folder/file (e.g. %appdata%\program\|c:\program) - Can have multiple lines of entries.
==========================================================================
; If using folder structure like this, with User AppData folder in ROOT\APP:
; ROOT = the main folder where the Autorun EXE is contained.
ROOT\App\MyApp.exe
ROOT\App\User\AppData\Roaming\MyApp\(config files here)
ROOT\Autorun.exe
ROOT\Autorun.inf
; Then:
relativepathandfilename=App\MyApp.exe
setenv=USERPROFILE|..\User ; You have to specify ..\ in the path to the User folder as it won't see it otherwise!
; But, if using folder structure like this, with User AppData folder in ROOT:
ROOT\App\MyApp.exe
ROOT\User\AppData\Roaming\MyApp\(config files here)
ROOT\Autorun.exe
ROOT\Autorun.inf
; Then:
relativepathandfilename=App\MyApp.exe
setenv=USERPROFILE|..\..\User ; You have to specify ..\..\ in the path to the User folder instead!
; programpath indeed does just that - The starting point is the AutoRun launcher.
programpath=. ; Start where the launcher is.
programpath=.. ; Start from a folder above the launcher.
programpath=thisfolder ; Start from a folder called 'thisfolder' where the launcher is.
; Be careful though, some (many?) programs might not work if you don't launch them from their own folders, because they will look for their DLL files, etc. inside programpath instead.
Latest X-Launcher_x64 update - Compiled with Aut2exe_x64.exe v3.3.16.1
Latest X-Launcher_x64 v1.5.4 update - Compiled with Aut2exe_x64.exe v3.2.12.1
Latest X-Launcher_x64 v1.5.4 update - Compiled with Aut2exe_x64.exe v3.2.12.1
Re: AutoRun LWMenu
For sure. Thanks for posting.sl23 wrote: ↑ Maybe this could be useful to others?
Re: AutoRun LWMenu
I'm completely confused with "setenv=". You can use an example of the autorun.inf file of the program, where APPDATA is used and it is registered in setenv=
Preferably a ready-made program with a config.
Preferably a ready-made program with a config.