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

Font selction is limited - please allow us to use any installed font #1908

Closed
NiklasBr opened this issue Feb 14, 2020 · 11 comments · Fixed by #2420
Closed

Font selction is limited - please allow us to use any installed font #1908

NiklasBr opened this issue Feb 14, 2020 · 11 comments · Fixed by #2420
Labels
🔭 area/editor 🐛 bug Something isn't working 🔍 needs further investigation This issue needs further investigation.

Comments

@NiklasBr
Copy link

Describe your feature request

Ability to select any operating system installed font

Additional context [optional]

Currently only a few fonts are available for selection, but I would like to use any of my installed fonts for rendering the document.

@Jocs
Copy link
Member

Jocs commented Feb 16, 2020

@NiklasBr You can try the 0.16.0-rc.2, it support system installed font.

@NiklasBr
Copy link
Author

@Jocs I could get it to work for Code Blocks, but I am unable to click and change the font in any way for the regular editor. See screen shot below, green square: clickable, red square: not clickable.

Screenshot (3)

@Jocs
Copy link
Member

Jocs commented Feb 16, 2020

@NiklasBr What's you Mark Text version?

@Jocs
Copy link
Member

Jocs commented Feb 16, 2020

截屏2020-02-16下午10 10 23

  1. Clear the selected font in the input.
  2. You'll the the options...

version: 0.16.0-rc.3

@NiklasBr
Copy link
Author

  1. Impossible because it is not clickable, see the screen shot above.
  2. I'll what?

I'm using v0.16.0-rc.3

@NiklasBr
Copy link
Author

Re-installed 0.16.0-rc.3 but still experiencing this. I can actually write whatever I want in the font block input field (why isn't it a regular drop-down by the way?) and if I spell a font correctly it works.

Still not able to use the regular editor to choose a different font.

@fxha
Copy link
Contributor

fxha commented Feb 21, 2020

@Jocs I can confirm this issue. I just build v0.16.0-rc-3 from develop (1c5b714) and the font family "list" only contain the selected font family without any logged errors. rc-2 (develop, custom build) from 30 January worked correctly.

@fxha fxha added 🐛 bug Something isn't working 🔍 needs further investigation This issue needs further investigation. 🔭 area/editor labels Feb 21, 2020
@fxha fxha added this to TO-DO in 0.16.0 Feb 21, 2020
@Jocs
Copy link
Member

Jocs commented Feb 23, 2020

and the font family "list" only contain the selected font family without any logged errors.

@fxha @NiklasBr Can you see all the installed fonts in the drop down if you clear the selected font family?

I'll what?

You can see the installed font family options.

@fxha
Copy link
Contributor

fxha commented Feb 23, 2020

Can you see all the installed fonts in the drop down if you clear the selected font family?

@Jocs You're right, the UX is very bad because the list is filtered. We should instead show all font families by default and only filter if the user types, otherwise it might be confusing. But I don't know whether @NiklasBr has the same issue, at least for me, the drop down list is always shown.

@NiklasBr
Copy link
Author

@NiklasBr Can you see all the installed fonts in the drop down if you clear the selected font family?

No, beucase it acts as a text input field, not as a dropdown. Clicking on the chevron does nothing. There is no dropdown anywhere when I click on it (as I expect it to be). It seems to detect the fonts if I spell them correctly though.

@fxha fxha removed this from TO-DO in 0.16.0 Mar 17, 2020
@NiklasBr
Copy link
Author

I installed v0.16.1 and the issue persists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔭 area/editor 🐛 bug Something isn't working 🔍 needs further investigation This issue needs further investigation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants