-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
menus with check/uncheck values becomes assigned to different ones when a submenu exist above them #117
Comments
Thanks for investigation and report. I can not check now. Could you please check whether menu.text is expected one in the cmd functions! |
don't worry, for when you have a spare time, menu.text is Not the expected one in cmd functions:
If a separator is added before menu_4, it get displaced one element:
In both cases the submenu behavior seems the expected:
Also it gets displaced if it's added a menu at the top:
The above rendered as:
And if the separator before menu_4 is enabled, it gets displaced again (with strange pattern) , rendered as:
there menu_5.text in cmd is menu_5 (just as happens with .checked ), what is the expected behavior. In all cases the submenus behavior seems correct. |
Thank you so much @sieukrem The build works as expected with the second debug code ( DebugMenu2 ) , but with the code of the first post ( DebugMenu ) the issue keeps happening . First post "DebugMenu", before patched build:
First post "DebugMenu", with patched build ( gets one element displaced ):
First post "DebugMenu", with patched build, enabled separator ( gets two elements displaced ):
I disabled menu elements of DebugMenu2 with the patched build until the issue raised. It seems the menu_0 and SubmenuTwo absence may be what alters the elements position that are seen with DebugMenu in the patched build: New debug code DebugMenu3
Test1: Issue keeps with the first patch
Before the first patch: -- Test2: Issue keeps with the first patch
Before the first patch: -- Test3: Issue keeps with the first patch
Before the first patch: -- Test:4: Issue SOLVED with the first patch
Before the first patch: -- Test5: Issue SOLVED with the first patch
Before the first patch: -- PS: Take care when you uncomment the blocks in the above debug code by selecting the lines and right-clicking, as I just realized there is some kind of issue with Notepad++ what do an unexpected uncomment of unselected lines. One select Test2 variables for uncomment, and it turns that Test2 and Test3 variables becomes uncommented. Edit: updated code to 5 test |
Perfect. This new build seems to solve all the issues @sieukrem , thank you so much for your time! The tests what I've tried are: // OK // OK // OK // OK // OK // OK // OK Additionally, I added more submenus, submenus of submenus, separators, and other combinations, in Notepad++ v8.4 and 8.5. All works as expected with this build. |
Hi, it may be some kind of array key misaligned? but I wasn't able to locate were. I hope it don't takes much of your time,
Description of the Issue
The menus with check/uncheck values becomes assigned to different ones when a submenu exist above them.
Adding a sepparator or other menu also affects such wrong assigment.
To Reproduce
Expected behavior
It's expected the above code render as,
SubmenuOne >
menu_1 : unchecked
menu_2 : unchecked
menu_3 : unchecked
menu_4 : checked
<<menu_5 : checked
<<if a menu is clicked it gets checked/unchecked and none of the other menus gets affected.
A separator or other menu would not affect the above neither.
Actual Behavior
Actually the menus are wrongly rendered as,
SubMenu 1 >
menu_1 : checked
<<menu_2 : checked
<<menu_3 : unchecked
menu_4 : unchecked
menu_5 : unchecked
if menu_4 is clicked, what gets checked/unchecked is menu_1
if menu_5 is clicked, what gets checked/unchecked is menu_2
If a separator or menu is added before menu_4, then menu_1 renders unchecked, and menu_2 and menu_3 as checked.
I took as temporal workaround not to use submenus at the top.
.
The text was updated successfully, but these errors were encountered: