Button changing states on Save status.

[preston2]

I have a button that runs calculations in a onpush event. I would like to remind users they need to click that button anytime they change some values on the form. Something like making the button green when they need to push it to recalculate the form and maybe grey when they do not. I have looked at using a conditional object with one color of the button for each condition but cannot find a way to have the condition track that the form has had changes keyed in and needs to be recalculated. Right now the built in Alpha Save button changes state based on if the data in the form is current and saved but I cannot find how or where that built in Save tracks the fact that the information on the form has changed and needs to be saved. Or could this possibly be done by tracking a table records event?

Any ideas would be appreciated.

[aschone]

Re: Button changing states on Save status.

Object Events - see the Events for Forms section. Should be something there that you can use.

To change the display of the button you can place an action script on the event you choose that will change the button color to your choice.

[preston2]

Re: Button changing states on Save status.

Object Events - see the Events for Forms section. Should be something there that you can use.

To change the display of the button you can place an action script on the event you choose that will change the button color to your choice.

I have looked into most of that and nothing seems to do the trick. The ones I did find where I could make it change the button color if some data changed only did the color changing after the changes where saved, not before.

Will keep looking.. If it can be done at all.

[preston2]

Re: Button changing states on Save status.

Ok, I think I have figured out a way. May not be the best and will require a lot of work but.

If I put something like this [ parentform:Button1.fill.color = "Red" ] on a fields "onchange" event and then add [ parentform:Button1.fill.color = "Green" ] to the button's "onpush" event it will work.

The hard part is having to put the first part on every object on the form I want to monitor.

[Nick Oldfield]

Re: Button changing states on Save status.

...in which case why do you need a button at all? Just trigger the recalculation in the "onchange" event...

[preston2]

Re: Button changing states on Save status.

...in which case why do you need a button at all? Just trigger the recalculation in the "onchange" event...

Because if I did that then it would recalculate and write several tables 80 or 90 times while they were filling out the form. Unless you know a way to have "onchange" know not to trigger the recalculate on a new record.

[Corelius]

Re: Button changing states on Save status.

Create a global variable, L_edit = .f.
setup a field rule record event on save
dim global L_edit as l
L_edit = .t.
use this global variabel L_edit for the dynamic properties, bold, color what ever.
When you push the button reset L_edit to .f.

I like to use the field event OnWroteField to trigger the recalculation. Also the OnDepart event of the embedded browse area can be use. Therefore I hide to total sum field by the OnArrive event to remeber the user to get out for the recalculation.

Cornelius

[Ray in Capetown]

Re: Button changing states on Save status.

Why not simply use <object>.mode_get()

[Corelius]

Re: Button changing states on Save status.

When you change the (invoice) header the recalculation is not necessary.

Cornelius

[Ted Giles]

Re: Button changing states on Save status.

This is yet another way. It's been posted before.
Try the Edit Names button.
There are other bits and pieces - like a dockable Navigation Bar - which you won't be interested in.

The Save button changes colour if a user changes anything in the Names table.

You can cut and paste the Conditional Object and place it on all of your forms. Just design it the way you want, once.

I often have a redundant Form, within which I create a style for Buttons and Menus. Then I just design once, and copy/paste with minimal coding for the non standard features. Helps keep a consistent approach for the user as the buttons will always be in the same place. Ones you don't need can be disabled and greyed out but still show.