Date this page was last
edited 04/01/2008 01:56:28 PM
(BE
SURE TO REFRESH YOUR BROWSER TO GET THE LATEST PAGE)
Shown below is the example invoice app with 3 menu
trees up to show variation of use. Spiced up
a little bit of course with BigMenuTree(tm) added... The Menu Tree
on the right has been resized to be a little wider so the user can see all or
most all of the text in the tree branches. You can make text different
sizes and typefaces to suit your (client's) fancy.
Many users have complained about how difficult it is to find what they are
looking for in the "standard" drop down menu system. It also
seems that the "tree system" of organization is the easiest for users to
grasp and understand,
especially a new user. Using Menu Tree the user can expand the
whole Menu Tree if they want and simply scroll to find the menu choice they
are looking for. This is especially true for the new user that hasn't
learned their way around a new application yet and get discouraged because
they can't find what they are looking for.
Shown below is the Menu Tree called 3 times to show how it looks with partial
and full expansion.
Shown below is the example invoice app with a normal
single menu tree and the tree browse from the invoice example app shown too. Spiced up
a little bit of course... As you can see, the look and feel is real
"clean" and easy to "read at a glance". You have
complete flexibility using menu tree with only the File and Menu Tree in the
drop down menu. All the rest of the drop down menu stuff is simply
hidden by the developer.
You can have any combination of procedure
calling methods you want in your applications to fit the user's desire.
To use the menu tree in the most effective way you should also have the app
set to remember window screen positions for procedure windows when they are called so
they will re-appear in the "correct" locations each time a particular
procedure screen is opened after they are "moved there" the first
time. That also allows the user to have any
combination of screens up at any time.
Menu Tree gives you the Developer the complete freedom to design your menu's
using MenuTree(tm) with or without drop down menus and button bar style in any
combination.
Add a button or drop-down menu choice for the MenuTree to call the MenuTree procedure.
Start a thread.
Pick default generic window, no buttons.
Add the control template to it--- BMTList MenuTree list
Resize window, etc.... Salt to taste. <g>
Go to the windows properties and pick
Frame Type 'Single or Double or Resizeable'
Initial Size 'Normal'
Go to Extra Tab and check
3D look
Toolbox
Float
Make sure rest are unchecked, don't want dock or left
right, etc.
Go to Window behavior and check INI File Settings:
>> Save and
Restore Window Location.
Go to procedure properties; >> Procedures
button:>> and >> Select All.
The procedures have to be selected here to run from the MenuTree.
You can also remove or hide all or most buttons
and hide most of the dropdown menu selections
and provide only the MenuTree if you want to clean up
the window... Or leave them in if desired...
Change the MenuTree header text to MenuTree or
whatever...
Fill in the Has Action Icon, and No Action Icon, and you are set. Change the other options as needed
Thats it, compile and test.
(So simple to use no other screen shots are
necessary.)
For the end user,
The menu items that DO NOT call procedures have the blue NoAction icon and are
the menu branching "categories" and "subcategories" per se'.
Just double click the other ones to fire off events to run your procedures.
The others like copy, paste, printers, tile windows,
etc don't work
due to idiosyncrasies of the CW menu system.
Enjoy
Bo
Date this page was last
edited 04/01/2008 01:56:28 PM
(BE
SURE TO REFRESH YOUR BROWSER TO GET THE LATEST PRICE AND PAGE)
Price: $39.00 Through October 31st Midnight CDST
as an earlybird special.
Price: $79.00 After above early bird special
expires.
