Dimitrie O. Paun wrote:
That's still a compile-time check. A runtime check runs when wine runs...
But the test is really a time-cost task. I won't merge it into WINEALSA if I
can't improve it.
Does anyone have any suggestions?
--
Dimi.
I hope you know what you will begin with. (For the ones that don't know
uxtheme.dll is the dll that takes care of all theming on WinXP and it is the dll
that dlls like comctl32 and all others use for theming)
Some time ago I checked out uxtheme.dll a bit and it seems that it needs
changes all
Everything that's LGPL should be listed on the above page. Additionally,
code in ReWind is X11. Anything else in WineX may be assumed AFPL, but
may also be released as X11 at TransGaming's discretion. I think most
non-DirectX code (and even a limited subset of the DirectX code) could
be released
I would be glad to be of any assistance I can be in this matter. I think
wine is a great project, and I have been looking for the right project to
immerse my self in. I think I've just found it :-)
Mike Jackson
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
On Mon, 2003-09-29 at 18:07, Craig Davison wrote:
Hi,
I've been trying to install the SQLserver Client Tools with Wine 20030911
(on Redhat 9). The setup process fails near the beginning because it
cannot install MDAC (Setup is installing Microsoft Data Access Components
(MDAC) ...).
On Mon, 2003-09-29 at 22:06, Robert van Herk wrote:
As I understand (from the explanation by Russell Howe (thanx:-))),
there is a script called wineshelllink that is supposed to install the
created start menu items in your KDE menu.
Indeed. It is rather broken though. It works sometimes, but
On Tue, 2003-09-30 at 01:40, Alexandre Julliard wrote:
One problem is that most makefiles specify different defines, so you
basically need to have one different rule for each C file. Then there
are many files that have explicit rules. It could be done, but I don't
think it's worth it, and the
On Tue, 2003-09-30 at 04:43, Sylvain Petreolle wrote:
This isnt a windows system dll. Isnt that another attempt like
cards.dll ?
Sure it is. Apps attempt to LoadLibrary it if they detect it to enhance
their drawing capabilities. It's conceivable that one day apps will not
have this backwards
On Tue, 2003-09-30 at 07:43, Jerry Jenkins wrote:
But the test is really a time-cost task. I won't merge it into WINEALSA if I
can't improve it.
Does anyone have any suggestions?
Well I for one am a bit confused. The reason it needs to be a runtime
check is so we can compile Wine on one
tir, 30.09.2003 kl. 09.39 skrev Jonathan Wilson:
Everything that's LGPL should be listed on the above page. Additionally,
code in ReWind is X11. Anything else in WineX may be assumed AFPL, but
may also be released as X11 at TransGaming's discretion. I think most
non-DirectX code (and even
Mike Hearn [EMAIL PROTECTED] wrote:
Well, the Russian Winter is a common exaggeration, like
a stray bear in every russian town, a hidden communist in
each russian, and many others :-)
I notice vodka isn't in that list of common exaggerations - party on! :)
It's included in the list of
Ofcourse I want uxtheme.dll implemented since it is a very cool new dll but I
think a problem will be that it needs changes in various parts of Wine.
Mainly in the user and common control area. Microsoft releases two sets of
comctl32 dlls. One of them is meant for backwards compatibility.
Hi,
--- Alexandre Julliard [EMAIL PROTECTED] wrote:
Precisely, this way it's obvious which functions are meant to be
used by Win32 apps and which are internal to Wine.
Hmm, I think any programmer who thinks a static function in one of
the implementation files of a given dll can possibly be
Bill Medland [EMAIL PROTECTED] writes:
Bill Medland ([EMAIL PROTECTED])
Expand the documentation on the --dll option
+Syntax: -dll name[,name[,...]]={native|so|builtin}[,{n|s|b}[,...]]
+- 'name' is the name of any dll without extension
+- the order of loading (native, so and
On Tue, Sep 30, 2003 at 01:16:17PM +0100, Mike Hearn wrote:
On Tue, 2003-09-30 at 01:40, Alexandre Julliard wrote:
One problem is that most makefiles specify different defines, so you
basically need to have one different rule for each C file. Then there
are many files that have explicit
On September 30, 2003 10:57 am, Roderick Colenbrander wrote:
Microsoft releases two sets of
comctl32 dlls. One of them is meant for backwards compatibility.
Do you have any idea why would that be needed?
--
Dimi.
On September 30, 2003 09:16 am, Ove Kaaven wrote:
Now the LGPL-ness of Wine
actually makes it an advantage to hold code back from Wine in some
circumstances, whether you and I like it or not.
Your argument is valid right now because there was not attempt
to abstract the copy protection through
On September 29, 2003 05:31 pm, Jon Griffiths wrote:
But since you're adament, this should probably be made a janitorial
task; internal stdcall functions are currently used in other places
(5 other files in shlwapi, for example).
It doesn't seem that much of a problem, a patch would be simpler
On September 30, 2003 08:16 am, Mike Hearn wrote:
Maybe oneday it would be worth porting the Wine build system to SCons
(http://www.scons.org/). From What makes SCons better:
Whenever I look at make replacements, I always find them more
cluttered/verbose/uglier, but this may be because I'm so
The old dll that MS ships with WindowsXP is comctl32.dll version 5.x which
is the same as on other Windows versions.
Version 6 is the new version. One of the biggest changes is that this updated
dll handles both the user and common controls. Further all controls now
include some area in which
tir, 30.09.2003 kl. 17.16 skrev Dimitrie O. Paun:
On September 30, 2003 09:16 am, Ove Kaaven wrote:
Now the LGPL-ness of Wine
actually makes it an advantage to hold code back from Wine in some
circumstances, whether you and I like it or not.
Your argument is valid right now because there
On Tue, 30 Sep 2003 13:40:50 +0900
Dmitry Timoshkov [EMAIL PROTECTED] wrote:
Steven Edwards [EMAIL PROTECTED] wrote:
I have always wanted to see the Russian Winter so I guess
St. Paul in January is good practice.
Well, the Russian Winter is a common exaggeration, like
a stray bear in
On September 30, 2003 11:51 am, Ove Kaaven wrote:
And it's impossible because the patch we're talking about does not
actually implement copy protection. It only makes Wine implement certain
Windows quirks. For Wine not to implement these quirks in certain APIs
may be considered bugs, and how
On September 29, 2003 03:33 pm, Alexandre Julliard wrote:
No it won't, that's why we need to change bin2res to generate only a
single file at a time, otherwise it breaks parallel makes.
OK, how about this:
ChangeLog
Teach bin2res to deal with one file at a time.
Index: tools/bin2res.c
On Mon, Sep 29, 2003 at 11:33:00AM +0300, Boaz Harrosh wrote:
Just a crazy taught:
What about a twin Wineconf, one in north-America one in Europe taking
place at the same time with live tele-conference. (Europe cameras on me)
I am sure it will be good for publicity, Journalists like that
Dimitrie O. Paun [EMAIL PROTECTED] writes:
On September 27, 2003 07:42 pm, Jakob Eriksson wrote:
Do you want a second file generated apart from the mail
sent to wine-tests-report? (If yes, where should this
file be sent?)
I'm not sure I like this idea. Correlating the two files
is
Jakob Eriksson [EMAIL PROTECTED] writes:
On Sat, Sep 27, 2003 at 02:29:48PM +0200, Ferenc Wagner wrote:
Tester= field should be given slightly more emphasis, and
How can I add more emphasis to it?
Sorry for my vague language, is reflects my vague thoughts.
Currently, it is amongst cryptic
On September 29, 2003 05:31 pm, Ferenc Wagner wrote:
I did not like this idea either, but decided to go with it
in the end. First, to generate summaries I have to
correlate files anyway, which *is* problematic already, and
having a master file could only make it simpler and also
make the
On Mon, Sep 29, 2003 at 11:33:00AM +0300, Boaz Harrosh wrote:
Just a crazy taught:
What about a twin Wineconf, one in north-America one in Europe taking
place at the same time with live tele-conference. (Europe cameras on me)
I am sure it will be good for publicity, Journalists like that
Gerald Pfeifer [EMAIL PROTECTED] writes:
[ 2nd attempt. I really don't see any viable alternative to these
casts; keeping the status quo certainly seems bad. ]
That code is generated, there's no point in fixing it. You need to
change tools/make_requests.
--
Alexandre Julliard
[EMAIL
On Thu, 2 Oct 2003, Mike McCormack wrote:
Robert van Herk wrote:
Mike McCormack wrote:
Ideally, you'd want to write a Gnome VFS module that calls shell32.dll
and queries the shell name space to generate the start menu the same
way Windows does. You need to use some RPC mechanism to
Hi all...
As I understand, right now there are various standards on how to write
menus for Linux, that are incompatible. That would mean that writing a
grand unified ;-) start menu client as I discussed before is currently
impossible.
What could be made already though, is a Wine deamon that
On Tue, 2003-09-30 at 18:13, Alexandre Julliard wrote:
The default is managed mode, and has been for a long time now.
I'm confused then -
[EMAIL PROTECTED] x11drv]$ cvs diff window.c
Index: window.c
===
RCS file:
Mike Hearn [EMAIL PROTECTED] writes:
is_window_managed returns false if none of the conditions match. Is it
the case that one of the conditions will always cause it to return true?
For windows that need to be managed yes. Even in managed mode there
are some windows that are never managed, like
IIRC it does not support Xrender at all.
Yes that would need to be fixed.
Well, the biggest problem would be how to have direct rendering for GL in a
Xnest environment. I have absolutely no idea if this is possible without
hacks.
And then you would also need to add RandR support to Xnest to
On Tue, 2003-09-30 at 21:13, Alexandre Julliard wrote:
For windows that need to be managed yes. Even in managed mode there
are some windows that are never managed, like menus, tooltips, etc.
That's what is_window_managed is for.
I suppose the problem then is that we can't figure out how a
Mike Hearn [EMAIL PROTECTED] writes:
I suppose the problem then is that we can't figure out how a fullscreen
install window is different to a menu or tooltip window. Perhaps in
future they too could be managed but with the appropriate hints to
switch off window decorations, appearing in the
My guess is that Transgaming has signed an NDA with one or more of the
companies that write copy protection schemes for games (eg. Safedisk),
and is not even able to discuss what is required to make such hooks in
Wine, or how to change the build procedure to make it possible for the
scheme to
Is anyone out there an expert in Windows focus handling?
I have problems with our application and the focus handling in places.
Basically it seems to me that there is some sort of logic in windows whereby
the code calls PostMessage (WM_SETFOCUS) but the result is that the parent of
the target
On Tue, 2003-09-30 at 21:57, Dimitrie O. Paun wrote:
In fact, what kind of problems
do we have with InstallShield?
It attempts to do window management across two different desktop windows
causing an X11 ConfigureWindow error. We can't run it outside of desktop
mode because the big blue window
On Tue, Sep 30, 2003 at 10:02:40PM +0200, Robert van Herk wrote:
Would such a system be appreciated by the you people? Or do you think I
should wait untill a better standarization is available? Or do you think
creating a Windows deamon and a Linux client is too much overkill for
such a
On Tue, 30 Sep 2003, Alexandre Julliard wrote:
That code is generated, there's no point in fixing it. You need to
change tools/make_requests.
Here we go. ;-)
(I never had a look at this script before, and it's not documented too
much, but it seems I found the right place to patch nevertheless,
Dimitrie O. Paun [EMAIL PROTECTED] writes:
-- we should include in the master file and the test output
some sort of unique identifier (a MD5 sum of sorts?) so
we make sure we correlate the test output with the correct
master file.
I thought the build tag (which can be any
Dimitrie == Dimitrie O Paun [EMAIL PROTECTED] writes:
Dimitrie On 30 Sep 2003, Mike Hearn wrote:
future they too could be managed but with the appropriate hints to
switch off window decorations, appearing in the window list etc.
Dimitrie It certainly be nice to defer the
On Tue, 30 Sep 2003, Ferenc Wagner wrote:
I thought the build tag (which can be any one-line string)
was enough. Why do we need anything else?
That works nicely IF Jakob builds the tests only on official
releases (which should happen anyway). I guess we can hope
not to do some silly things.
Mike Hearn wrote:
On Tue, 2003-09-30 at 21:57, Dimitrie O. Paun wrote:
In fact, what kind of problems
do we have with InstallShield?
It attempts to do window management across two different desktop windows
causing an X11 ConfigureWindow error. We can't run it outside of desktop
mode because the
Francois Gouget wrote:
rant
The Linux desktop menus are a total mess. FreeDesktop came up with a
broken standard (vfolders) to 'unify' KDE and Gnome (which were already
pretty similar and relatively easy to work with).
But what we need is a truly standard way to create menus for all desktop
Jon Griffiths [EMAIL PROTECTED] writes:
i don't know why this function was changed when it was moved, but it
breaks
some versions of msvcrt. This puts it back the way it was.
There's no reason not to use the version that the user specified. If
you are using XP native dlls and they break with
I'm aware of the scope of the project. The general design of uxtheme lends
itself well to being done incrementally, eg. controls could be modified as
support for the particular control is implemented, etc.
Also part of the API are a few functions (IsThemeActive IsAppThemed) which
will allow
Well I for one am a bit confused. The reason it needs to be a runtime
check is so we can compile Wine on one machine then run it on a totally
different one, and Wine figures out what it can and cannot do on the
fly. If we are altering its behaviour according to the capabilities of
the
On Wed, 1 Oct 2003, Jerry Jenkins wrote:
I knew. I also want it can be compiled once and run on any other machines.
My point is that only the best code should go into the wine, and the test
code I have written is not so¡ :-(. It will give someone many troubles if
he wants to do something
51 matches
Mail list logo