Hi Mihai, I wouldn't write this function in the SDK for the reason you mentioned but keep backward compatibility.They're still a lot of companies which didn't do the migration yet but still use Squiggly and would be happy to benefit of this fix.
What do you think ? Frédéric THOMAS > From: mihai.ch...@gmail.com > Date: Thu, 17 Jul 2014 16:41:18 +0100 > Subject: Squiggly memory leak > To: dev@flex.apache.org > > Heya, > > > Both of Squiggly's SpellUI.as classes have a memory leak detailed in > https://issues.apache.org/jira/browse/FLEX-34421. > > In order to fix them I need to write a function which searches through > a Dictionary by value and returns the associated key (if there's > already one in the sdk, please point me to it). I'm thinking to put > that in a new file called DictionaryUtils in > sdk\frameworks\projects\framework\src\mx\utils\, and reference it from > Squiggly, since the latter uses the flex framework anyway. > > Does that sound ok to people? It would mean that the next version of > Squiggly only worked with the latest SDK. I guess that's a problem if > projects which now use Squiggly want to update to the latest version > without using the latest SDK. I have a feeling that's unlikely or very > rare, but I'm really not sure. > > If we want to keep backward compatibility I can create the > DictionaryUtils class inside Squiggly itself. > > > Thanks, > Mihai
