Features for POS terminal

[ANAT01]

Hi, use your program in POS terminal (start in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell)

It is work nice but have some feature proposal:

1. Config don't find If path in Shell (in registry) look to you program. I don't know, maybe lwmenu find that not there .exe located (in Shell I run bat with cd "c:\lwmenu" and then exec lwmenu.exe)

2. On start lwmenu - I need to start one program (example in [button1]) automatically, but haven't options for it.

3. POS computer have low performance of hardware and my work programs loading slow time. It would be nice if there was a possibility set a timeout to disable button active (users don't wan't to wait and clicking the button many times)

4. It would be nice if main preference will be possible to set centered position of windows and disallow close main window

Everything else is cool 👍 😃

[lwcorp]

Hi, thanks! That's certainly an interesting use for it, is there any way to see it?
In any case I've converted this to a discussion as each issue is meant for a specific feature request.
As for your questions:

1. It's hard to understand the phrasing, but when you click on Browse Folder, which folder does get opened?
2. Do you mean that Must I use menus? is not enough because you wish to open the menu and launch one of the buttons?
3. Why timeout and not just immediately upon clicking? And then do you wish to re-activate the button once they exit the launched program? BTW, in theory there's already singlerun=1 but not for this use case since it relies on the program already loading.
4. Centered position is what should already happen. Can you show a screenshot of what you see instead?
5. You asked it in the same question, but it's not related - the default config shows you can use button_close=blocked or button_close=hidden (I'll make it clearer in the next version - see 1f6b7cb), but do you ask to disable/hide the top right X button as well?

[ANAT01]

1. Don't remember but other which not contain lwmenu.exe
   Now I use batch script

CD "C:\Scripts"
"C:\Scripts\lwmenu.exe"

2. Yes. Both.
3. In my use case - lwmenu is main program of user. User work with two programs on computer time to time. If disable button permanently then user can't more run second program until reboot computer. But users don’t like to wait and press the button several times thinking that the program has not started and this causes problems in the launched application.
4. Need lock moving of window. It is not critical, just proposal.
5. Yes. Computer haven't keyboard (only touch screen). If close lwmenu (it is main program instead Explorer Shell) then user can't start any application more until reboot computer

[ANAT01]

To first proposal: Oh, found '/ini=' parameter. Don't know about that before 😄

[lwcorp]

Alright, released a new beta with everything, could you try it and share your input?

1. Didn't do anything, since /ini= seems to fix it for you.
2. Done! Just use the new feature clickbutton=X, which opens the menu and click button X.
3. Done! What I did was this flow, if you use the new feature singleclick=1:
   1. Click button X to launch a program
   2. Button X becomes disabled
   3. It waits till program X not only finally loads, but after it exits - read note below
   4. Button X becomes enabled again
4. Done! Just use the new feature kiosk=1. Keep in mind it's still possible to close the menu using task manager, since preventing that is probably stepping on kernel level territory, and it sounds your POS prevents task manager anyway.
5. Done! It's also part of the new Kiosk Mode.

Notes:

1. Also added Dark mode (automatic if your system uses it, but can also be defined manually as dark or light). Since you have the menu open all the time, you might like it.
2. All the new features can also be used as command line parameters (/clickbutton=X, /singleclick, /kiosk).
3. About 3. above, it might be possible to already activate the button as soon as the program loads, even before it exists, and thus allow to open multiple instances of it. But it's much more complex, and sounds like in your slow POC you should prefer anyway just 1 instance of each launched program.

[lwcorp]

Someone did spot an issue, so here's a newer beta.
Since all your requests became fulfilled, please join the effort and give it some testing, before it's released officially and then you might have to wait longer if you only then find something.

[ANAT01]

singleclick=1 option work not correctly.

It disables the pressed button, but also blocks the action of other buttons. After closing the first application, other pressed buttons start to launch one after another.

In screen record I run notepad.exe in singleclick mode and after that many times click button to run cmd.exe.
After that I close notepad.exe and cmd.exe start many times after close each.

[lwcorp]

I wish you tested it before the beta was done.
It's like this with every setting that requires waiting (like the setting that deletes files after the launched program exits).
While it waits, it queues further clicks until the launched program exits, and only then performs all queued clicks.
To fix this I'll have to reprogram the whole logic of waiting to do polling in the background. Will mention here when a new beta involving this comes out. Meanwhile maybe test the other new features.

[lwcorp]

Released a newer beta in which I:

Reconstructed the new multiple combination logic of skiptobutton VS buttonafter VS closemenuonclick VS kiosk

[lwcorp]

Since it seems you're unable or unwilling to test the features that were made for you, I've sent ahead and released them officially, hope they'll provide all you wanted.

I'll leave this discussion open for a while should you wish to continue it.

[ANAT01]

I did not have time to test the beta version, because... I didn't expect features to be added so quickly. Sorry.
Last time I tested all the functions mentioned, and the problem was only with the one I described. All the others worked well (there was also a problem with clickbutton along with singleclick, but this is due specifically to singleclick because of the queue). Thank you.