- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have an application that does some image rendering that was written a long time ago using quickwin under digital visual fortran. I recently bought Composer XE.
The app. renders the image and writes to a window on a pixel by pixel basis using SETPIXELRGB. This is works OK but is slow. Under DVF I had a utility to write to a buffer and then draw the buffer with PUTIMAGE which is fast.
The format of the buffer has changed it used to have 2bytes for the row width , 2 bytes for the number of rows and then pixel colour values on a row by row basis.
Now if I use IMAGESIZE the buffer is ROWS*COLUMNS*4 + 54 bytes long. Please could I have the information on the structure of this buffer. It looks to me likes bytes 19-22 are width and 23-26 are height and the pixel info. starts at bytes 55 but it will be rather difficult & time consuming to reverse engineer.
Thanks in advance
Andrew
The app. renders the image and writes to a window on a pixel by pixel basis using SETPIXELRGB. This is works OK but is slow. Under DVF I had a utility to write to a buffer and then draw the buffer with PUTIMAGE which is fast.
The format of the buffer has changed it used to have 2bytes for the row width , 2 bytes for the number of rows and then pixel colour values on a row by row basis.
Now if I use IMAGESIZE the buffer is ROWS*COLUMNS*4 + 54 bytes long. Please could I have the information on the structure of this buffer. It looks to me likes bytes 19-22 are width and 23-26 are height and the pixel info. starts at bytes 55 but it will be rather difficult & time consuming to reverse engineer.
Thanks in advance
Andrew
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Having looked a bit harder is looks like a device independant bitmap with the 14 byte bitmap header folled by a 40 byte DIB header.
Is this format fixed within the Quickwin application or will it change dependant on the hardware the application is being run on?
Is this format fixed within the Quickwin application or will it change dependant on the hardware the application is being run on?

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page