Skip to main content

Using BINDEVENT to ease FoxPro Grid issues

BINDEVENT is one of those great FoxPro commands that you never think of until you need it but when you do, you really appreciate it and you'll want to immediately refactor your code (hmmm- this sounds like a good Refactoring rule for the Code Analyst).

I was updating a client's older VFP system that used a lot of grids with RightClick methods. Lots of older programs do the same thing: putting code directly into the rightclick method of each columns' Text1 control. It's a real pain later on - especially if you ever reset the recordsource (which rebuilds the columns from scratch). In addition, if you use Page Up and Page Down to scroll through the various pieces of code, you get to see each individual column's method, which can get very tedious if you have a lot of grids.

Now, when you use BINDEVENT, it's a lot less code and a lot easier to manage. I put the actual rightclick code into a method either on the form or grid and then just do:

FOR EACH loColumn IN THIS.Grid.Columns
BINDEVENT(loColumn.text1,"Rightclick",;
THIS,"ColRightClick")
ENDFOR

When the user right-clicks in the grid, it calls the ColRightClick method.

Is this easier than putting THIS.ColRightClick() in each Text1 object? Maybe not if you only have two or three columns; but most of the grids I work with have lots of columns. Using this approach means I can keep my code OUT of the grid's columns and accomplish this in only three lines of code.

Comments

Garrett said…
Yup, BINDEVENT() is really useful in this situation.

The question is, is it more useful here than MemberClasses?

Popular posts from this blog

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

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

I’m Supposed to Know

https://programmingzen.com/im-supposed-to-know/ Great post for developers who are struggling with unrealistic expectations of what they should know and what they shouldn't. Thirty-forty years ago, it was possible to know a lot about a certain environment - that environment was MS-DOS (for non Mac/UNIX systems). . There was pretty much only a handful of ways to get things going. Enter networking. That added a new wrinkle to how systems worked. Networks back then were finicky. One of my first jobs was working on a 3COM + LAN and it then migrated to LAN Manager. Enter Windows or the graphical user interface. The best depiction of the complexity Windows (OS/2, Windows NT, etc) introduced that I recall was by Charles Petzold (if memory serves) at a local user group meeting. He invited a bunch of people on the stage and then acted as the Windows "Colonel", a nice play on kernel. Each person had a role but to complete their job they always had to pass things back to h...