PocketMatrix

Hi again,

Thanks for taking my ideas serious

I like you have the different resolutions and window alignment high on the list. The most improtant one for me would be to have the window in the correct resolution when you do a landscaped application (640x480 instead of 480x640), would make it SO much easier for debugging.

WOW.. Seems my idea for array setPixels will be implemented.

You write you plan to remove the old linked list setPixels, why ? I can still see many advantages of this one such as:
1. If you remove a pixel it will never take time. With the array you have to check the flags to see if it is active.
2. You don't have to allocate an array of worst case. Linked list can expanded as needed.
(Okay, you dont want to do too much allocation and deallocation runtime anyway).
But I will leave it to you to decide

The palletized device support could also be my fault To be honest, I'm not sure HOW important this is. I do know one game developer who released a shareware game that DID NOT support this. He has one customer who just bought the game without testing it.. this customer of course had a HP 525 so his game just crashed

If you don't plan to support these devices then please let the OpenDisplay return a error saying PALETTE_DEVICES_NOT_SUPPORTED

Great ideas, again.. I have updated the list above...

Dan: Good thinking.. I'll see what I can put together...

By the way. I was thinking of renaming the DLL to gapidraw11.dll to avoid versioning conflicts. I hope it won't impose any problems for anyone, please let me know if otherwise.

/Johan