These are currently returning 'not implemented'.
Would it make sense to have 'GetCount' always return '1' and have the indexed read simply read in the whole thing?
Max TenEyck Woodbury max@mtew.isa-geek.net wrote:
These are currently returning 'not implemented'.
Would it make sense to have 'GetCount' always return '1' and have the indexed read simply read in the whole thing?
Looks like you don't understand what those APIs do. What's that 'the whole thing'?
On 11/14/2012 07:03 AM, Dmitry Timoshkov wrote:
Max TenEyck Woodbury max@mtew.isa-geek.net wrote:
These are currently returning 'not implemented'.
Would it make sense to have 'GetCount' always return '1' and have the indexed read simply read in the whole thing?
Looks like you don't understand what those APIs do. What's that 'the whole thing'?
Yes, it's the simplest way to stub the whole sequence into doing something useful. When someone wants to get fancy, they can build a vector of blocks, but that is much more work. Definitely NOT great, but better than nothing, which is what we have now.
'The whole thing' is the entire image in one swallow.
Max TenEyck Woodbury max@mtew.isa-geek.net wrote:
These are currently returning 'not implemented'.
Would it make sense to have 'GetCount' always return '1' and have the indexed read simply read in the whole thing?
Looks like you don't understand what those APIs do. What's that 'the whole thing'?
Yes, it's the simplest way to stub the whole sequence into doing something useful. When someone wants to get fancy, they can build a vector of blocks, but that is much more work. Definitely NOT great, but better than nothing, which is what we have now.
'The whole thing' is the entire image in one swallow.
Then you need to investigate what should be returned and in which format, probably write some tests, read some docs.
On 11/14/2012 09:38 AM, Dmitry Timoshkov wrote:
Max TenEyck Woodbury max@mtew.isa-geek.net wrote:
These are currently returning 'not implemented'.
Would it make sense to have 'GetCount' always return '1' and have the indexed read simply read in the whole thing?
Looks like you don't understand what those APIs do. What's that 'the whole thing'?
Yes, it's the simplest way to stub the whole sequence into doing something useful. When someone wants to get fancy, they can build a vector of blocks, but that is much more work. Definitely NOT great, but better than nothing, which is what we have now.
'The whole thing' is the entire image in one swallow.
Then you need to investigate what should be returned and in which format, probably write some tests, read some docs.
Document reading is in progress. Have the PNG side more or less in hand, Need to do the windows side. Looking for an overview and match between the two.
So, its just a small mater of code...
Would calculating the total number of 'row' calls and reading each row as a 'block in turn be an alternate implementation?
Max TenEyck Woodbury max@mtew.isa-geek.net wrote:
Would calculating the total number of 'row' calls and reading each row as a 'block in turn be an alternate implementation?
No, your terminology (what is a "row" in PNG?) shows lack of undertsanding of what is a block, or what that APIs are supposed to return. Start with writing a couple of simple tests, and demonstrate that you really undrestand things before asking further questions.
On 11/14/2012 10:15 AM, Dmitry Timoshkov wrote:
Max TenEyck Woodbury max@mtew.isa-geek.net wrote:
Would calculating the total number of 'row' calls and reading each row as a 'block in turn be an alternate implementation?
No, your terminology (what is a "row" in PNG?) shows lack of undertsanding of what is a block, or what that APIs are supposed to return. Start with writing a couple of simple tests, and demonstrate that you really undrestand things before asking further questions.
PNG terminology does not mention 'blocks' as such. It talks about 'rows' and 'chunks'. 'Row' is mentioned in the 'libpng' terminology, as in reading a 'row' and 'row_pointer'. It is apparently a unit of processable data. Much as a block is apparently a unit of processable data from the WIC end.
WIC is the end I have only scratched the surface on.
-
Dmitry Timoshkov -
Max TenEyck Woodbury