Re: winhelp: add preliminary *.cnt file support (parser)
Kirill K. Smirnov a écrit :
ChangeLog:
Add preliminary *.cnt file support (parser)
Hi Kirill,
good to see someone enhancing winhelp!!
a few comments though about your patch
1/ you forgot to include the changes (at least) to hlpfile.h
2/ internal function definitions
+static BOOL HLPFILE_ReadCntFile(HLPFILE*);
+static void HLPFILE_FreeCnt(HLPFILE_CNT*);
I think those two functions are not correctly designed... I'd more
likely see something like:
+static HLPFILE_CNT* HLPFILE_ReadCntFile(const char*);
+static void HLPFILE_FreeCnt(HLPFILE_CNT*);
this makes the two functions consistent in what they depend on (either
both of them are passed a HLPFILE* or none of them), and also allows to
return the newly created HLPFILE_CNT which you never store in HLPFILE
3/ don't use C++ comments in C code
+if (cur->level == entry->level) // level exists
+{
+entry->parent = cur->parent;
+cur->next = entry;
+}
+else // entry on new level
A+
Re; Solidworks 2006
I added the bug to winehq here is the link thank you for the help I made it a little better to run: http://bugs.winehq.org/show_bug.cgi?id=6723 -- Kartik Thakore 250313003 [EMAIL PROTECTED] 1st year engineering
Re: Wine Version String
On Saturday, November 18, 2006 18:17, Robert Lunnon wrote: > Somewhere between Version 0.9.23 and Version 0.9.25 the version string > format changed from > > Wine X.X.X > > to > wine-X.X.X > > Can we please decide on a version string format and stick to it so > packaging can be reasonably automated. > > Bob I think that's a result of the new git version magic, for example: $ ./wine --version wine-0.9.25-gef2c062 Presumably the gef2c062 allows one to identify the exact sources used to build that version, but for release builds just the tag is sufficient. - Neil
Wine Version String
Somewhere between Version 0.9.23 and Version 0.9.25 the version string format changed from Wine X.X.X to wine-X.X.X Can we please decide on a version string format and stick to it so packaging can be reasonably automated. Bob
Re: Wine 0.9.25 for SuSE 10.1 is Wine 0.9.24
There were not much functional changes in the last days. Oh, I think that the changes between 0.9.24 and 0.9.25 are big. In 0.9.24 Java-Swing programs of the Windows Java runs creates a black backgraou over all and if you move the window, then the graphics inside the Swing-windows don't move with it. And in 0.9.25 all that is fixed. Greatings theuserbl _ Die neue MSN Suche Toolbar mit Windows-Desktopsuche. Suchen Sie gleichzeitig im Web, Ihren E-Mails und auf Ihrem PC! Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden!
Re: Wine 0.9.25 for SuSE 10.1 is Wine 0.9.24
On Sat, Nov 18, 2006 at 05:10:23PM +, theUser BL wrote: > Yesterday I have seen, that Wine 0.9.25 is already published and I have > downloaded it. > I gave downloaded the Sorces > http://prdownloads.sourceforge.net/wine/wine-0.9.25.tar.bz2 > And the rpm-files for SuSE 10.1. > > But after installing the SuSE-rpms, after the input of "wine --version" it > says, that it is version 0.9.24. > After an "winver" its says also 0.9.24. > > Then I have compiled the sources. The self-compiled Wine says 0.9.25. > And in 0.9.25 are some bugs fixed, which in 0.9.24 still exists. And the > Wine 0.9.25 for SuSE 10.1 have still the old 0.9.24 bugs. > > So the builds of SuSE 10.1 are not correct created. Yes. Due to a mistake (and my automated git scripts) a version of 1 or 2 days before the release got put into RPMs :( There were not much functional changes in the last days. I can however sit down and create true 0.9.25 rpms ... :/ Ciao, Marcus
Wine 0.9.25 for SuSE 10.1 is Wine 0.9.24
Yesterday I have seen, that Wine 0.9.25 is already published and I have downloaded it. I gave downloaded the Sorces http://prdownloads.sourceforge.net/wine/wine-0.9.25.tar.bz2 And the rpm-files for SuSE 10.1. But after installing the SuSE-rpms, after the input of "wine --version" it says, that it is version 0.9.24. After an "winver" its says also 0.9.24. Then I have compiled the sources. The self-compiled Wine says 0.9.25. And in 0.9.25 are some bugs fixed, which in 0.9.24 still exists. And the Wine 0.9.25 for SuSE 10.1 have still the old 0.9.24 bugs. So the builds of SuSE 10.1 are not correct created. Greatings theuserbl _ Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden!
oleaut32 tests and VarAdd(VT_DISPATCH, ...)
Alex Villacís Lasso wrote: BTW, I see many attempts of VarAdd(VT_DISPATCH, ...) tested. All of them are expected to fail. However, the tax app does just that (VarAdd(VT_DISPATCH, ...)) and fails to display a print preview because of this. I think that native oleaut32 fails these tests, not because it does not support VarAdd(VT_DISPATCH) at all, but because these VT_DISPATCHs are incorrectly formed (as in, just zeroing the variant, then assigning VT_DISPATCH as variant type). I need to confirm this with a test program. Yes, if you can improve the variant tests for oleaut32, please do! - Dan
Re: CD-ROM access via "\\\\.\\Cdrom0"
On Friday 17 November 2006 23:34, Pavel Roskin wrote: > I actually think that complete Wine configuration should be in the > registry. As soon as parts of Wine configuration can be changed using > UNIX file operation, we have a problem of consistency. File managers Yes, the registry is the main alternative, although even then you will be pointing to a changing filesystem. And there may be a chicken-and-egg on boot where you need to access a drive before the registry is accessible, I'm not sure. -Hans
Re: ASN.1 parser
On Saturday 18 November 2006 01:12, Juan Lang wrote: > Hi Kai, > > > I'm just looking into implementing Kerberos and Negotiate for SSPI. It > > seems like I'll need an ASN.1 parser for both of those. I know you have > > a partial implementation of an ASN.1 DER parser in crypt32, but I think > > it would be kind of silly to keep two seperate copies. Think it would > > make sense to create our own asn dll? Or is there any method to find out > > what functions msasn1.dll provides? > > I think you could get Kerberos and Negotiate working quicker just by > copying code as needed. No non-MS application I'm aware of uses msasn1 > directly, so Wine wouldn't gain much from a compatible version. Doing the > "right" thing could be sort of a hassle for crypt32 too (not that so many > apps use it right now.) Ok, never mind then. I'll trust you on that one. :) > The only thing is how much duplicated code offends you. I'm trying to > prevent you from diving into a black hole, like I did with crypt32 when > what I was really after was SSL ;) Well, an alternative option for Kerberos and Negotiate would be using GSSAPI, but I now agree with Dan Kegel on that one, it's a bit too bloated for what we want to do with it. The api is a bit too different from SSPI to enable making SPPI a thin wrapper for GSSAPI and implementing our providers as GSSAPI plugins... It was a nice plan, though ;) I'll just copy what I need then. Kai -- Kai Blin, WorldForge developerhttp://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin/ -- Will code for cotton. pgpHHKyNrgDm4.pgp Description: PGP signature
