Hi Fang, for the trivial case of non complex languages we have the glyph as the key and the mapped value is the flash id of the created geometry inside the flash document. For complex languages we have the problem that the glyph does not map to only one geometry. So we must create the PolyPolygon each time we have a glyph of text. But we do not want to store the same PolyPolygon again and again. And as you can see in the flash documentation, you can once define a geometry and later reference it by a flash id. So the key to that cache is actually the PolyPolygon itself and the mapped value is the flash id. Since this map is only useful for flash, just put it next to the filter code.
Regards, Christian Fang Yaqiong wrote: > Hi Christian, > Before the labor day, I sent you an email. Then I was on my vocation. But > today I find > that I maybe sent it to a wrong one. > > I will continue with the flash export. I looked at the codes. I think that > maybe we > can new a map to resolve the problem. We can store the polygons in the map, > just > like "Writer::defineBitmap()". How do you think about it? > > Then the problem turns to what is the key and what is the mapped value? And > where > suitable to new the map? Can you give me some suggestions? > > Sincerely, > Fang > > -- Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht Muenchen: HRB 161028 Geschaeftsfuehrer: Marcel Schneider, Wolfgang Engels, Dr. Roland Boemer Vorsitzender des Aufsichtsrates: Martin Haering --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
