How to read GetDeviceCaps() return values?












0














I am new to Windows API and I just can't seem to figure this out:



According to the documentation the function int GetDeviceCaps(HDC hdc,int index); returns integer values which correspond to the selected item I want to know about. However, how am I supposed to convert the integers to the values?



printf("Rastercaps: %dn", GetDeviceCaps(hdc, RASTERCAPS));
// rastercaps: 32409


item RASTERCAPS:



values




  • RC_BANDING Requires banding support.

  • RC_BITBLT Capable of transferring bitmaps.

  • RC_BITMAP64 Capable of supporting bitmaps larger than 64 KB.

  • RC_DI_BITMAP Capable of supporting the SetDIBits and GetDIBits
    functions.

  • RC_DIBTODEV Capable of supporting the SetDIBitsToDevice
    function.

  • RC_FLOODFILL Capable of performing flood fills.


...



Does 32409 mean the device has RASTERCAP values (capabilities) 3,2,4,0 and 9, in the order as stated in their table?



Thank you.










share|improve this question






















  • This is a bit field so you have to use binary! 32409 = 111111010011001b, so the bits with values 1, 8, 16, 128, 512, 1024, 2048, 4096, 8192, and 16384 are set. To see if a particular bit it set, use the "and" operator.
    – Andreas Rejbrand
    Nov 19 '18 at 14:52


















0














I am new to Windows API and I just can't seem to figure this out:



According to the documentation the function int GetDeviceCaps(HDC hdc,int index); returns integer values which correspond to the selected item I want to know about. However, how am I supposed to convert the integers to the values?



printf("Rastercaps: %dn", GetDeviceCaps(hdc, RASTERCAPS));
// rastercaps: 32409


item RASTERCAPS:



values




  • RC_BANDING Requires banding support.

  • RC_BITBLT Capable of transferring bitmaps.

  • RC_BITMAP64 Capable of supporting bitmaps larger than 64 KB.

  • RC_DI_BITMAP Capable of supporting the SetDIBits and GetDIBits
    functions.

  • RC_DIBTODEV Capable of supporting the SetDIBitsToDevice
    function.

  • RC_FLOODFILL Capable of performing flood fills.


...



Does 32409 mean the device has RASTERCAP values (capabilities) 3,2,4,0 and 9, in the order as stated in their table?



Thank you.










share|improve this question






















  • This is a bit field so you have to use binary! 32409 = 111111010011001b, so the bits with values 1, 8, 16, 128, 512, 1024, 2048, 4096, 8192, and 16384 are set. To see if a particular bit it set, use the "and" operator.
    – Andreas Rejbrand
    Nov 19 '18 at 14:52
















0












0








0







I am new to Windows API and I just can't seem to figure this out:



According to the documentation the function int GetDeviceCaps(HDC hdc,int index); returns integer values which correspond to the selected item I want to know about. However, how am I supposed to convert the integers to the values?



printf("Rastercaps: %dn", GetDeviceCaps(hdc, RASTERCAPS));
// rastercaps: 32409


item RASTERCAPS:



values




  • RC_BANDING Requires banding support.

  • RC_BITBLT Capable of transferring bitmaps.

  • RC_BITMAP64 Capable of supporting bitmaps larger than 64 KB.

  • RC_DI_BITMAP Capable of supporting the SetDIBits and GetDIBits
    functions.

  • RC_DIBTODEV Capable of supporting the SetDIBitsToDevice
    function.

  • RC_FLOODFILL Capable of performing flood fills.


...



Does 32409 mean the device has RASTERCAP values (capabilities) 3,2,4,0 and 9, in the order as stated in their table?



Thank you.










share|improve this question













I am new to Windows API and I just can't seem to figure this out:



According to the documentation the function int GetDeviceCaps(HDC hdc,int index); returns integer values which correspond to the selected item I want to know about. However, how am I supposed to convert the integers to the values?



printf("Rastercaps: %dn", GetDeviceCaps(hdc, RASTERCAPS));
// rastercaps: 32409


item RASTERCAPS:



values




  • RC_BANDING Requires banding support.

  • RC_BITBLT Capable of transferring bitmaps.

  • RC_BITMAP64 Capable of supporting bitmaps larger than 64 KB.

  • RC_DI_BITMAP Capable of supporting the SetDIBits and GetDIBits
    functions.

  • RC_DIBTODEV Capable of supporting the SetDIBitsToDevice
    function.

  • RC_FLOODFILL Capable of performing flood fills.


...



Does 32409 mean the device has RASTERCAP values (capabilities) 3,2,4,0 and 9, in the order as stated in their table?



Thank you.







windows






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 '18 at 14:34









thehorseisbrown

257




257












  • This is a bit field so you have to use binary! 32409 = 111111010011001b, so the bits with values 1, 8, 16, 128, 512, 1024, 2048, 4096, 8192, and 16384 are set. To see if a particular bit it set, use the "and" operator.
    – Andreas Rejbrand
    Nov 19 '18 at 14:52




















  • This is a bit field so you have to use binary! 32409 = 111111010011001b, so the bits with values 1, 8, 16, 128, 512, 1024, 2048, 4096, 8192, and 16384 are set. To see if a particular bit it set, use the "and" operator.
    – Andreas Rejbrand
    Nov 19 '18 at 14:52


















This is a bit field so you have to use binary! 32409 = 111111010011001b, so the bits with values 1, 8, 16, 128, 512, 1024, 2048, 4096, 8192, and 16384 are set. To see if a particular bit it set, use the "and" operator.
– Andreas Rejbrand
Nov 19 '18 at 14:52






This is a bit field so you have to use binary! 32409 = 111111010011001b, so the bits with values 1, 8, 16, 128, 512, 1024, 2048, 4096, 8192, and 16384 are set. To see if a particular bit it set, use the "and" operator.
– Andreas Rejbrand
Nov 19 '18 at 14:52














1 Answer
1






active

oldest

votes


















0














They're bitmasks. In the relevant C header file (wingdi.h) there is



/* Raster Capabilities */
#define RC_NONE
#define RC_BITBLT 1 /* Can do standard BLT. */
#define RC_BANDING 2 /* Device requires banding support */
#define RC_SCALING 4 /* Device requires scaling support */
#define RC_BITMAP64 8 /* Device can support >64K bitmap */


...and many more.



The return value (32409) is made up of the bitwise-or of these values. So, for example, if you wanted to know if the device could support >64K bitmap you would do



int rc = GetDeviceCaps(hdc, RASTERCAPS);
if (rc & RC_BITMAP64) { /* it does support >64k */ }


So in this case, 32409 is 0111111010011001 in binary which means it has the capabilities RC_BITBLT | RC_BITMAP64 | RC_GDI20_OUTPUT | RC_DI_BITMAP |
RC_DIBTODEV | RC_BIGFONT | RC_STRETCHBLT | RC_FLOODFILL | RC_STRETCHDIB | RC_OP_DX_OUTPUT.



See "Bitwise operations in C"






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53376844%2fhow-to-read-getdevicecaps-return-values%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    They're bitmasks. In the relevant C header file (wingdi.h) there is



    /* Raster Capabilities */
    #define RC_NONE
    #define RC_BITBLT 1 /* Can do standard BLT. */
    #define RC_BANDING 2 /* Device requires banding support */
    #define RC_SCALING 4 /* Device requires scaling support */
    #define RC_BITMAP64 8 /* Device can support >64K bitmap */


    ...and many more.



    The return value (32409) is made up of the bitwise-or of these values. So, for example, if you wanted to know if the device could support >64K bitmap you would do



    int rc = GetDeviceCaps(hdc, RASTERCAPS);
    if (rc & RC_BITMAP64) { /* it does support >64k */ }


    So in this case, 32409 is 0111111010011001 in binary which means it has the capabilities RC_BITBLT | RC_BITMAP64 | RC_GDI20_OUTPUT | RC_DI_BITMAP |
    RC_DIBTODEV | RC_BIGFONT | RC_STRETCHBLT | RC_FLOODFILL | RC_STRETCHDIB | RC_OP_DX_OUTPUT.



    See "Bitwise operations in C"






    share|improve this answer




























      0














      They're bitmasks. In the relevant C header file (wingdi.h) there is



      /* Raster Capabilities */
      #define RC_NONE
      #define RC_BITBLT 1 /* Can do standard BLT. */
      #define RC_BANDING 2 /* Device requires banding support */
      #define RC_SCALING 4 /* Device requires scaling support */
      #define RC_BITMAP64 8 /* Device can support >64K bitmap */


      ...and many more.



      The return value (32409) is made up of the bitwise-or of these values. So, for example, if you wanted to know if the device could support >64K bitmap you would do



      int rc = GetDeviceCaps(hdc, RASTERCAPS);
      if (rc & RC_BITMAP64) { /* it does support >64k */ }


      So in this case, 32409 is 0111111010011001 in binary which means it has the capabilities RC_BITBLT | RC_BITMAP64 | RC_GDI20_OUTPUT | RC_DI_BITMAP |
      RC_DIBTODEV | RC_BIGFONT | RC_STRETCHBLT | RC_FLOODFILL | RC_STRETCHDIB | RC_OP_DX_OUTPUT.



      See "Bitwise operations in C"






      share|improve this answer


























        0












        0








        0






        They're bitmasks. In the relevant C header file (wingdi.h) there is



        /* Raster Capabilities */
        #define RC_NONE
        #define RC_BITBLT 1 /* Can do standard BLT. */
        #define RC_BANDING 2 /* Device requires banding support */
        #define RC_SCALING 4 /* Device requires scaling support */
        #define RC_BITMAP64 8 /* Device can support >64K bitmap */


        ...and many more.



        The return value (32409) is made up of the bitwise-or of these values. So, for example, if you wanted to know if the device could support >64K bitmap you would do



        int rc = GetDeviceCaps(hdc, RASTERCAPS);
        if (rc & RC_BITMAP64) { /* it does support >64k */ }


        So in this case, 32409 is 0111111010011001 in binary which means it has the capabilities RC_BITBLT | RC_BITMAP64 | RC_GDI20_OUTPUT | RC_DI_BITMAP |
        RC_DIBTODEV | RC_BIGFONT | RC_STRETCHBLT | RC_FLOODFILL | RC_STRETCHDIB | RC_OP_DX_OUTPUT.



        See "Bitwise operations in C"






        share|improve this answer














        They're bitmasks. In the relevant C header file (wingdi.h) there is



        /* Raster Capabilities */
        #define RC_NONE
        #define RC_BITBLT 1 /* Can do standard BLT. */
        #define RC_BANDING 2 /* Device requires banding support */
        #define RC_SCALING 4 /* Device requires scaling support */
        #define RC_BITMAP64 8 /* Device can support >64K bitmap */


        ...and many more.



        The return value (32409) is made up of the bitwise-or of these values. So, for example, if you wanted to know if the device could support >64K bitmap you would do



        int rc = GetDeviceCaps(hdc, RASTERCAPS);
        if (rc & RC_BITMAP64) { /* it does support >64k */ }


        So in this case, 32409 is 0111111010011001 in binary which means it has the capabilities RC_BITBLT | RC_BITMAP64 | RC_GDI20_OUTPUT | RC_DI_BITMAP |
        RC_DIBTODEV | RC_BIGFONT | RC_STRETCHBLT | RC_FLOODFILL | RC_STRETCHDIB | RC_OP_DX_OUTPUT.



        See "Bitwise operations in C"







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 19 '18 at 14:47

























        answered Nov 19 '18 at 14:40









        Peter Hull

        2,89522331




        2,89522331






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53376844%2fhow-to-read-getdevicecaps-return-values%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            'app-layout' is not a known element: how to share Component with different Modules

            android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

            WPF add header to Image with URL pettitions [duplicate]