thanks for all the work, but i hate this "desaturate" N8-like effect in the latest update, how can i go back to the -blur effect- version? can you give a choice to the user to choose or no this "black&white" effect?
I really dislike it :-(
I like it :P
Next update will have "more standard" transitions.ini bundled (blurless focus disabled, forcerotation disabled).
Heh, you can enable those by editing the file:
/opt/theme-customizer/transitions.ini
(end of the file)
And then run Theme Customizer again with reboot enabled to get those new settings activated ;-)
Later when I have time to finish my transitions.ini tuner, you can do all this inside Theme Customizer.
Heh, you can enable those by editing the file:
/opt/theme-customizer/transitions.ini
(end of the file)
And then run Theme Customizer again with reboot enabled to get those new settings activated ;-)
Later when I have time to finish my transitions.ini tuner, you can do all this inside Theme Customizer.
That's great. A simple GUI that is fast to use is just what I'd want.
/opt/theme-customizer/transitions.ini had the forcerotate =1 and X/Y = 1, the forcerotate was happening on my device after 12.1 update to the CSSU. Which I didn't like.
I changed the new CSSU transition options in /opt/theme-customizer/transitions.ini to 0, but after reboot via TC they still seem to be in effect.
Any ideas from you? I'm double checking everything but I found nothing out of place as of yet.
That's great. A simple GUI that is fast to use is just what I'd want.
/opt/theme-customizer/transitions.ini had the forcerotate =1 and X/Y = 1, the forcerotate was happening on my device after 12.1 update to the CSSU. Which I didn't like.
I changed the new CSSU transition options in /opt/theme-customizer/transitions.ini to 0, but after reboot via TC they still seem to be in effect.
Any ideas from you? I'm double checking everything but I found nothing out of place as of yet.
And after editing the file you had "use custom transitions" checked in Theme Customizer?
Check the contents of this file:
/etc/hildon/theme/transitions.ini
That's the one that's used (if it exists) by hildon-desktop.
Check the contents of this file:
/etc/hildon/theme/transitions.ini
cat: can't open '/etc/hildon/theme/transitions.ini': No such file or directory
Because I didn't select your 'use custom transitions'. I understood that /etc/hildon/theme/ is always the current themes' folder.
Imma try that next.
/usr/share/hildon-desktop/transitions.ini should be the default that is used when /etc/hildon/theme/transitions.ini isn't specified. It has the settings I'd like as well.
I've never selected that option. I'm thinking I try after the edits, so they'll get written.
cat: can't open '/etc/hildon/theme/transitions.ini': No such file or directory
Because I didn't select your 'use custom transitions'. I understood that /etc/hildon/theme/ is always the current themes' folder.
Imma try that next.
/usr/share/hildon-desktop/transitions.ini should be the default that is used when /etc/hildon/theme/transitions.ini isn't specified. It has the settings I'd like as well.
This is getting stranger by the minute... =D
Nono, it's very simple. If you didn't choose to use custom transitions then it doesn't matter what's in /opt/theme-customizer/transitions.ini
Just make sure that there's no transitions.ini under /etc/hildon/theme and then the system will use one located at /usr/share/hildon-desktop/transitions.ini
But if the forcerotate still kicks in, then it must be bug with cssu.
I like it :P
