Verification of Issue

[MikeC]

Hi all,
I have found an issue that before sending in as an additional bug in a sample I have been using for this purpose, I would like to make certain it is not something I simply have missed (or messed up!).

It involves having both a Browse Title button and Row buttons for the same field. As it stands currently, the only event that is honored for the _Buttonclick() function located in the browse events Events is when the object name is used such as Address1_Buttonclick(). You are supposed to be able to name the event for each button and use that but I cannot do so.

Using Form1 the two buttons are located in the Address1 field. I have given more information on the form itself.

I have NOT given instructions as to where to find or change the properties so unless familiar with browse buttons most likely you will not be able to test this---

Clicking on the Title button should present a messagebox of: "Address1 TITLE button event" and clicking on a Row button will bring up the message "Address1 ROW button event". The Row button event uses the Object name which works. The Title button uses the event name created in its properties and does Not work--brings up the Row button's message.

The two associated events Events are second and third from last in the Browse events editor.

[Tim Kiebert]

Re: Verification of Issue

Yeh its a bug. And he is sitting in front of your keyboard. :D

There is/should only be one code/function block per column. (EDIT: Previous sentence is not completely correct. See comments to Tom in posts following) In the button setup dialog the last field is called Event Name. Here you have 'Event1' for the title button and 'plus' for the row button. Use these event names with in the function for the Address1 column to distinguish the two button actions. The event names are passed in to the function using its 'event' parameter. If you only have one button defined for a column you can get away with not specifying an event in the code because you don't need to distinguish one event from the other.

Delete the code block that you have for 'Event1' and change the code block for the Address1 column to

FUNCTION Address1_ButtonClick AS V ( event AS C, data AS C , row AS N )
'DESCRIPTION: Fired when a button is clicked on a column.
'Arguments:    event    - the name of the event that is fired
'            data    - the data in the column cell
'            row        - the row number in the browse
    'this.SetViewport_Row() sets the current row to the row with the button that was clicked.
    this.Set_Viewport_row(row)
    [COLOR=Red]select
        case event = "plus"
          msgbox("Address1 ROW button event")
        case event = "event1"
          msgbox("Address1 TITLE button event")
    end select[/COLOR]
END FUNCTION

[Tom Cone Jr]

Re: Verification of Issue

Tim, I, too, have been struggling with the EVENTS event for embedded browses. Your post helps a bit. Is there additional documentation somewhere? How about some more examples? Where should I look? Thanks.

-- tom

[Tim Kiebert]

Re: Verification of Issue

Tom,

Afraid I can't point you to any specific help topics. What I learned I gleaned from the 'Whats New' stuff when v8 came out(or was it v7), the odd example I came across, and trial and error.

Happy to help (if I can) on any specific questions.

In general, the functions seem to follow the hierarchy found in the naming convention. The top is the column name. Then the event type (ie buttonclick or column event. I think the only one so far is OnChange.) Then for button clicks you use the event name as described to Mike to further distinguish the actions.

So my comment to Mike re only one function per column is not correct. It should be only one buttonclick function per column in his particular case and in general one event type per column.

[Tom Cone Jr]

Re: Verification of Issue

thanks, Tim.

[MikeC]

Re: Verification of Issue

Tim,
Thank you (again!!). I can get a simple Title button now to work with row buttons (even conditional ones).....but I have a more complex Title button that changes its text from Expand to Contract dependent upon conditions...which is present also in the sample I gave. I cannot yet make that work in conjunction with the row buttons so something else is amiss.

[MikeC]

Re: Verification of Issue

Got it to work but only by completely eliminating the prior button. It seems that there is some code remnants that cannot be gotten rid of...in fact I had to use the default "Event1" for the prior button that I had completely eliminated (and database compact) in order to get it working.

If I can get a reproducible scenario I will repost again for verification....but is nice that I can get it working nonetheless!!

Thanks again Tim--you sure saved me a bit of time on this one.

[Tom Cone Jr]

Re: Verification of Issue

Tim, I wonder if you could extend Mike's example to illustrate how to trap the OnChange event for the Address column in his browse? Thanks. -- tom

[MikeC]

Re: Verification of Issue

Hi Tom,
The OnChange is fairly straightforward in that using what is given in the What's new for version 8 works---I cannot get the CanSave event to work however which is the third function available.

FUNCTION Address1_OnChange AS V ()

gvRec=recno()
msgbox("OnChange record number is "+gvRec)

END FUNCTION

So like the _Buttonclick() function, you just add the field's object name in front of the prefix.

[Tom Cone Jr]

Re: Verification of Issue

Mike, thanks. I was hoping for a specific example because of uncertainty concerning the parameter list that must (?) be passed to the function. I also thought it might be helpful to have the onChange, and both types of buttonclick functions illustrated in a single browse. Might be very useful addition to the code archive.

[MikeC]

Re: Verification of Issue

As far as I know there are no arguments for the OnChange function. My sample would not be the best way to show an example really as it has what are currently issues/bugs that I will be submitting again once the next patch is out (one of the verified "bugs" might be fixed then).

I agree though that with the documentation being as it is, a sample in the Code Archive is a good idea....maybe once the CanSave event has been figured out as well, my sample can be cut up and used.

[MikeC]

Re: Verification of Issue

My mistake regarding the new version 8 CanSave (and also OnSave) event---this is not a column event but a browse event and is listed amongst all the other standard browse events...so nothing more to figure out I guess.

One thing I noticed though, which is a bit limiting, is that when the browse row's display properties are modified it no longer allows the data to be changed (from within the browse)---so is a display only situation.