Thanks for your explanation Niels. >I think it makes sense to change >if (descs[i].type == encoder_type[n].type) to if >(descs[i].type & encoder_type[n].type) let me know if this >works for you, so I can include it in the archive.
This change does correct dfbinfo's encoder type printing and it now works as I had expected. Best regards, Timothy -- Timothy Strelchun CE Software Engineering Digital Home Group Intel Corporation The views expressed above are my own and not those of Intel >-----Original Message----- >From: Niels Roest [mailto:ni...@directfb.org] >Sent: Tuesday, January 20, 2009 3:44 AM >To: Strelchun, Timothy >Cc: 'directfb-dev@directfb.org' >Subject: Re: [directfb-dev] Encoder type field, intended to >hold a single value or a set of types as flags? > >These fields can be used to describe the kind of encoder you are using. >You are correct in seeing that currently, DirectFB is not >using these fields. >So, it is primarily intended as a 'hint' or information >towards the application. > >You are also correct in noting that dfbinfo is acting unexpected. >I think it makes sense to change >if (descs[i].type == encoder_type[n].type) to if >(descs[i].type & encoder_type[n].type) let me know if this >works for you, so I can include it in the archive. > >Greets >Niels _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
