If backwards compatibility stands in the way of progress, I say "to hell with it" ;-)
All kidding aside, if there is no Dictionary key search by value, I think the SDK will benefit from it as well as Squiggly. And I don't see a problem in giving folks another reason to update to the latest SDK. EdB On Thu, Jul 17, 2014 at 5:41 PM, Mihai Chira <mihai.ch...@gmail.com> wrote: > 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 > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
