search

Cacti / cacti

Cacti ™
http://www.cacti.net
GNU General Public License v2.0
1.63k stars 405 forks source link

Update console navigation menu to show/hide via pin button #1508

Closed chathurag closed 3 days ago

chathurag commented 6 years ago

If we are already in graphs tab page cannot be reloaded by clicking graphs again.

Also for nectar tab this happens. When we are editing one report unable to use browser back button or reload nectar main settings by clicking nectar tab.

netniV commented 6 years ago

The top tab being non-clickable is by design since you are on that tab currently because when you are on the console tab, it shows/hides the console menu. We could potentially allow it to work differently on the non console tabs as I can see how it would be useful clicking them to force a reload.

cigamit commented 6 years ago

I've been re-thinking this behavior. But no changes for now. We'll keep this open for the moment.

netniV commented 6 years ago

No further thoughts in a while, so I'm going to close this one.

cigamit commented 6 years ago

Right now, in the Classic, Modern, and Dark themes, you can re-click the breadcrumbs and that will force a page reload. I use that all the time when I need to. For the other themes, you need to press F5. I know what the user is asking for here, and I've given it some thought, but it is not important enough for the 1.2 release.

I suggest we open a new ticket and request something more positive then negative. What I'm suggesting is a widget by the left pane navigation that allows you to open and close it. That way we can remove the show/hide of the navigation feature on the second click of the tab behavior. But the bug should be labeled as such.

netniV commented 6 years ago

Like a side-ways button when collapsed that would expand, with maybe a pin for keeping it permenantly open? Similar to this:

nav

netniV commented 6 years ago

Found this fiddle that seems to be similar to what I was suggested: http://jsfiddle.net/W7sNp/1/

cigamit commented 6 years ago

Yea, that's kind of it. Simple thing to do, but each theme may have to do it differently, which is the rub. If it were not for classic, this would be easy. @ronytomen would just say wipe out Classic, but the backlash "might" be large.

netniV commented 6 years ago

So we leave the old functionality for classic, since it's classic. Put the new functionality into the new themes?

cigamit commented 5 years ago

I've seen an interesting method of doing this lately, that should not be too complicated. All these UI issues should be moved to 1.3.

TheWitness commented 3 days ago

This issue is resolved differently in the Cacti 1.2.x and above using local storage.