Hi,
I confirm the bug. I found a rough workaround but as it's the first time I look into Parley's code, use at your own risk! I'm quite sure it breaks something else. Still it can help the debugging.
I have modified the lines 41 to 52 in flashcarmodewidget.cpp, commenting out everything related to Latex Renderer, see below:
Before doing this, I noticed that mixedlettersmodewidget.cpp had a setSolutionFont function but not a setQuestionFont one.
I tried to mimic the setSolutionFont code into a setQuestionFont code; not sure it is necessary or appropriate.
After doing this, I can use Kde system settings to change the fonts, and the question font changes (sometimes in a weird way: it does not always stay correct I think).
Hi,
I confirm the bug. I found a rough workaround but as it's the first time I look into Parley's code, use at your own risk! I'm quite sure it breaks something else. Still it can help the debugging.
I have modified the lines 41 to 52 in flashcarmodewid get.cpp, commenting out everything related to Latex Renderer, see below:
void FlashCardModeWi dget::setQuesti on(const QVariant& question) >questionLabel- >setMinimumSize (QSize( 0, 0)); :isLatex( question. toString( ))) { atexRenderer) { Renderer = new LatexRenderer( this); Renderer- >setResultLabel (m_ui-> questionLabel) ; Renderer- >renderLatex( question. toString( ));
m_ui-> questionLabel- >setText( question. toString( ));
{
m_ui-
// if (LatexRenderer:
// if(!m_questionL
// m_questionLatex
// m_questionLatex
// }
// m_questionLatex
// } else {
// }
}
Before doing this, I noticed that mixedlettersmod ewidget. cpp had a setSolutionFont function but not a setQuestionFont one.
I tried to mimic the setSolutionFont code into a setQuestionFont code; not sure it is necessary or appropriate.
After doing this, I can use Kde system settings to change the fonts, and the question font changes (sometimes in a weird way: it does not always stay correct I think).
Hope this helps!
mayeulk