Action Script: Copy Previous Field/Record

[forskare]

Re: Action Script: Copy Previous Field/Record

Yes, you are correct. This 'smells' like a job for Clifton. After all, it did go past him before being released. I think he needs to re-sniff the issue.

[GGandhi]

Re: Action Script: Copy Previous Field/Record

I don't think this is really a bug or a problem, in my opinion
in a form when you have five fields and want to enter data and the fields are in focus consecutively and the entry takes place without a flaw.
however when you press the button the focus shifts to that button and alpha cannot copy that button since it is not a field nor does it have a previous value.
but if you add in your actionscript
object, activate and then select the field you want to activate, then the second action
records, copy previous field
(you can repeat as many time you want for other fields in the form)
the previous value will be copied, I think while you are in the entry mode.
so it is a matter of telling alpha what to do.
I think that is what happens if you have a button that copies the whole record all the fields are copied without any problem.

on a philosophical note, when you have a button and use it to copy previous value, you need to remember what the previous value was.
when you have multiple entries you may forget what it is at that time.
if you have a default value to copy on arrival you may be able to override if you do not like that value.

[G Gabriel]

Re: Action Script: Copy Previous Field/Record

It's a docs bug.
After a little correspondence with Selwyn, here is the latest:
Selwyn tested it in v12 and reported that it works fine. I asked him if he could test it in v11, he did and also reported that it worked fine.
so, I was trying to remember how I reproduced the error and managed to reproduce it again.
Here is the latest email to Selwyn:

Selwyn:
I think it's a docs bug.
The docs aren't clear on how to use it.
I did more testing and found out the following:
Use the same example you have, but place 2 buttons on the form:
One button with topparent.new_record() only
and the other topparent.copy_prev_field()
If you put the form in "Enter" mode and
Now, if you click the first button and start a new record
then
click the second button to copy the prev field value, you will get the error.
If you start a new record by pressing the "New Record" icon from the toolbar, again, same error.
In other words, these whole sequence of starting a new record, placing the focus (via code) in the desired field and copy the previous value, all has to occur without any user interruption of manually placing the focus in a certain field.
Thanks

[forskare]

Re: Action Script: Copy Previous Field/Record

What do you mean by "Docs bug"?

[G Gabriel]

Re: Action Script: Copy Previous Field/Record

Improperly (inadequately) documented in the Help file.

[forskare]

Re: Action Script: Copy Previous Field/Record

Improperly (inadequately) documented in the Help file.

Not sure I would call that a bug for two reasons. Inadequate docs is more of a poor documentation issue which is not unusual. Additionally, it's also the action script which has nothing to do with documentation. It is the code entered by Alpha. I have no idea what builds Selwyn is using but as mentioned in this thread, it also rears it's ugly head with v12. Maybe Selwyn , or you if he told you what/how he did it, would let us know what was done to get it to work?

[G Gabriel]

Re: Action Script: Copy Previous Field/Record

I already mentioned it before.
In my original response, or the second, I mentioned giving focus back to the field before using topparent.copy_prev_field().
In my first email to Selwyn, I used a code where you, via xbasic, enter a new record, give focus to the field then use topparent.copy_prev_field().
He tried what I submitted to him and it worked for him in those versions, 11 & 12.

I was a bit baffled, how come I got the error and he didn't.
I tried it in v8 and it worked.
So, I backtracked and realized that, in my testing I had it broken down in two buttons: One starts a new record and another gives focus to the field and then copy the prev value.
But also, in my testing, I changed the focus from one field to another before clicking the second button. Under this scenario, you get the error. But, if you do it without user interference as in:
xbasic:
start a new record (now you are in Enter mode)
Give focus to the desired field
Copy prev value.
It works without errors.That's what I submitted to Selwyn and that's what he tested.

If you manually give focus to a field, it throws the error.
The document ion does not say any of that, it simply says if you have this code (topparent.copy_prev_field()) on a button, it will copy the previous value.
Does not mention any of these qualifications, hence at best, it's lacking.

topparent.new_record() 
your_field.activate()
topparent.copy_prev_field()

It will work as such.
But, if you change the focus around to a different field, it won't work

[forskare]

Re: Action Script: Copy Previous Field/Record

G,

Thank you for your explanation. I added a couple rows of code to allow another field to copy as well.

topparent.new_record()
Lastname.activate()
topparent.copy_prev_field()
Firstname.activate()
topparent.copy_prev_field()

Alternatively, using action scripting works quiet well too, as long as the proper sequence of events is used. This will work quite nicely for me. Thank you for your time and persistence in this.

[G Gabriel]

Re: Action Script: Copy Previous Field/Record

No problem, but I still don't like it because I wanted to make it more flexible such that when the user points to any field (that you might not have had programmed initially) will be able to copy the previous value which is still doable with a little bit of finagling.

[forskare]

Re: Action Script: Copy Previous Field/Record

As I think about this, it is a 3 step process, even doing it the manual way.

1. Enter new record mode.
2. Give the field focus (unless the first field is what should be copied)
3. Copy the previous field.

Once we realize the thought process, it's an easy thing to do and clearly the documentation is at fault.