On Tue, Aug 30, 2011 at 09:11:33PM -0300, Lucas Zawacki wrote:
> > It doesn't make sense to pass the info as WM_INITDIALG parameter if it's
> > going to be stored in global variables anyway. A better way would be to
> > store this in the window info.
> >
>
> Any pointers on what's the set of winap
On Wed, Aug 31, 2011 at 3:11 AM, Lucas Zawacki wrote:
> Any pointers on what's the set of winapi functions used to store and
> retrieve data in windows? I've searched MSDN for almost 30 minutes and
> no luck.
Try SetWindowLongPtr [1] / GetWindowLongPtr [2].
You probably want to use the W variants
> It doesn't make sense to pass the info as WM_INITDIALG parameter if it's
> going to be stored in global variables anyway. A better way would be to
> store this in the window info.
>
Any pointers on what's the set of winapi functions used to store and
retrieve data in windows? I've searched MSDN
Lucas Fialho Zawacki writes:
> +static INT_PTR CALLBACK ConfigureDevicesDlgProc(HWND dialog, UINT uMsg,
> WPARAM wParam, LPARAM lParam)
> +{
> +static LPDIACTIONFORMATW lpdiaf;
> +static DIDevicesData devices_data;
> +static ConfigureDevicesData *conf_data;
> +
> +switch(uMsg)
>
