Problems at new Style configuration

[arvanus]

@Jdochoa could you take a look at the new style?
I got 2 minor issues from now, when I try to type a SQL, it always changes the keywords to mixed case, in the default behavior of flamerobin is to use uppercase for keywords, BUT I cant change the casing even when I retype the word, example "FROM", "FrOm", "fROm" always shows as "From"

Also, I opened the Style Configurator, scrolled a bit, saved, closed, reopened and got this error:

Thank you

[Jdochoa]

Hello @arvanus

The first thing is changed in: Style Configurator\SQL\KEYWORD\Font Case.

The second problem is because a style has not been selected.

See the image below

[arvanus]

It worked, looks like I needed to reopen Fr to refresh style config
Thank you! nice feature!

[luronumen]

Hi @arvanus

I am still facing the same issue even after installing it thru the new flamerobin-0.9.6-setup-x64.exe installer.
Is there any way for fixing it in manually?

Thanks in advanced,
Luciano

[andreschulle]

I am having the same problem @arvanus had. The font was blank, so I selected a font and saved, then an error said the access was denied. When executing Flame Robin as administrador, there's no error message, but preferences isn't saved.

It worked, looks like I needed to reopen Fr to refresh style config Thank you! nice feature!

I reopened the app, but the font field still appears blank.

[virgoparna]

Saving changes is not possible even after selecting style, because it tries to save to install location (%ProgramFiles%\Flamerobin\xml-styles\stylers.xml). i think that user changes should be saved somewhere at %appdata%\Flamerobin or %LocalAppData%\Flamerobin

[kalwados]

Is there a way to manually disable using styles until this issue is fixed?
I would like to change the SQL editor font to "Consolas" but SQL-Editor View->"Set editor font" does nothing (opens no font dialog), and MainWindow View->Preferences -> leads to error
"can't open file 'C:\Program Files\FlameRobin (x64)\xml-styles\stylers.xml' (error 5: Access denied)"

[virgoparna]

Seems to be fixed by 0.9.9 snapshot (be8c344). Probably by #330 pull request.