View Single Post
Old 08-12-2020, 06:33 PM   #221
geek1011
Wizard
geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.
 
Posts: 2,804
Karma: 7025947
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
Quote:
Originally Posted by babygau View Post
@geek1011, is it possible to put nickel menu item in `more` tab, i find myself `nickelmenu` tab is redundant and clutter.
Quote:
Originally Posted by DNSB View Post
Personally, I like it where it is. I don't find it redundant since it's the only instance on the home/my books/discover/more screens. I also like having the 5 icons since, to my eyes, it balances the bottom bar. The current location also saves me a tap each time I want to use a NickelMenu function.
I also like it where it is, since in addition to the points you mentioned, I also find it easier to press blindly when it's in the corner.

Quote:
Originally Posted by babygau View Post
your opinion is not wrong, however, i think it would be better to have more options for everyone :thumbsup:
I don't want to add too many arbitrary options to NickelMenu for a few reasons:
  • Options for positioning are going towards being out of scope for NickelMenu, which is intended for adding custom menu items, not changing the UI in general.
  • The fewer options there are, the less breakage there is between firmware versions and the more flexibility I have to improve things in the long term while keeping compatibility. For example, if I had given more options for where to add the menu items in the main menu, implementing live reloading would have been a lot more complicated, and also, I would now have to figure out what to do with that option (e.g. not everyone reads the documentation, but might complain if an option they see somewhere stops working in a new version) since it only applies on the older firmware version.
  • If I add options for positioning, I won't be able to reload them with the rest of the config without a lot more work and code.
  • The fewer options there are, the stabler it is.
  • For this option in particular, remember that NM used to add items to the menu, and it's not like you could control that before this version.

Quote:
Originally Posted by Vladi69 View Post
I see that it doesn't accept <label> like ON/OFF in reader, library, browser. But in main it is accepted, seems strange. Is it known?
Can you show me the exact `menu_item`s you added to the config file, and if possible, a screenshot of what happens?

Quote:
Originally Posted by John F View Post
With the Kobo firmware changing, any chance that you can implement setting the light level using nickelmenu?
The situation with the frontlight hasn't changed.

Quote:
Originally Posted by compurandom View Post
Debugging NickelMenu is an exercise in frustration.
It'd be a lot less so if an error didn't zap all my custom menus, especially the one containing force usb... :)

Instead of ignoring all configuration, when it gets an error, could you have it add the config error to the menu as it does now and then do one of the following:

* stop reading config entries, but accept what it has read so far

* abort reading the current file (or ignore everything in the current file) but continue to the next file as if there was no error

* skip the flawed entry (and any following chained entries), but continue with the rest of the file

Ideallly, if there are multiple flaws, it might end up with multiple config errors in the menu.
The issue with that is it makes reloading a bit more complicated, but I'll consider it for later.

Quote:
Originally Posted by compurandom View Post
On a related note, the entry that was failing for me was:

Code:
menu_item:main:Web Browser: nickel_browser:
Did I miss something to open a non-modal default url?
I can get it to work if I either add modal or add a url (or both).

Also, there's no examples in Doc for nickel_browser
Are you sure you included the trailing colon? If so, what was the exact error message?

Quote:
Originally Posted by Patatas View Post
Dumb question, with Nickelmenu can I launch QT apps, or thats outside of the scope of things it can run?

I am unsure if this can be a replacement to something like Kobo Launcher or if they are different things?
Yes, you should be able to launch normal Qt apps with NickelMenu as long as the executable is standalone or you have a script to launch it. You can use the `cmd_spawn` action to start it.
geek1011 is offline   Reply With Quote