Rafael Copquin wrote on 2013-12-10:
> Thanks for your response, Tracy
> I just don't see the point of using writemethod the way you used it in
> the past. Would it not be simpler to just clicking on the click event
> and write or paste the code?
>
> But that is not what I need anyways. I just need to be able to send code
> to the click methods of buttons in a commandgroup as parameters, since I
> do not know how many buttons there will be.
>
> Rafael
>
Rafael,
For that little bit of code, yes.
That was very simplified. I had used it to globally overwrite some base
class code in certain class types from the command line many moons ago.
Thinking about this, I actually do use this in our build system. I've pulled
out an IF statement and changed a few things.
MODIFY CLASS myclass OF mylibrary NOWAIT
ACTIVATE WINDOW "Class Designer -"
=ASELOBJ("laForm", 1)
laForm[1].WriteMethod("methodname", "* New method code")
SYS(1500, "_MFI_SAVE", "_MFILE")
SYS(1500, "_MFI_CLOSE", "_MFILE")
IF WEXIST("Class Designer -")
RELEASE WINDOW "Class Designer -"
ENDIF
Tracy Pearson
PowerChurch Software
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
