Modernflyouts: Feature Request: tell users what the default flyout timeout is

[Poopooracoocoo]

Is your feature request related to a problem? Please describe:

If you change the flyout timeout you don't know what the default is

Describe the solution you'd like:

A little i icon with a tooltip like the default flyout position

Describe alternatives you've considered:

A reset button

Put the default in the description of the setting: "Flyout timeout (ms) (default: 2750)" (or something like that)

Additional context:

ModernFlyouts version: 0.8.0.1
Windows 10 version: 20H2

[Samuel12321]

Agreed, very easy to fix.

[ShankarBUS]

Ever used properties tool window in VS?

If a property's value is changed from default, it will show the value in bold. After reverting it to default it will turn back to normal.

Would something like it be good?

[Cyberdroid1]

But a button to reset would be required, no?

[Samuel12321]

Even simpler solution would be to add [Default 2750] to the text above the box

[Cyberdroid1]

What about adding this text when the box is empty, as a hint in greyish color (I don't know what they are called).

[Poopooracoocoo]

@Cyberdroid1

What about adding this text when the box is empty, as a hint in greyish color (I don't know what they are called).

fyi those are called placeholders :) There are so many articles about forms. One I've read recently is this one: https://gerireid.com/forms.html

[ShankarBUS]

@Samuel12321,

Even simpler solution would be to add [Default 2750] to the text above the box

That wouldn't be good.

We can use placeholders though 🤷‍♂️.

[Cyberdroid1]

@Poopooracoocoo Thanks!

So, we can add placeholder text "2750".

[ShankarBUS]

@Samuel12321, we can also use ui:ControlHelper.Description for this purpose.

[Poopooracoocoo]

Would the default flyout position setting use a placeholder instead of a tooltip too?

[Cyberdroid1]

Would the default flyout position setting use a placeholder instead of a tooltip too?

I think no, as we have to tell the user how to type the position settings, as X,Y. I don't think it would be appropriate.

[ShankarBUS]

Unfortunately, "Placeholders" wouldn't work for number boxes (as the value has to be cleared to show the placeholder, they are only valid for textboxes).

We may need to use the description property for this. We can show something like "Default - 2750"
@Samuel12321, should we localize this one too?

[ShankarBUS]

What about this?

[Samuel12321]

Great, however probably best to be a bit clearer and change the star to "Default:"

[ShankarBUS]

The reason I chose a star instead of text is due to the struggle with the localization process!
We have to introduce a new entry just for this one and update all language resources simultaneously!

The default value could be changed internally and will easily be updated with this method.
However if we were to use a string we have to hard code this value (2750) into the multilingual resources. Thus, making it hard to update it in the future.
We can work this around by making the string like this "Default: {0}" (some cultures keep the numerical values first and description at last, it depends).

A star however is universally understandable to everyone and easy for us to maintain.

[Samuel12321]

good point.

[ShankarBUS]

So, Is it okay?
Shall I close this now?

[Samuel12321]

yes close and merge. 😁

[ShankarBUS]

Great!

Hey @Samuel12321,

Do you know what time it is 😁?????????????

[Samuel12321]

This means that V0.8.2 is done, WELL DONE EVERYONE.
Will release to beta testers soon.

Do you know what time it is?

Where?

[ShankarBUS]

Do you know what time it is?

It's 🥳 🎉 R E L E A S E T I M E!

Where?

Bruh!

This means that V0.8.2 is done, WELL DONE EVERYONE.
Will release to beta testers soon.

Was just about to say this!

[Samuel12321]

Oh, jokes on me. Totally misinterpreted that. :)

[Samuel12321]

Just waiting on your commit with the default flyout timeout.

[ShankarBUS]

Give me a minute 😅.
I didn't see you committed 3 commits to the origin. My local clone is messed. I will clean it up and commit the changes again.
It did 3 unnecessary merge commits due to the changes I made to the packaging project.

[ShankarBUS]

I guess we may have to do git rebasing once in a while. Not for now next month maybe?

Look at this abomination 🤣🤣🤣

[Samuel12321]

ouch

[ShankarBUS]

If I did merge the origin onto my local and committed it, it would look much worse. Nothing wrong on your side.
I should have pulled origin before committing it 😅.