hide/disable entries in the web interface

[Batwam]

Hello,

I love this utility but I was wondering if it would be possible to hide/disable entries in the web interface so they can be kept as template or for future use without being deleted.

For instance, there could be a checkbox somewhere to disable it which would grey out the text and remove them from the export but leave them in the list?

[bassmanitram]

Thank you for kind remarks and for using AFN.

Now THAT is a cool suggestion - I'm already thinking on it and it wouldn't be too tough! THANK you!

[kb-ig]

Came here for the same thing. I like having the default actions present in the config UI to refer to, but I dont actually need them in the Nautilus context menu. Being able to disable them would be a great addition.

[bassmanitram]

Hey there - you mean the delivered actions on first start? I think I could a) put them in a submenu and b) add a "disable" flag to submenus and items so that they stay in the config but don't get parsed or displayed. then you could disable that submenu when you start adding your own - and disable any other that you might want to keep around but not use Would that fit your requirement? Thanks for using A4N Martin

…

On Mon, Oct 7, 2024 at 2:45 PM Kieron ***@***.***> wrote: Came here for the same thing. I like having the default actions present in the config UI to refer to, but I dont actually need them in the Nautilus context menu. Being able to disable them would be a great addition. — Reply to this email directly, view it on GitHub <#57 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADAKLWVNUF5VLCJR6GW344TZ2J65TAVCNFSM6AAAAABPP3DHWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWHAZDSMJQGI> . You are receiving this because you were assigned.Message ID: ***@***.***>

[kb-ig]

Hi @bassmanitram, thanks for the quick response.

you mean the delivered actions on first start

Yeah, I think that's what I'm referring to (the actions that seem to be included by default) - screenshot included below to clarify.

I dont think it's necessary to hide them all within a sub-menu. In fact, I think doing so would make it more difficult to get familiar with this app. It's useful to have top-level examples of a command (e.g. the "Open in Gedit" command).

I think all we need is a bool/switch on each action in the web UI so we can enable/disable them from the Nautilus context menu. If an action is disabled, it's still visible in the web UI but will not appear in the Nautilus context menu. If it's enabled, it's visible in the UI and Nautilus context menu.

Looking back over the requirement @Batwam described:

hide/disable entries in the web interface

I think they mean something along the lines of what I'm describing, as opposed preventing the action from appearing in the web UI.

Screenshot for reference

These are the actions that seem to be created by default. They're useful for reference, so I'd like to include them in the UI but not show them in the Nautilus context menu.

Edit: I just want to highlight how useful this app is! For years I've just accepted poor the default Nautilus context menu actions are, but now I can finally add what I need. Thanks a lot for maintaining this!

[Batwam]

Yeah, what I meant would be to have entries which are listed in the UI so they can stay visible (eg templates) but are marked as inactive so they do not appear in Nautilus.

I haven't looked at how the underlying config file looks like but essentially something similar to commenting out a line of code where it's visible to the person setting it up but not actually actioned.