The Portable Freeware Collection Forums

In that case released the new official version. Guess I also know what it's like to be from the side that submits issues...

Bear with me: Haven't used it yet but I'm just wondering here if there's any way to run LWMenu without it showing its UI, only executing launching directives (kinda like yaP does)?

In the affirmative, I see LWMenu could easily become yet another Portabilizer alternative...

Well, it's double affirmative because it's actually an official feature that was based on a previous discussion is this very thread.
This FAQ explains how to do it and you can also see it in the comparison table.

I'm sorry, but it's not enough for me. Somewhere here in the Yap topic, the name of the project with the name "Gap" flashed. It is based on Yap, but the author allegedly built in work with services. That is, deleting the services installed by the application after it is closed. Is this feasible?
viewtopic.php?t=22129

lwc wrote: ↑ Well, it's double affirmative because it's actually an official feature that was based on a previous discussion is this very thread.
This FAQ explains how to do it and you can also see it in the comparison table.

Thanks for enlightening me -- I hadn't caught that feature, I'll have to look into it...

You're all welcome to try the latest beta with various new features, most of which were based on this user's kiosk mode use case discussion.
The main new features are:

1. Dark mode (great for the eyes)
2. clickbutton=X (opens the menu and then clicks a button)
3. kiosk=1 (prevents moving or closing the menu)
4. singleclick=1 (disables a button after it's clicked until the program it launched exists)

Now you have to forcibly use the "closemenuonclick=1" parameter. Otherwise, after closing the program the main LWMenu opens.
This was not the case in the previous version.
Example:
[CUSTOM CD MENU]
hidetrayicon=1
skiptobutton=3
blinktaskbarwhendone=1
singlerun=1
; netaccess=0
; admin=1

[BUTTON3]
buttontext=Audioconverter
relativepathandfilename=App\audioconverter.exe
registry=+HKEY_CURRENT_USER\Software\Abyssmedia
backuppath=App
closemenuonclick=1

@lwc & -ElCoyot-: Thanks to both -- I reckon the example provided may be a great starting point...

-ElCoyot- wrote: ↑
Example:

Code: Select all

[CUSTOM CD MENU]
hidetrayicon=1
skiptobutton=3
blinktaskbarwhendone=1
singlerun=1
; netaccess=0
; admin=1

[BUTTON3]
buttontext=Audioconverter
relativepathandfilename=App\audioconverter.exe
registry=+HKEY_CURRENT_USER\Software\Abyssmedia
backuppath=App
closemenuonclick=1

-ElCoyot- wrote: ↑Wed May 15, 2024 11:34 am Now you have to forcibly use the "closemenuonclick=1" parameter. Otherwise, after closing the program the main LWMenu opens.

Good catch, fixed! Can you try the latest beta? There are so many options now and thus greater risk of clashes. Please do let me know if you find any more clashes.

Midas wrote: ↑Thu May 16, 2024 5:19 am @lwc & -ElCoyot-: Thanks to both -- I reckon the example provided may be a great starting point...

No problem, you can also see the default file that comes with the launcher, which can also be seen right in GitHub.

Good catch, fixed!

No, it's repeating itself.
Video https://streamable.com/pgbkdz

I can't reproduce this using your own autorun.inf from an earlier post. But your video shows it's HijackThis, while the autorun.inf you pasted earlier was Audio Converter.
When you post a movie, please include exactly the matching autorun.inf
If it was the same autorun.inf I'd ask to click Help=>About to make sure it shows the latest beta version.

I did not specify the "closemenuonclick=1" parameter. I'm telling you, it wasn't needed in the previous version. And so yes, the menu does not appear with this option.
[CUSTOM CD MENU]
hidetrayicon=1
skiptobutton=3
blinktaskbarwhendone=1
singlerun=1
; netaccess=0
; admin=1

[BUTTON3]
buttontext=HiJackThis
relativepathandfilename=App\HiJackThis.exe
registry=+HKEY_LOCAL_MACHINE\SOFTWARE\HijackThis+
backuppath=App

Can you try it in the latest beta?

Just to show why it's complex - even just coming up with all these options:

Originally before buttonafter and kiosk existed:
If Launched button while skipping or asked to close menu => exit

What should be now:

1. Launched button while skipping menu + no buttonafter + asked to close menu => exit
2. Launched button while skipping menu + no buttonafter + asked to keep menu open => exit (skip beats asked to keep menu open)
3. Launched button while skipping menu + buttonafter + asked to close menu => launch buttonafter (without menu)
4. Launched button while skipping menu + buttonafter + asked to keep menu open => launch buttonafter without menu (skip beats asked to keep menu open)
5. Launched button with menu + buttonafter + asked to close menu => close menu + launch buttonafter (without menu)
6. Launched button with menu + buttonafter + asked to keep menu open => launch buttonafter
7. Launched button with menu + no buttonafter + asked to close menu => exit
8. Launched button with menu + no buttonafter + asked to keep menu open => do nothing

Combining + adding kiosk logic (only relevant when not skipping) - this is what needs to tested:

1. if Launched button with menu + no buttonafter + asked to keep menu open => do nothing
2. else if Launched button while skipping menu + no buttonafter => exit
3. else if Launched button with menu + no buttonafter + asked to close menu + kiosk => do nothing
4. else if Launched button with menu + no buttonafter + asked to close menu + not kiosk => exit
5. else if Launched button while skipping menu + buttonafter => launch buttonafter (without menu)
6. else if Launched button with menu + asked to close menu + not kiosk => close menu
7. else if Launched button with menu + buttonafter => launch buttonafter

Thank you.It works the way it should.

In that case, new version released.