The color data will have to be stored either in a database or in some kind of resource file. But, when the application loads all of the color information could be put into a table/dataset in memory, so the speed won't be a problem since it doesn't have to make any additional calls to the database. Especially if there are only two options for the colors.
Problem B:
It arrow keys/tab key shouldn't be any big deal at all. That's the default behavior for those keys.
The enter key thingie is non-standard Windows behavior. It's more of a mainframe standard. That doesn't mean it can't be done, but it will take a bit of programming since now the KeyUp, KeyDown and KeyPressed events must all be checked and some kind of Select...Case statement whipped up. But it can be done.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
flatlanders
no subject
Date: 2006-04-05 05:28 pm (UTC)Problem A:
The color data will have to be stored either in a database or in some kind of resource file. But, when the application loads all of the color information could be put into a table/dataset in memory, so the speed won't be a problem since it doesn't have to make any additional calls to the database. Especially if there are only two options for the colors.
Problem B:
It arrow keys/tab key shouldn't be any big deal at all. That's the default behavior for those keys.
The enter key thingie is non-standard Windows behavior. It's more of a mainframe standard. That doesn't mean it can't be done, but it will take a bit of programming since now the KeyUp, KeyDown and KeyPressed events must all be checked and some kind of Select...Case statement whipped up. But it can be done.