I also merge our fixed with css animate branch
ShikemokuMK/tyranoscript#40
because it wont work without them
and remove this line
if (key.indexOf("message") != -1) this.map_layer_fore[key].css("opacity", "")
in css animate branch.
I think it isn't used with css transitions.
And update main request
ShikemokuMK/tyranoscript#32
But there is another problem with css animations.
Because DOM objects with "transform3d" in chrome rendered at top, they shown at top of menu button.
And when I add
* {
/* transform and z-index conflict fix for Chrome */
-webkit-transform: translate3d(0px,0px,0px);
transform: translate3d(0px,0px,0px);
}
then 0-9 layers shown at top of message layer.
I think there should be other way... will think about it tomorrow.
Refactor transition branch still has some unresolved bugs.
Applying "translate3d(0px,0px,0px)" is bad fix. Somthing else needed.
That is abolut z-index, opacity and, probably, transform.
This is strange but if tyrano_base scaled <= 1 then animations are OK.
But if tyrano_base scaled > 1 then animated objects overlapping other.
Audio refactor branch
https://github.com/ValeryVS/tyranoscript/tree/refactor-audio
check commit message
ValeryVS/tyranoscript@c485f80
I will test last changes on android and make new features.
Questuion:
質問
Is it ok to use "variable.sf.settings.volume"?
"variable.sf.settings.volume"を使用して大丈夫ですか?
Now "this.variable.sf" is set three times in kag.js.
If we use "variable.sf.settings.volume" this should be refactored.
https://github.com/ValeryVS/tyranoscript/commit/c485f80f0b39f9b5fac672af89ee289186f7909a#diff-e6ecc5b1867ec8519179b9875b932672R38
https://github.com/ValeryVS/tyranoscript/commit/c485f80f0b39f9b5fac672af89ee289186f7909a#diff-e6ecc5b1867ec8519179b9875b932672L247
https://github.com/ValeryVS/tyranoscript/commit/c485f80f0b39f9b5fac672af89ee289186f7909a#diff-e6ecc5b1867ec8519179b9875b932672L329