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

v1.0.0 Title gets cut off #96

Closed
DragonSlayer88 opened this issue Sep 17, 2021 · 8 comments
Closed

v1.0.0 Title gets cut off #96

DragonSlayer88 opened this issue Sep 17, 2021 · 8 comments

Comments

@DragonSlayer88
Copy link

Title gets cut off if its too long. There is still space as I have no subtitle. Can this be expanded?

Also title max lines does nothing. If i set that to 2 or anything really, it doesnt work.

@RemcoSchrijver
Copy link

+1 I have the same problem, would be great if this get's fixed.

@fumin65
Copy link

fumin65 commented Sep 21, 2021

This problem seems to have been fixed in v1.0.1.
However, it has not been deployed to pub.dev yet.

#93

@SylvainFlattet
Copy link

Any clue when 1.0.1 will be released?

@malikdoksoz
Copy link

malikdoksoz commented Nov 13, 2021

settings_ui:
    git:
      url: https://github.com/yako-dev/flutter-settings-ui.git
      ref: master

You can use it like this
The new version does not appear in pub.dev. Needs to be fixed.
don't forget to run flutter clean command

@fredecodes
Copy link

No, you just need to reference the new package, which is called flutter_settings_ui:
flutter_settings_ui: ^2.0.1

@malikdoksoz
Copy link

No, you just need to reference the new package, which is called flutter_settings_ui: flutter_settings_ui: ^2.0.1

I mentioned this package. (settings_ui)

@fredecodes
Copy link

This problem seems to have been fixed in v1.0.1. However, it has not been deployed to pub.dev yet.

#93

Did you test this and verify that it is fixed? I am still seeing this bug with latest code on master (after manually applying the ListThemeData compile fix needed for Flutter 2.8). Note that this bug was originally submitted awhile ago (see #78) and marked as fixed but doesn't appear that it actually was fixed.

@yadaniyil
Copy link
Contributor

Hey @DragonSlayer88 @RemcoSchrijver @fumin65 @sylvain-flt @malikdoksoz @fredecodes . There is a new 2.0.0 version of the package, could you please if your issue is fixed there? Thanks :)

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

No branches or pull requests

8 participants