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

Comments

Anonymous said…
Andrew,

Cool demo of the CommandBars. I had one question though...how 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?
Anonymous said…
Andrew,

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

Thanks!

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

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.

Regards,

Alex

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

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 distinction...