Thanks Thomas, but the title of bug3649 is "Combined Images are not
Automatically included in the Build".

I just want to make sure you noticed that the error is on *both* 'versions':
"source" _and_ "build", so this might be a little different issue
...just to make this clear.

I (will) add this as a comment to the bug, too

/Peter


On 2010-08-31 10:57 thron7 wrote:
> Yes, looks like a regression. I've reopened bug3649.
> 
> T.
> 
> On 08/27/2010 11:40 AM, Peter Schneider wrote:
>> Hi List (Hi Thomas ;) )
>>
>> I currently face an issue here. It seems that the generated code (neither
>> 'build' nor 'source' version) does not use the combined images...
>>
>> I am using qooxdoo 1.2.x version[1].
>>
>> Unfortunately I'm not sure since when it does not work anymore.
>>
>> To be on the 'clean' side I even did these steps:
>> - delete all *.pyc files from project
>> - run "generate distclean"
>>
>> - run "generate source" => no luck, the application doesn't use combined 
>> images
>> - run "generate build"  => no luck, the application doesn't use combined 
>> images
>>                            AND the combined resources are not copied to the
>>                            build folder...(regression of Bug #3649 ? [2] )
>>
>> Can someone check this on their side?
>> It looks like the whole thing is a regression of the issue discussed here:
>> http://qooxdoo.678.n2.nabble.com/image-combining-qooxdoo-1-1-pre-tp4969328p4969328.html
>>
>> Regards,
>>   Peter
>>
>>
>> [1] 
>> https://qooxdoo.svn.sourceforge.net/svnroot/qooxdoo/branches/branch_1_2_x/
>>     revision: 23168
>> [2] http://bugzilla.qooxdoo.org/show_bug.cgi?id=3649

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to