Closed DanielFabian closed 10 years ago
Hi Daniel, thanks for the report. I've implemented some unit tests which reproduce the issue, and I'll try to fix it sometime this week.
Update: I figured out what the problem was -- I forgot to include one line of code to call the internal processing function. I don't have my laptop setup to properly build ExtCore, so I can't immediately push a new release with this fix; I'll do it as soon as I get my other machine up and running again (likely next weekend).
cool, no hurry, just noticed it.
On 18 May 2014 15:46, Jack Pappas notifications@github.com wrote:
Closed #8 https://github.com/jack-pappas/ExtCore/issues/8.
— Reply to this email directly or view it on GitHubhttps://github.com/jack-pappas/ExtCore/issues/8#event-122239753 .
Hi @DanielFabian -- I finally had a chance today to release an updated build of ExtCore (0.8.42) with fixes for this bug and a few others. Thanks again for letting me know about the bug -- I'm going to try to find some time soon to fix the last few bugs that are stopping the CI builds from passing, so it'll be more obvious if a new bug is introduced somewhere.