I am testing the current SE V19 Release Candidate 02 - (SE V19 RC2) -
using four SE Menu Module testcases (as attached).
I have attached 4 testcases (V_04, V_05_A, V_05_B, V_06) - that show a
size limitation on menus. All four are pretty much identical - except
around line 785.
My test results - to load the SE module are;
V_04 - Pass (see Line 785) - No submenu
V_05_A - Fail (see Line 787) - submenu "PoiNT"
V_05_B - Fail (see Line 787) - submenu "SCoPe"
V_06 - Pass (see Line 785) - submenu "PoiNT" (Note submenu "PoiNT" loads OK)
The last testcase (V_06) shows that the two failing testcases have no bugs
in syntax (V_05_A, B). In V_06 - I commented out a previous submenu
section (submenu "Base Action High Level") - to make room for the submenu
items in V_05_A, B - to prove the syntax is OK.
Thus : The two failing testcases - appear to fail - due to a size
limitation of custom menus in SE (and not a SE code syntax problem).
In summary:
The SE custom menu in testcase V_04 loads OK - and actually works (when
the macros are loaded).
NOTE : I did not attach the SE Macro module - that has the commands used
by the menus. The macros work just fine. Its the menu size problem that
is the issue (herein).
Near as I can tell....
The SE custom menu in testcase V_05_A - Fails the load process - due to a
menu size limitation.
The SE custom menu in testcase V_05_B - Fails the load process - due to a
menu size limitation.
I have found some other issues with custom menus - but this post is
focused on what appears to be a size limitation. The failing testcases
(attached) - appear to be one submenu item too many (right on the cusp of
the failure point).
Is there a size limitation? - and can this be fixed - so that SE can
perform like any other Windows application (ie; Large scale menus are no
problem).
When any SE custom menus get around this size - a massive failure can
occur in the SE GUI - which I will post in another topic (under SE V19
RC2 beta testing).