unfortunately I experience some problems with the ScriptyFader action:
Some of the DIV boxes used for the fader contain “non-english” chars, which are replaced by question marks.
The fader’s DIV box is nested within an other DIV box. I’m not sure if this is the reason, but the fader effect shows up totally destroyed. The boxes are “jumping” from their location left on the page to their intended position first and then start to fade.
I wonder if there are some known errors, limitations or special instructions to take care when applying the fader action ?
You may need to change the page output setting from Automatic to Unicode, and see if that helps.
Walter
On Feb 12, 2012, at 3:44 PM, tobiaseichner wrote:
Hello,
unfortunately I experience some problems with the ScriptyFader action:
Some of the DIV boxes used for the fader contain “non-english” chars, which are replaced by question marks.
The fader’s DIV box is nested within an other DIV box. I’m not sure if this is the reason, but the fader effect shows up totally destroyed. The boxes are “jumping” from their location left on the page to their intended position first and then start to fade.
I wonder if there are some known errors, limitations or special instructions to take care when applying the fader action ?
just ran a few tests and as far as I know, Fader and Inline is not the best choice.
However try the following method:
Draw a HTML-item (as your fader-wrapper)
Pick up the HTML tool again and draw carefully your scripty fader div within the wrapper (the wrapper must be outlined blue during this method).
This is the semi-inline construction method that should (could) work however I recognized that fader seems to be a little bit queasy towards any inline methods.
“outlined blue” means non-CSS layout ? That would not work with the other components of the page, unfortunately.
Well, if anything goes wrong I may simply use the Carousel action, which could also work (just don’t like the rewind effect when the carousel is at the end of the cycle).
Okay… but then I don’t think that it will work (anyway, I’m going to give that a try this evening when I have more time).
Just to avoid another misunderstanding: You mean that the DIV containing the fader must be put within the main DIV ? That’s what I already tried, but give it another one your way.
Basically I don’t know why you’re after “inline-style”. The method I tried is:
Assumed you have a box-model layout, where you centered the page via DIV construction (and not the inspector) the only chance to work further is either DIV in DIV by in-click each DIV and insert → HTML).
This method does not work with FADER, cause Fader needs layered style.
But you can’t just throw a DIV onto your box-model, cause it has no orientation. So a workaround is, to carefully draw this Fader-element into a placeholder of your box-model to make it a child-box of the parent box.
This is what I meant, and this is what I see the only chance to combine FADER and Full inline box construction.
I also have the same problem with “non-english” chatacters using ScriptyFader. Only way how this problem can now be solved seems to be use Graphic text.
But, if anyone find a solution to this problem, I’m very pleased to hear about it!
Wow, you’re right. I’m having the same issue here as well. I’ll see what I can come up with. I’ve already tried a handful of other encodings, and can’t seem to get the issue to be resolved. It appears to be a JavaScript / Freeway thing, because the partial files are being written out without their Byte Order Marker, and so they are not being interpreted as UTF-8, even though they contain nothing but.
Walter
On Feb 14, 2012, at 6:57 AM, Peka wrote:
I also have the same problem with “non-english” chatacters using ScriptyFader. Only way how this problem can now be solved seems to be use Graphic text.
But, if anyone find a solution to this problem, I’m very pleased to hear about it!
Also I wonder why these files are residing at the page’s location and have not been placed within the ./Resources folder where all other files are located. Was there a special reason for breaking with the concept of using separate resource folders ?
