cannot make a question mandatory (not optional) - also no back button

[appliedrd]

example.
Next button starts grey, then goes active within 1 second.
Doesnt matter if optional: false, or commented out
For now, I have reverted back to https://github.com/appliedrd/research.package.git branch: realign

List likert7PointAgreeChoices = [
RPChoice(text: "Strongly disagree", value: 1),
RPChoice(text: "Disagree", value: 2),
RPChoice(text: "Somewhat disagree", value: 3),
RPChoice(text: "Neither agree or disagree ", value: 4),
RPChoice(text: "Somewhat agree", value: 5),
RPChoice(text: "Agree", value: 6),
RPChoice(text: "Strongly agree", value: 7),
];

RPChoiceAnswerFormat likert7PointAgreeChoicesAnswerFormat = RPChoiceAnswerFormat(
answerStyle: RPChoiceAnswerStyle.SingleChoice,
choices: likert7PointAgreeChoices,
);

RPQuestionStep s2_1 = RPQuestionStep(
identifier: "s2_1",
title: "1. Overall, the workshop was easy to understand.",
// optional: false,
answerFormat: likert7PointAgreeChoicesAnswerFormat);

[appliedrd]

also no back button

[mario-bermonti]

I can confirm this. I am on version "1.5.0" of the research_package.

Is this the intended use of the optional parameter when creating RPQuestionSteps? I was reviewing the code and am not clear anymore. Setting optional to true adds a button to skip the question (first code chunk below). This button calls the skipQuestion, which sets the result to null and continues to the next step (second code chunk below). However, none of this code disables the "next button".

// question_step.dart

widget.step.optional
    ? TextButton(
        onPressed: () => skipQuestion(),
        child: Text(locale?.translate("Skip this question") ??
            "Skip this question"),
      )
    : Container(),

// question_step.dart

  void skipQuestion() {
    timer?.cancel();

    FocusManager.instance.primaryFocus?.unfocus();
    blocTask.sendStatus(RPStepStatus.Skipped);
    currentQuestionBodyResult = null;
  }

[mario-bermonti]

I was able to figure out the reason why the next button appears after one second and was able to fix it in my fork of the research_package (see changes).

I am happy to submit a pull request, but want to make sure this is the intended use first. Could any one confirm?

[mario-bermonti]

Could I get your input on this, @bardram?

[bardram]

Sorry @mario-bermonti - I wasn't following this package closely, so didn't see your comments. But if the small change above fixes the problem, please make a PR on the current master branch and I can take a look.

[mario-bermonti]

Great! It is a little busy for me right now because the semester just started, but I will submit a PR soon.