Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Bug / Improvement) hardcoded text height #21

Open
danilogr opened this issue May 18, 2021 · 1 comment
Open

(Bug / Improvement) hardcoded text height #21

danilogr opened this issue May 18, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@danilogr
Copy link

It seems that the location of the buttons, grids, and pretty much everything is hard-coded to questions with a single line of text.
For example, I tried to add the full NASA TLX question to the NASA TLX questionnaire that comes with VRQuestionnaireToolkit and this is what I got:
image

As looked further into the source code, it seems that all content-generation behaviours rely on a hard-coded value for the text height:
image

Is there an easy way to fix this? I have hard-coded a longer length per question to solve my problem, but I think that it would be great if the authors of this toolkit made it flexible enough to support multi-line questions. This is especially important for validation because the real NASA TLX has longer text descriptions that matter. I.e., the shortened NASA TLX in use by this toolkit hasn't been validated.

@MartinFk MartinFk self-assigned this May 19, 2021
@MartinFk MartinFk added the enhancement New feature or request label May 19, 2021
@MartinFk
Copy link
Owner

I completely agree, this is kind of a legacy issue. When I originally developed the toolkit for myself, I had a pretty hard time dealing with Unity3D´s dynamic layouting system. There were many non-trivial issues which I could not sufficiently resolve in time. Eventually I gave up and just worked with fixed offsets. All standard question types should support at least(!) two-line questions (except the NASA, because the layout was specifically generated for it, as mentioned in the documentation).

That being said, it has been on our list for quite some time, and we plan to release a more dynamic UI layout with version 2.0. However, this unfortunately requires some major changes, and will most likely not happen before the end of summer.

Thank you very much for bringing it up, your feedback helps us to prioritize tasks and improve the toolkit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants