Closed GoogleCodeExporter closed 9 years ago
what exactly do you mean? i didn't dig into the code, yet, so please could you
tell
me where the parsing could be doubled?
Original comment by pog...@gmail.com
on 18 Apr 2008 at 4:34
The way it works now, is that the program reads the file tree from the player
and
parses the string multiple times (i.e. when building the treeview in the
playlists
view and again in the filemanagement view). Maybe it could be sped up by
builing a
tree of all the files on the player and using this tree in the whole
application,
until it needs to be refreshed.
Also, MTPAxe needs optimization to reduce the amount of memory required. Right
now
all arrays are statically allocated, for ease of debugging. A big improvement
would
be to make them dynamically allocated
Original comment by rios.fer...@gmail.com
on 19 Apr 2008 at 3:31
Speed improvements implemented in r16. Now need to work on memory usage
improvements
Original comment by rios.fer...@gmail.com
on 29 Apr 2008 at 12:18
reduced the memory usage in mtpaxe in r42 by removing some unecessary static
arrays
Original comment by rios.fer...@gmail.com
on 29 Jun 2008 at 10:12
Original comment by rios.fer...@gmail.com
on 9 Aug 2008 at 7:04
Original issue reported on code.google.com by
rios.fer...@gmail.com
on 18 Apr 2008 at 12:45