Derrell, As you might have gathered I've been very busy as well. I've only just come up for air and had a chance to review checkins and bug changes.
Thanks for checking in the fix for 770 to the 0.7.3 branch without me having to create a test application. You will also need to do 775. However, you will see my comment in the bug - I'm concerned about trunk. Perhaps someone from the main team can answer my question at the end of http://bugzilla.qooxdoo.org/show_bug.cgi?id=770 about how the fix is to be ported to trunk? More importantly, how this sort of problem is tracked so that it isn't lost? Surely it can't be down to mere mortals like me bugging [sic] people! As the change is identical (apart from a full-stop!) to my patch it will be OK. Hugh > > Sounds like you might need the fixes in > > http://bugzilla.qooxdoo.org/show_bug.cgi?id=770 and > > http://bugzilla.qooxdoo.org/show_bug.cgi?id=775 > > as well. > > > > Derrell: have you considered these for checkin at all? > > > Ping me next week and I'll try to look into this in more depth. > > > > I'm hereby pinging you - some time after the original posting > > though! > > > > Hugh, thanks for the ping. I will try to take a look at this. > Unfortunately, I'm not in a great position to be able to work on it > at the moment. Do you think you could come up with a small test > program that can exercise the issue, maybe even tracking when the > remote requests are sent and received in relationship to appearance, > and need for refreshes, etc.? ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
