I've been wrapping up a project for a furniture company in which one section of the site features numerous finish samples with text below.
It seems that the text is getting cut-off; but not on everyone's machine/internet connection. All of my machines show the text properly, my neighbor's laptop shows the text properly, but several test members on the client side cannot view the text without the end of long strings getting cut-off!?!?!
It's driving me crazy.
I'd be very appreciative if anyone here could take a look at the link below and/or download my .fla file and have a look. I've tried everything I know, but nothing is working. Thanks.
Have yoy tried making your text boxes longer? cause some of them are quite small only accomodating the selected current title. This can be why some text is getting cuff off. Try that first and let me know.
Have yoy tried making your text boxes longer? cause some of them are quite small only accomodating the selected current title. This can be why some text is getting cuff off. Try that first and let me know.
Good call. I actually did try that this morning and the client still reported a problem. I thought for sure that was it.
I even sent them a .swf file to try, and they did NOT report any issues with the .swf!? Bizarre. That truly leads me to believe it's something to do with viewing it a.) across the net and/or b.) viewing it across their network.
I wonder if a preloader is the answer? Perhaps the text just isn't loading properly.
What's also bizarre is that they click on a sample, the text is cut-off, but a second click fixes the problem. It's like that way on all the finishes that have rather long text descriptions.
are you using a ufo file to support your swf file on the net. If not I can supply one to you. You don't need to do anything to it other than linking it to your page.
Last edited by iHATEsushi; 01-25-2007 at 12:52 PM.
Here is the ufo file. Save it out as ufo.js and then save the .js file in your folder with your index.html page
/* Unobtrusive Flash Objects (UFO) v3.20 <http://www.bobbyvandersluis.com/ufo/>
Copyright 2005, 2006 Bobby van der Sluis
This software is licensed under the CC-GNU LGPL <http://creativecommons.org/licenses/LGPL/2.1/>
*/
expressInstallCallback: function() {
var _b = document.getElementsByTagName("body")[0];
var _c = document.getElementById("xi-con");
_b.removeChild(_c);
UFO.createCSS("body", "height:auto; overflow:auto;");
UFO.createCSS("html", "height:auto; overflow:auto;");
},
cleanupIELeaks: function() {
var _o = document.getElementsByTagName("object");
var _l = _o.length
for (var i = 0; i < _l; i++) {
_o[i].style.display = "none";
for (var x in _o[i]) {
if (typeof _o[i][x] == "function") {
_o[i][x] = null;
}
}
}
}
I'm guessing that it was the text box being too small and the clients computer is still using the old Flash file out of the cache. Have them clear the cache and try again.
Jason L. Wright
I'm not that hard to imitate. Just make some random negative claim at Apple or anything else for that matter and then have nothing to back it up.
Oh ok... I'm stumped... I tested it on all my systems here and they all work fine. Keep in mind they all have the latest Flash players, so it just might be ther version he's using. What size of monitor does he have or viewing it on, compared to the size your viewing it on. Here all our monitors are 19 inches and up.
Problem solved. Thought I'd post back here and give the solution in case anyone else has a similar problem.
The solution was two-fold:
1. Separate the image and the text onto different layers.
2. Put plenty of space between the individual sample/text keyframes.
BOTH of these needed to be done in order to completely get rid of the cut-off text problem.
Again, this problem was VERY regional. Only viewers in Minnesota seemed to be affected. I kid you not. I had people in NY, Los Angeles, London, Texas, Michigan, Chicago, and several other states/cities checking this out, but ONLY those folks in MN were affected. Mondo mondo MONDO bizarro. MN is, BTW, is where the company is located.
iHateSushi, your question about monitor size was a good one. Everyone from the MN area (at the company itself, and on their home PCs) reported the problem and, as you can imagine, the monitor sizes and types ran the whole spectrum. We had to therefore eliminate that as a potential problem.
This problem makes NO sense whatsoever. You shouldn't have to put spaces between keyframes. You should really have to separate text and images that share a keyframe. Yet, for those folks in MN, that's exactly what had to be done!