Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt November 11, 2024
Marcher Technologies Posted November 8, 2011 Posted November 8, 2011 I have no qualms with the acp menu structure, or positioning.... but when it vanishes before i can select an item because of mouse-out it is severely frustrating and un-intuitive... and its something that annoys many... would it be so horrible to have a delay on mouse-out before the menu ninja-vanishes? just my two cents.... when id rather click the application link than even attempt to use a sub-item... that's bad, right?
KitCarl Posted November 8, 2011 Posted November 8, 2011 I agree, The mouse out delay should be increased.
Richard.C Posted November 8, 2011 Posted November 8, 2011 I have lost count of the number of times I've fallen off the side of the menu *shakes fist* I agree, annoying. Our Apps menu is also taller than the page, which just adds to our woes >.<
.time Posted November 8, 2011 Posted November 8, 2011 I've noticed this and I don't use the dropdowns because of it. I think they should be click activated like the public dropdowns are.
Marcher Technologies Posted November 8, 2011 Author Posted November 8, 2011 I've noticed this and I don't use the dropdowns because of it. I think they should be click activated like the public dropdowns are. I would be happy with that as well for the menu sub-items... as it is now it is wholly unusable for me.... i see that they put a LOT of effort into a dynamic menu for installed applications modules, but when it is literally so hard to use it lays Un-used.... not much of a feature.
Aisha Posted November 8, 2011 Posted November 8, 2011 This but I'm more concerned with the menu taking too long to pop-up personally.
.time Posted November 8, 2011 Posted November 8, 2011 It's probably changeable by editing one word in the JS code... Anyone familiar with the ACP code willing to post a manual fix?
Bethanyrayne Posted November 8, 2011 Posted November 8, 2011 I think everyone that reads this would agree. i add my voice to a call for the mouse out delay to be increased.
3DKiwi Posted November 9, 2011 Posted November 9, 2011 Add vote. The new system is damn annoying closely followed by the silly OK message after you do something. 3DKiwi
Connor T Posted November 9, 2011 Posted November 9, 2011 I agree. I don't even use the dropdown menus because of the hover timeout. I just click the tab, and navigate from there.
Marcher Technologies Posted November 9, 2011 Author Posted November 9, 2011 I agree. I don't even use the dropdown menus because of the hover timeout. I just click the tab, and navigate from there. I am so often in "Other apps" that I have to at least use the base levels, as there seems to be no such thing as an "Other Apps" listing(hrmmmm...........idea)>.< but i simply wont bother with the sub-menus, and any tab i CAN use, i will over the drop-down.
broni Posted November 9, 2011 Posted November 9, 2011 We should be looking for "onMouseOut" value in one of ACP .js files. I checked few files but I wasn't able to find it.
Marcher Technologies Posted November 9, 2011 Author Posted November 9, 2011 ive found it, but ive nary a clue what to do with it, and that is kinda rare.... ive messed with the duration value on the doClose function's fade to no avail.... ahhhhh dangit browser cache... ill report back lol.>.< it looks like there is some.... js callbacks? /admin/js/acp.menu.js EDIT.... nope, set it to like 10 and did nothing.
Enkidu Posted November 9, 2011 Posted November 9, 2011 in admin/js/acp.jquery.js find:var timeout = setTimeout( function(){ $(_this).children('ul:first').hide() }, 250 ); increase the 250 to your liking.
broni Posted November 9, 2011 Posted November 9, 2011 Those are for fading in/out effects <----comment at Marcher's reply
Marcher Technologies Posted November 9, 2011 Author Posted November 9, 2011 in admin/js/acp.jquery.js find:var timeout = setTimeout( function(){ $(_this).children('ul:first').hide() }, 250 ); increase the 250 to your liking. very nice, no wonder i wasn't finding it, wrong file.... that is appreciated.
Marcher Technologies Posted November 9, 2011 Author Posted November 9, 2011 blah, and lookit it freak out..... is this truly a choice between having mass menu overlap and a reasonable delay, or "normal" behavior and insta-poof?? this actually seems more difficult to use... eesh>.<
Enkidu Posted November 9, 2011 Posted November 9, 2011 blah, and lookit it freak out..... is this truly a choice between having mass menu overlap and a reasonable delay, or "normal" behavior and insta-poof?? this actually seems more difficult to use... eesh>.< what do you wanna do?
Marcher Technologies Posted November 9, 2011 Author Posted November 9, 2011 what do you wanna do? well right now, when i breeze (.... i know) my mouse over a set of menus, they all appear(and stay..... and stay..), and the correct behavior is for the mouseout to have the delay, but the mousein on another item to close the previous menu. i have trouble hitting the menu on transition... the behavior incurred by above mod just makes it worse.... not at all your fault btw Enkidu, its a flaw in the standard acp js if anything.
Enkidu Posted November 9, 2011 Posted November 9, 2011 well right now, when i breeze (.... i know) my mouse over a set of menus, they all appear(and stay..... and stay..), and the correct behavior is for the mouseout to have the delay, but the mousein on another item to close the previous menu. i have trouble hitting the menu on transition... the behavior incurred by above mod just makes it worse.... not at all your fault btw Enkidu, its a flaw in the standard acp js if anything. you can add some delay to the .hide() in the above code e.g. .hide('300') but I would expect you to still have problem. You see the way IPS implements the dropdown menu is through a timer that gets cleared on mouseout and sets on mousein. There is no way around without rewriting the code, IMO.
Marcher Technologies Posted November 9, 2011 Author Posted November 9, 2011 you can add some delay to the .hide() in the above code e.g. .hide('300') but I would expect you to still have problem. You see the way IPS implements the dropdown menu is through a timer that gets cleared on mouseout and sets on mousein. There is no way around without rewriting the code, IMO. seeing that..... wow..... shouldn't it viably simply close the menu when we mousein on another? I really don't see the point of it closing on a timer in the first place, the new mousein or the page refresh of a click should be closing it.....>.< not some set length of time.
broni Posted November 9, 2011 Posted November 9, 2011 Try changing it to some reasonable number. 250 is 250ms, try 2000, or 3000, which will be 2s-3s.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.