Both lines should work actually. The compiler seem confused about the
declaration of WcaAddTempRecord(). It is probably something simple. A "go to
declaration" on the function name might even shed some light on it. :)
In case you have a VC++ project you could share, mail it over and I'll offer to
have a look.
From: Christopher Karper [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 01, 2008 11:54 PM
To: Fredrik Grohn
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How do I execute a custom action before a dialog?
It does not.
error C2664: 'WcaAddTempRecord' : cannot convert parameter 6 from 'LPCWSTR' to
'UINT'
Thanks for trying though. I definitely appreciate the effort.
Chris
On Thu, May 1, 2008 at 5:40 PM, Fredrik Grohn <[EMAIL PROTECTED]<mailto:[EMAIL
PROTECTED]>> wrote:
Just guessing but, does this work?
hResult = WcaAddTempRecord (&hTable, &hColumns, L"ListBox", 0, 3,
(LPCWSTR)L"LISTBOXVALUES", i, (LPCWSTR)L"Item 1");
From: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> [mailto:[EMAIL
PROTECTED]<mailto:[EMAIL PROTECTED]>] On Behalf Of Christopher Karper
Sent: Thursday, May 01, 2008 11:01 PM
To: wix-users@lists.sourceforge.net<mailto:wix-users@lists.sourceforge.net>
Subject: Re: [WiX-users] How do I execute a custom action before a dialog?
This is killing me. I'm trying to do the same thing.
Now, I'm a C++ newb, but I have some people helping me. When I try to compile
even the sample code, I'm getting:
error C2664: 'WcaAddTempRecord' : cannot convert parameter 6 from 'const
wchar_t [14]' to 'UINT'
on this line:
hResult = WcaAddTempRecord (&hTable, &hColumns, L"ListBox", 0, 3,
L"LISTBOXVALUES", i, L"Item 1");
Anyone have any ideas why? I've included wcautil.h, msi.h and msiquery.h, I'm
not sure where else to turn. I'm not even sure what to look at next. Thanks
in advance
Chris
On Thu, May 1, 2008 at 1:38 PM, Bob Arnson <[EMAIL PROTECTED]<mailto:[EMAIL
PROTECTED]>> wrote:
Richard wrote:
> Yes, using the control event table and putting the action on the
> next/back button transitions into this dialog are the way to do it.
> There might be an opportunity for a WiX extension for dialogs here
> that managed these transitions for you, but it would do the same thing
> under the covers as suggested by Bob.
>
Yes, longer-term, an extension could do a lot more at compile and link
time to make MSI UI more bearable. That said, at the end of the day,
it's still MSI UI with the awful feature selection tree control and
without esoteric controls like hyperlinks.<sigh>
> or you can simply hide the combobox when there are no items to be
> selected and show a text control in its place that says something
> descriptive like "(no items available)".
>
Would that prevent MSI complaining if it couldn't find a matching item?
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net<mailto:WiX-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
