fVirt<\/code> of the last entry in the accelerator resource\nhas its high bit set to indicate that it is the end of the table.\n<\/p>\n\nThe format of 32-bit accelerator table resources is nearly identical\nto its 16-bit counterpart.\nThe only difference is the addition of an additional word of padding\nto bring the size of the structure up to a multiple of four bytes.\n<\/p>\n
\ntypedef struct tagACCEL_RESOURCE {\n BYTE fVirt;\n BYTE bPadding; \/* making the padding explicit *\/\n WORD key;\n WORD cmd;\n WORD wPadding; \/* making the padding explicit *\/\n} ACCEL_RESOURCE;\n<\/pre>\n\nOnce again, the last entry is marked by setting the high bit\nof the fVirt<\/code> member.\nThe extra word of padding adds a second obstacle to taking the resource\ndata and passing it to the CreateAcceleratorTable<\/code>\nfunction to create the accelerator table manually.\nNot only do you have to strip off the high bit of the fVirt<\/code>,\nyou also have to convert the table to an array of ACCEL<\/code>\nstructures\nand pass the converted table to the\nCreateAcceleratorTable<\/code> function.\n<\/p>\n\nThat’s all there is to the format of accelerator table resources.\nI told you it was pretty simple.<\/p>\n","protected":false},"excerpt":{"rendered":"
Continuing in the extremely sporadic series on the format of resources, today we’ll take a look at accelerator tables. This topic is so simple, I’ll cover both 16-bit and 32-bit resources on the same day! In 16-bit Windows, the format of an accelerator table resource was simply an array of ACCEL structures. typedef struct tagACCEL […]<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[25],"class_list":["post-27593","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":"
Continuing in the extremely sporadic series on the format of resources, today we’ll take a look at accelerator tables. This topic is so simple, I’ll cover both 16-bit and 32-bit resources on the same day! In 16-bit Windows, the format of an accelerator table resource was simply an array of ACCEL structures. typedef struct tagACCEL […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/27593","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=27593"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/27593\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=27593"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=27593"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=27593"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}