Thank You for your continued support and contributions!
Quote from: Frankenpod on March 31, 2015, 08:27:42 AM1/ Is there a rockbox API call to get the total size of the DAP's disk/flash storage?No. I suspect you'd have to add this to fat.c and then export it in the plugin api.Quote2/ I'm struggling to understand the rockbox graphics functions - in particular, why is there an _array_ of screen objects, rather than just the one?Because there can be more than one screen. Think remotes.QuoteWhich one do I use to draw graphics on?SCREEN_MAIN, usually (unless you want to draw on the remote's screem)QuoteOther issue is am not sure about type conversions - adding up disk usage in bytes leads to numbers too large for int or even long int. Not sure whether to use floats instead or just to round to kb or Mb.Going with 512-byte sectors isn't wrong, or you could try to get the FAT cluster size and use that as a unit. It depends on what you want disk usage to mean, actual bytes or used disk blocks.
1/ Is there a rockbox API call to get the total size of the DAP's disk/flash storage?
2/ I'm struggling to understand the rockbox graphics functions - in particular, why is there an _array_ of screen objects, rather than just the one?
Which one do I use to draw graphics on?
Other issue is am not sure about type conversions - adding up disk usage in bytes leads to numbers too large for int or even long int. Not sure whether to use floats instead or just to round to kb or Mb.
Somehow I got the graph to draw without referring to the screen object. just with rp->lcd_... function calls. Quite confused what the correct way to do it is.
Quote from: Frankenpod on March 31, 2015, 08:27:42 AM1/ Is there a rockbox API call to get the total size of the DAP's disk/flash storage?No. I suspect you'd have to add this to fat.c and then export it in the plugin api.
Page created in 0.082 seconds with 22 queries.