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 selection not working (From SF #129) #23

Closed
wbrenna opened this issue Sep 9, 2013 · 6 comments
Closed

Font selection not working (From SF #129) #23

wbrenna opened this issue Sep 9, 2013 · 6 comments
Labels

Comments

@wbrenna
Copy link
Contributor

wbrenna commented Sep 9, 2013

for Xournal++ 0.9.1
There seems to be no effect from Tools > Text Font. It neither changes the font of subsequent text input, nor does it change the font of a selected bit of text.
The only way I find to change font, is by editing it manually in ./xournalpp/settings.xml. But that just changes the default font, and does not allow for comfortably using multiple fonts in one document.

@wbrenna
Copy link
Contributor Author

wbrenna commented Sep 9, 2013

This bug does not appear for me on Fedora 15, though I do get a PANGO warning:

(xournalpp:11126): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='common'

@wbrenna
Copy link
Contributor Author

wbrenna commented Oct 19, 2013

I can't replicate this problem so I'll close this for now.

@wbrenna wbrenna closed this as completed Oct 19, 2013
@wbrenna wbrenna reopened this Dec 23, 2013
@x2b
Copy link
Contributor

x2b commented Dec 30, 2013

I think that the callback is not connected properly. This should work as a fix:

x2b@546fbbc

@wbrenna
Copy link
Contributor Author

wbrenna commented Dec 31, 2013

Putting this fix into the next commit (I still can't replicate this bug so hopefully someone else can check).

PS What did you use to alter the indentation in your commit x2b/xournalpp@282ef2788, @x2b? I can't easily patch it into master because it was applied to addpoppler, and because of that git am is breaking on all of your patches. Probably just doing what you did on master will catch things up.

wbrenna added a commit that referenced this issue Dec 31, 2013
@x2b
Copy link
Contributor

x2b commented Dec 31, 2013

Well, as I mentioned in the commit, I used "artistic style" (http://astyle.sourceforge.net/):

astyle --recursive "*.h" "*.cpp" --style=allman \
                                 --indent=tab \
                                 --indent-namespaces \
                                 --indent-preprocessor \
                                 --indent-col1-comments \
                                 --min-conditional-indent=0 \
                                 --pad-oper \
                                 --align-pointer=type \
                                 --align-reference=type \
                                 --break-after-logical \
                                 --max-code-length=80 \
                                 --max-instatement-indent=120

I think it is a quite powerful tool. I generally work alone on software projects, I realize now that unilaterally changing pretty much every single file might not have been such a good idea...

However, I would still like to fix those insane includes (#include "../../model/PageRef.h"). I think this can be done automatically as well.

@wbrenna
Copy link
Contributor Author

wbrenna commented Dec 31, 2013

You're right, I'm impressed with astyle. If you find the command to fix includes let me know and I can apply it starting from master to avoid merge conflicts!

I'll take your word that this callback was a fix for the font problem and close this bug.

@wbrenna wbrenna closed this as completed Dec 31, 2013
@wbrenna wbrenna removed this from the Xournalpp 1.0 milestone May 17, 2014
@yasmah74 yasmah74 mentioned this issue May 18, 2023
@Samanbaia Samanbaia mentioned this issue Jul 22, 2023
@opaluja opaluja mentioned this issue Aug 3, 2023
@bmany bmany mentioned this issue Aug 4, 2023
@rschram rschram mentioned this issue Oct 26, 2023
@majorace majorace mentioned this issue Apr 9, 2024
@01-1 01-1 mentioned this issue Apr 20, 2024
@IlyaSulli IlyaSulli mentioned this issue May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants