Hmm, yeah. Just seems a little more straightforward with the clear() method.
2010/2/24 Greg Brown <[email protected]> > I personally think either approach is equally valid (clearing or > replacing). Adding a clear() method is possible, but in the absence of > this method you could simply call taskSequence.getCount .remove(0, > taskSequence.getCount()). > > On Feb 24, 2010, at 12:20 PM, Mathias Versichele wrote: > > I have one TaskSequence as a private field in my GUI startup class. When I > start up the program I have to parse a directory of files, so I fill the > TaskSesquence with tasks (one for every file to be parsed). When this is > done, I want to clear the TaskSequence so it is ready for accepting new > tasks. Now I do this by re-instantiating, but clearing the existing object > seems more elegant. > > 2010/2/24 Greg Brown <[email protected]> > >> Under what circumstances might you want to do that? Just want to >> understand the use case... >> >> On Feb 24, 2010, at 11:01 AM, Mathias Versichele wrote: >> >> > A clear() method on the TaskSequence and TaskGroup classes might be >> useful if you want to remove all tasks. >> > >> > -- >> > Mathias Versichele >> > Bio-ir milieutechnologie / Msc. geografie >> > Oudburgstraat 16 >> > 9240 Zele >> > 0485/16.07.08 >> >> > > > -- > Mathias Versichele > Bio-ir milieutechnologie / Msc. geografie > Oudburgstraat 16 > 9240 Zele > 0485/16.07.08 > > > -- Mathias Versichele Bio-ir milieutechnologie / Msc. geografie Oudburgstraat 16 9240 Zele 0485/16.07.08
