Skip to main content

Using the CommandBars library

Some users asked me a while ago about how tough it was to use the CommandBars library from Arg.

It's not hard but I've prepared a sample screen cast on it:
Using the CommandBars library


Anonymous said…

Cool demo of the CommandBars. I had one question well does it integrate/hook into the VFP menu?

By that I mean, does it automatically know things like when to enable/disable the menu options like Cut, Copy, Paste, etc. the way VFP's native menu does? You are well aware that the latter has the smarts built into it to determine which menu and items are applicable when say I highlight some text in an editbox control.

What about context sensitive/shortcut menus?
Malcolm Greene said…

I really enjoyed your narrated screen presentation of how to use the CommandBars product.


Malcolm Greene
Andrew MacNeill said…
Here are some comments from the author:

Sorry for the delay with reply. I was out several days and had no chance to read my e-mail and to write you.

Yes, it is possible to enable/disable menu items (Cut, Copy, Paste, etc) automatically. The SkipFor property was designed especially for that.
For sample, if the SkipFor property contains "SkpBar("_MEDIT",_MED_CUT)" value, the Cut menu item will be automatically enabled/disabled, like native Cut menu item works.

Developers can easy create context sensitive/shortcut menus, samples provided with the library contain simple shortcut menu example (PopupMenu1 on Form1). To activate that menu all they have to do just call the ShowPopupMenu method of the CommandBarsManager object. For sample, the RightClick method of the cntClientArea object of the Form1 contains the following code:
ThisForm.CBM.ShowPopupMenu( ThisForm.PopupMenu1)

Please let me know if you, or someone else, have other questions.



Popular posts from this blog

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator)

So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinctions I…

Security in Windows 10

 discusses some Windows 10 privacy settings and their implications.

"Finally, we will access, disclose and preserve personal data, including your content (such as the content of your emails, other private communications or files in private folders), when we have a good faith belief that doing so is necessary." "In other words, Microsoft won't treat your local data with any more privacy than it treats your data on its servers and may upload your local data to its servers arbitrarily"
I did a quick install on a VM choosing the Express settings. When I fully deploy this on a real workstation, I will likely choose to wade through all of the individual pages, as David recommends.

Of course, losing one's privacy is nothing new - it's happening all over the place (despite Santa Ana's police force's lawsu…


I'm not TRYING to be "fanboy-flame bait" but what I saw yesterday was a typical "Do it this way, now do it this way and then we'll go back to this way" all over again.... a move similar to what Microsoft does to developers on an ongoing basis.

Remember the first iPhone? Smooth and curved, at least as far as it could be back then. I still pull out my 3G and can see the curves on it.

Then the 4 came out and "boxy" was all the rage. Everything should be "tight with corners"

Now iPhone 6.... smooth and curvy is back. Granted I don't have the actual device yet, but that's the message.

Guess that means the iPhone 8 will be back to boxy.

And honestly, Apple Watch is not worth "one more thing" --- especially when everyone knows it's going to be shown. "One more thing" would be something no one saw coming.  The device itself ? Very interesting and yes, definitely lots of potential but "one more thing" wor…