VLF-ONE Customize Logon Handler (solved)

[jyoung]

Trying to find more information on how to customize the UI for the logon handler. The docs keep pointing to the source of UF_OEXEC which in turn points me to here. https://docs.lansa.com/14/en/lansa048/i ... 8_8285.htm which tells me that it must have an ancestor of VF_AC026O.

Creating a panel that extends VF_AC026O I get

Code: Select all

function options(*DIRECT)
begin_com role(*EXTENDS #VF_AC026O) height(409) width(500)

define_com class(*ANCESTOR) name(#Panel_ChangePlatformP) width(486)
define_com class(*ANCESTOR) name(#Panel_Logon) width(486)
define_com class(*ANCESTOR) name(#ShowChgPswOption) width(488)
define_com class(*ANCESTOR) name(#ShowMessageText) width(487) top(381)

end_com

Not sure what to do with this so I searched the docs for VF_AC026O and came across this https://docs.lansa.com/14/en/lansa048/c ... 8_6045.htm which in turn says to ask on the forum for more details and examples.

Capture.PNG (10.34 KiB) Viewed 19611 times

This is what the default logon handler (VF_AC026O) looks like (we've added a header).

Capture1.PNG (65.17 KiB) Viewed 19611 times

I want to clean up the "Change Password" section to look a bit cleaner.
How do I go about doing that with the above code?

Thanks,
Joe

[MarkD]

Start with your own compent MYLOGIN (say) as:

Code: Select all

Begin_Com Role(*EXTENDS #vf_ac026O) Width(353) Height(396)
End_Com

Compile it.

Change your entry point form to use it instead of the default VF_AC026O …..

Code: Select all

#VLF_ONE.uInitialize Frameworkidentifer("VF_VLFONE_SYSTEM") Logonhandlerid(MYLOGIN) Passwordchangerid(UF_OLOGON) .... etc...

Compile it and check that your new MYLOGIN component runs okay.

Then you can make visual changes to its layout.

For example, I changed to this using the form painter:

Code: Select all

Begin_Com Role(*EXTENDS #vf_ac026O) Width(353) Height(404)

Define_Com Class(*ANCESTOR) Name(#OldPlatformP) Left(162) Top(6)
Define_Com Class(*ANCESTOR) Name(#OldPlatformPText) Width(89) Top(8)
Define_Com Class(*ANCESTOR) Name(#NewPlatformPText) Width(100)
Define_Com Class(*ANCESTOR) Name(#NewPlatformP) Left(162) Top(34)
Define_Com Class(*ANCESTOR) Name(#ConfirmNewPlatformPText) Width(148) Top(62)
Define_Com Class(*ANCESTOR) Name(#ConfirmNewPlatformP) Left(162) Top(60)
Define_Com Class(*ANCESTOR) Name(#Panel_Logon) Width(339)
Define_Com Class(*ANCESTOR) Name(#ShowChgPswOption) Width(341)
Define_Com Class(*ANCESTOR) Name(#Panel_ChangePlatformP) Width(339) Height(126)
Define_Com Class(*ANCESTOR) Name(#ShowMessageText) Width(340) Height(29) Top(387)
Define_Com Class(*ANCESTOR) Name(#ChangePlatformPButton) Left(74) Top(88) Width(209) Height(32)

End_Com

To get this:

capture1.png (20.95 KiB) Viewed 19602 times

There are limits to how much you can do this way, so it’s best to stick to just basic layout changes. Things like trying to change input field or button types, etc is likely to end up in a tangle.

[jyoung]

Thanks Mark,

Had a couple issues with the designer using Layouts, however when I used your example (without layouts) it worked great.

Thanks,
Joe