[Xerte] FW: Transition setup?
Dave Burnett
d_b_burnett at hotmail.com
Tue Nov 17 23:00:37 GMT 2009
Good thought.
Yep, that seems to function as expected.
I removed the default fontsize from the LO and the transition from the icon itself.
Does that point to anything?
A transition applied directly to the icon is executing prior to the css render?
Subject: RE: [Xerte] FW: Transition setup?
Date: Tue, 17 Nov 2009 21:59:47 +0000
From: Julian.Tenney at nottingham.ac.uk
To: xerte at lists.nottingham.ac.uk
did you try running the transition using a button after the text has rendered? Create an ad-hoc button, add a script to iconID.wipe(...blah...) and then click it once the text has been rendered? Does that make any difference?
From: xerte-bounces at lists.nottingham.ac.uk on behalf of Dave Burnett
Sent: Tue 17/11/2009 17:29
To: Xerte list
Subject: RE: [Xerte] FW: Transition setup?
Excellent. Cheers!
Still wish I could figure out why the css is ignored by the transition engine.
Setting the default font to the largest used in the piece lets the transition function, but of course on smaller fonts it still thinks the area is much larger.
The effect is that the same transition applied to smaller fonts appears to move much slower. (As it is wiping a non-text area for a while before it hits the visible text.)
It must be ignoring the css font def, and uses the default text size it it's place.
Couldn't reproduce in Flash, and not a peep out of the Flash lists I queried.
Subject: RE: [Xerte] FW: Transition setup?
Date: Tue, 17 Nov 2009 09:56:07 +0000
From: Julian.Tenney at nottingham.ac.uk
To: xerte at lists.nottingham.ac.uk
OK, got it.
Download the latest build from the website.
Create a new piece.
Add script
trans = "wipe('in', 2, 'None', 'easeNone',2)" ; //so you can define popular transitions upfront and reuse them throughout the piece
then in the transition field of the icon put {trans}
cheers,
From: xerte-bounces at lists.nottingham.ac.uk [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Julian Tenney
Sent: Tuesday, November 17, 2009 9:44 AM
To: Xerte discussion list
Subject: RE: [Xerte] FW: Transition setup?
Hmm. Not easy to add the variable route. Either set the icon proeprties ahead of time, or call IconID.wipe(…) afterwards. You can call the transitions dynamically afterwards iconID[‘wipe’](..blah..);
Have you tried you transition sometime after the icon has rendered? Is it a timing issue – i.e. the tranition is being called before the screen has updated with the textField’s contents?
From: xerte-bounces at lists.nottingham.ac.uk [mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Dave Burnett
Sent: Monday, November 16, 2009 9:27 PM
To: Xerte list
Subject: RE: [Xerte] FW: Transition setup?
Cool, but I guess that means I have to pop a script icon above each icon I want to transition:
icon.nextSibling.attributes.transition = trans_var;
Subject: RE: [Xerte] FW: Transition setup?
Date: Mon, 16 Nov 2009 21:15:40 +0000
From: Julian.Tenney at nottingham.ac.uk
To: xerte at lists.nottingham.ac.uk
At the minute it takes a string, but you can set what that string is:
icon.nextSibling.attributes.blah = "my value for the icon's property when it gets parsed"
From: xerte-bounces at lists.nottingham.ac.uk on behalf of Dave Burnett
Sent: Mon 16/11/2009 20:24
To: Xerte list
Subject: RE: [Xerte] FW: Transition setup?
Well, I asked about it in a couple Flash type places and got no response, so I went back to brute force and discovered:
If I set the default font size on the LO to the largest I'm using in the CSS, the transition works on all fonts that size and below.
??
and
This alters the speed of the transition. (I guess it thinks it is dealing with that larger size font).
Which leads me to the next question:
Can I use a variable in the icon "transition" parameter?
I've tried a bunch of variations and no go.
No way to even "eval" a variable into that spot?
Dave
Subject: RE: [Xerte] FW: Transition setup?
Date: Sat, 14 Nov 2009 21:49:43 +0000
From: Julian.Tenney at nottingham.ac.uk
To: xerte at lists.nottingham.ac.uk
I dunno.
This si what the engine does:
if (transition != undefined) {
script(this+'.'+transition, engine);
}
so that basically runs the script iconID.wipe(...blah...), which is here:
IconID.wipe:
ICON.prototype.wipe = function(dir, duration, easing, easeType, startPoint) {
var direction = dir == 'in' ? Transition.IN : Transition.OUT;
var tween = TransitionManager.start(this, {type:Wipe, direction:direction, duration:duration, easing:mx.transitions['easing'][easing][easeType], startPoint:startPoint});
tween.mc = this;
tween.onMotionFinished = function(){
this.mc.broadcast('onMotionFinished');
}
};
After that? I haven't a clue.
I would build a very simple Flash file, recreate the situation ( a text field in a movie clip with your styled test in, and then wipe that) and find out if transitionManager fails even when it's not suppposed to, before you take it any further. Take Xerte (and everything else) out of the picture. I don't think this is a Xerte problem, as Xerte doesn't really do much other than act to pass on the transition to the transition manager - check the values of the parmeters getting sent?
From: xerte-bounces at lists.nottingham.ac.uk on behalf of Dave Burnett
Sent: Sat 14/11/2009 15:19
To: Xerte list
Subject: RE: [Xerte] FW: Transition setup?
Forget the .fla, I found it in google code.
The AS is over my head, but as far as I can make out:
The transition AS files get imported.
The guts are in
Transition.as
TransitionManager.as
They seem to use getcontent() as one of the means of determining the area to be affected. An overlay clip is built and that is what is erased off.
So the overlay is being built to the correct size, but the erasure function is using some other value, not completing the "wipe" of the overlay.
Any Flashmeisters care to tell me how far off base I am before I start fatfingering class files?
;-)
Subject: RE: [Xerte] FW: Transition setup?
Date: Fri, 13 Nov 2009 21:23:51 +0000
From: Julian.Tenney at nottingham.ac.uk
To: xerte at lists.nottingham.ac.uk
Interesting. I'm not a big user of styles as we tend to use the default interface.
In this situation, I would open up the XMLEngine.fla, look into how the transition works, put some debug statements in there and see what things look like as it runs, and see what I can figure out...
From: xerte-bounces at lists.nottingham.ac.uk on behalf of Dave Burnett
Sent: Fri 13/11/2009 17:34
To: Xerte list
Subject: [Xerte] FW: Transition setup?
Gaa.
I found it.
Plain text works fine.
Text tagged with html tags works fine.
However, if I use a CSS style tag, the transition only covers the area where text would have been without any formatting e.g. the default text face/size.
Reproducible?
Dave
From: d_b_burnett at hotmail.com
To: xerte at lists.nottingham.ac.uk
Subject: Transition setup?
Date: Fri, 13 Nov 2009 08:19:17 -0500
First crack at transitions.
Text icon, transition property added.
wipe('in', 1, 'None', 'easeNone', 2);
(the Help file example)
Transition reveals 3/4 of text block then halts.
Tried a few variations, other transitions, same result.
??
Dave
Bing brings you maps, menus, and reviews organized in one place. Try it now.
Windows 7: Unclutter your desktop. Learn more.
Hotmail: Trusted email with Microsoft's powerful SPAM protection. Sign up now.
Hotmail: Trusted email with powerful SPAM protection. Sign up now.
Hotmail: Free, trusted and rich email service. Get it now.
Hotmail: Trusted email with Microsoft's powerful SPAM protection. Sign up now.
_________________________________________________________________
Windows 7: It works the way you want. Learn more.
http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen:112009v2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.nottingham.ac.uk/pipermail/xerte/attachments/20091117/faa30435/attachment.html
More information about the Xerte
mailing list