|
|
|
[
Permlink
| « Hide
]
Gaurav Jain - [08/21/07 09:53 AM ]
Tom, can you please attach the bug files.
Workaround is to define relative path in the source attribute of style element.
<mx:Style source="../diffSrcClass/extClassRefAS.css"/> will work. I don't think its a bug.
The documentation says that the value of source property is teh URL of a file that contains style declaration. i don't agree. One, "extClassRefAS.css" *is* a URL to a file that contains a style declaration. Two, this works if you put it in the first source path, just not the second. Three, it's obvious from the "workaround" that the compiler is only trying to resolve the relative URL from the first folder (diffSrcProj) and not the second one as it should.
>> this works if you put it in the first source path, just not the second.
Works because then the file location becomes relative to the mxml file. >> it's obvious from the "workaround" that the compiler is only trying to resolve the relative URL from the first folder (diffSrcProj) and not the second one as it should. If I change the example to move extClassRefAS.css from folder diffSrcClass to folder diffSrcProj and also move extDiffSrcASTest.mxml to a folder diffSrcProj/mxml and if I use the command mxmlc -sp=diffSrcProj diffSrcProj\mxml\extDiffSrcASTest.mxml It doesn't work even though the css is now in the first and only source path but not relative to the mxml. I totally do not follow that last comment from Gaurav. I believe the original steps demonstrate the bug. The mx:Style source path is a source-root-relative path. It should resolve regardless of which source path the css file is in and regardless of which one the mxml file is in.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||