From: dgurjar@codeaurora.org
To: edk2-devel@lists.01.org
Subject: Convention for creating dynamic HII forms
Date: Wed, 10 May 2017 14:38:36 -0600 [thread overview]
Message-ID: <847821b780b0848d92d7bfcd03ea3bcf@codeaurora.org> (raw)
Hi,
I was wondering if anyone here could provide some clarification on how
to create dynamic HII forms.
Currently I have a Form A with multiple goto statements to Form B.
When the user clicks a goto, my ConfigCallback function will use the
QuestionId to get the data to populate Form B with from a UEFI variable.
Form B's values appear to be updated when I use HiiSetBrowserData.
However, when I do this I notice that after the user modifies Form B,
the "Configuration Changed" string does not always appear. As a result
when I try to save the form, there are no calls made to my RouteConfig
function.
When I enter Form B the internal question values for that form are not
updated with the values. Because of this the form doesn't recognize when
its questions are modified.
I was wondering if anyone has had experience creating form where the
internal question values need to be modified on entry, and what the
common convention was for doing this.
Thanks,
Dev
next reply other threads:[~2017-05-10 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 20:38 dgurjar [this message]
2017-05-11 6:53 ` Convention for creating dynamic HII forms Dong, Eric
2017-05-18 15:35 ` dgurjar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=847821b780b0848d92d7bfcd03ea3bcf@codeaurora.org \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox