Re: Problems with Ubuntu packages

[Scott Ritchie]

On Tue, 2007-04-24 at 17:39 +0200, Mirek wrote:
> Hi, I am using Ubuntu FF, and I have some fullsreen issues. In Ubuntu 
> universe is wine 0.9.33 compiled with xrandr support, but on winehq site 
> is repository with wine 0.9.35 compiled without xrandr support. Can 
> someone fix this? I have several fullscreen issues with packages from 
> winehq, but not with original packages from Ubuntu.
> 
> Mirek Slugen
> 
> 

Sorry, I was away from my email this week and couldn't get to your issue
earlier.

You're right, this was a separate issue with the 0.9.35 packages, which
in retrospect were broken in all kinds of ways.  Anyway, I've fixed them
and included the changes into the new 0.9.36 packages.

Hope everything works for you now,
Scott Ritchie

Re: wine killing X?

[Chris Spencer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I get this fairly regularly. After a few runs of any Wine program, the
next time I try and run something it will crash X. I searched on Google
and found something about lack of fonts in
${WINEPREFIX}/dosdevices/c:/windows/fonts, so I put a bunch in there,
and the fonts now look nice, but it still crashes regularly.

- --
Chris.

Juan Lang wrote:
> I just upgraded to the latest wine version and tried wineprefixcreate (no
> .wine directory), and it kills X.  Nvidia drivers 1.0.9755.
> 
> Anyone else see this?
> --Juan
> 
> __
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGMnWFL9xvevzwdSkRAr8+AJ4itPoU8wS6P0E73sOvW1LPsAwPFACZAceA
D8VJ0jj7kB0wP1pJFWDBlSk=
=54SZ
-END PGP SIGNATURE-

Re: wine killing X?

[Stefan Leichter]

Am Friday 27 April 2007 23:25 schrieb Ben Hodgetts:
> Juan Lang wrote:
> > I just upgraded to the latest wine version and tried wineprefixcreate (no
> > .wine directory), and it kills X.  Nvidia drivers 1.0.9755.
> >
> > Anyone else see this?
> > --Juan
> >
> > __
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
>
> Sounds like you need to reinstall your graphics drivers. I bet running
> glxinfo kills X for you too...

If glxinfo kill your X too check /usr/lib/xorg/modules/extensions/libglx.so. 
For the Nvidia driver it should be a symbolic link to 
libglx.so.1.0.

Bye Stefan

Re: wine killing X?

[Ben Hodgetts]

Juan Lang wrote:
> I just upgraded to the latest wine version and tried wineprefixcreate (no
> .wine directory), and it kills X.  Nvidia drivers 1.0.9755.
>
> Anyone else see this?
> --Juan
>
> __
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
>
>
>   
Sounds like you need to reinstall your graphics drivers. I bet running
glxinfo kills X for you too...

Re: wine killing X?

[Tom Spear]

On 4/27/07, Juan Lang <[EMAIL PROTECTED]> wrote:

I just upgraded to the latest wine version and tried wineprefixcreate (no
.wine directory), and it kills X.  Nvidia drivers 1.0.9755.

Worked fine for me.  But I'm not using nvidia drivers or an nvidia card.

--
Thanks

Tom

Check out this new 3D Instant Messenger called IMVU.  It's the best I
have seen yet!



http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email

Re: [programs/regedit] Fix command line processing for /? patch

[Tom Spear]

On 4/27/07, Carl-Daniel Hailfinger <[EMAIL PROTECTED]> wrote:

On 27.04.2007 21:58, Tom Spear wrote:
> On 4/27/07, Tom Spear <[EMAIL PROTECTED]> wrote:
>> On 4/27/07, Tom Spear <[EMAIL PROTECTED]> wrote:
>> > On 4/27/07, Tom Spear <[EMAIL PROTECTED]> wrote:
>> > > On 4/27/07, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
>> > > > You don't want to do that, even if you print usage, an invalid
>> switch
>> > > > needs to cause an error.
>> > > So should we fprintf the usage statement and exit(1); or should we
>> > > print both the usage, and the error for the invalid switch.
>> > >
>> > > Unfortunately I don't have a copy of win98's regedit, and winxp's
>> > > regedit does not accept command line switches (I have tried), so I
>> > > can't check (easily) how the native regedit that ours is supposed to
>> > > be command-line compatible with, does it.
>> >
>> > Neither.  I just figured out why /? is not working.  I can't believe
>> > that I did not think of this before.  The shell processes an unescaped
>> > ?.  In order for it to work, I have to use /\? ..  If I just do /?
>> > then s ends up being /c /d and so ch ends up being c, which makes chu
>> > C (which is missing from the ignored switches if statement)..
>> >
>> > With the old code:
>> >
>> > regedit /c returns "regedit: Undefined switch /C!"
>> > regedit /? returns "regedit: Undefined switch /C!"
>> > regedit /C returns "regedit: Undefined switch /C!"
>> >
>> > The usage shows /c and /C as being valid switches.
>> >
>> > So.. I changed the line
>> >
>> > if (chu == 'S' || chu == 'V') {
>> >
>> > to
>> >
>> > if (chu == 'S' || chu == 'V' || chu == 'C') {
>> >
>> > and so now:
>> >
>> > regedit /c opens regedit
>> > regedit /? shows the usage statement  !
>> > regedit /C opens regedit
>> >
>> > Is this a proper fix?  Can I submit it?  The diff is attached..
>> Further testing shows apparently not, because s is being shifted to
>> the /d now.
>>
>> Any ideas on how to properly capture /? vs having to escape it like
>> /\?  ??
> And even more further testing shows that my distro is wonky.  echo /?
> for me echos /c /d to my terminal  Guess it's time to email Pat
> Volkerding to find out if he can fix it for the next slack release.

That is expected if you have one-letter directories in your root folder.
Try echo "/?"

Wonderful. Thanks for that.  Now I have renamed my symlinks to
~/.wine/drive_c and mnt/d so that they are no longer one letter, and
regedit works as it should!  All this trouble over a stupid directory
name..  Although I do understand why and how it works, now..  That is
extremely annoying, but since regedit is the only wine program that I
know of that uses /? it's not too big of a deal..


--
Thanks

Tom

Check out this new 3D Instant Messenger called IMVU.  It's the best I
have seen yet!



http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email

Re: [programs/regedit] Fix command line processing for /? patch

[Carl-Daniel Hailfinger]

On 27.04.2007 21:58, Tom Spear wrote:
> On 4/27/07, Tom Spear <[EMAIL PROTECTED]> wrote:
>> On 4/27/07, Tom Spear <[EMAIL PROTECTED]> wrote:
>> > On 4/27/07, Tom Spear <[EMAIL PROTECTED]> wrote:
>> > > On 4/27/07, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
>> > > > You don't want to do that, even if you print usage, an invalid
>> switch
>> > > > needs to cause an error.
>> > > So should we fprintf the usage statement and exit(1); or should we
>> > > print both the usage, and the error for the invalid switch.
>> > >
>> > > Unfortunately I don't have a copy of win98's regedit, and winxp's
>> > > regedit does not accept command line switches (I have tried), so I
>> > > can't check (easily) how the native regedit that ours is supposed to
>> > > be command-line compatible with, does it.
>> >
>> > Neither.  I just figured out why /? is not working.  I can't believe
>> > that I did not think of this before.  The shell processes an unescaped
>> > ?.  In order for it to work, I have to use /\? ..  If I just do /?
>> > then s ends up being /c /d and so ch ends up being c, which makes chu
>> > C (which is missing from the ignored switches if statement)..
>> >
>> > With the old code:
>> >
>> > regedit /c returns "regedit: Undefined switch /C!"
>> > regedit /? returns "regedit: Undefined switch /C!"
>> > regedit /C returns "regedit: Undefined switch /C!"
>> >
>> > The usage shows /c and /C as being valid switches.
>> >
>> > So.. I changed the line
>> >
>> > if (chu == 'S' || chu == 'V') {
>> >
>> > to
>> >
>> > if (chu == 'S' || chu == 'V' || chu == 'C') {
>> >
>> > and so now:
>> >
>> > regedit /c opens regedit
>> > regedit /? shows the usage statement  !
>> > regedit /C opens regedit
>> >
>> > Is this a proper fix?  Can I submit it?  The diff is attached..
>> Further testing shows apparently not, because s is being shifted to
>> the /d now.
>>
>> Any ideas on how to properly capture /? vs having to escape it like
>> /\?  ??
> And even more further testing shows that my distro is wonky.  echo /?
> for me echos /c /d to my terminal  Guess it's time to email Pat
> Volkerding to find out if he can fix it for the next slack release.

That is expected if you have one-letter directories in your root folder.
Try echo "/?"

Regards,
Carl-Daniel

Re: [programs/regedit] Fix command line processing for /? patch

[Tom Spear]

On 4/27/07, Tom Spear <[EMAIL PROTECTED]> wrote:

On 4/27/07, Tom Spear <[EMAIL PROTECTED]> wrote:
> On 4/27/07, Tom Spear <[EMAIL PROTECTED]> wrote:
> > On 4/27/07, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> > > You don't want to do that, even if you print usage, an invalid switch
> > > needs to cause an error.
> > So should we fprintf the usage statement and exit(1); or should we
> > print both the usage, and the error for the invalid switch.
> >
> > Unfortunately I don't have a copy of win98's regedit, and winxp's
> > regedit does not accept command line switches (I have tried), so I
> > can't check (easily) how the native regedit that ours is supposed to
> > be command-line compatible with, does it.
>
> Neither.  I just figured out why /? is not working.  I can't believe
> that I did not think of this before.  The shell processes an unescaped
> ?.  In order for it to work, I have to use /\? ..  If I just do /?
> then s ends up being /c /d and so ch ends up being c, which makes chu
> C (which is missing from the ignored switches if statement)..
>
> With the old code:
>
> regedit /c returns "regedit: Undefined switch /C!"
> regedit /? returns "regedit: Undefined switch /C!"
> regedit /C returns "regedit: Undefined switch /C!"
>
> The usage shows /c and /C as being valid switches.
>
> So.. I changed the line
>
> if (chu == 'S' || chu == 'V') {
>
> to
>
> if (chu == 'S' || chu == 'V' || chu == 'C') {
>
> and so now:
>
> regedit /c opens regedit
> regedit /? shows the usage statement  !
> regedit /C opens regedit
>
> Is this a proper fix?  Can I submit it?  The diff is attached..
Further testing shows apparently not, because s is being shifted to the /d now.

Any ideas on how to properly capture /? vs having to escape it like /\?  ??

And even more further testing shows that my distro is wonky.  echo /?
for me echos /c /d to my terminal  Guess it's time to email Pat
Volkerding to find out if he can fix it for the next slack release.

--
Thanks

Tom

Check out this new 3D Instant Messenger called IMVU.  It's the best I
have seen yet!



http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email

wine killing X?

[Juan Lang]

I just upgraded to the latest wine version and tried wineprefixcreate (no
.wine directory), and it kills X.  Nvidia drivers 1.0.9755.

Anyone else see this?
--Juan

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: [programs/regedit] Fix command line processing for /? patch

[Tom Spear]

On 4/27/07, Tom Spear <[EMAIL PROTECTED]> wrote:

On 4/27/07, Tom Spear <[EMAIL PROTECTED]> wrote:
> On 4/27/07, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> > You don't want to do that, even if you print usage, an invalid switch
> > needs to cause an error.
> So should we fprintf the usage statement and exit(1); or should we
> print both the usage, and the error for the invalid switch.
>
> Unfortunately I don't have a copy of win98's regedit, and winxp's
> regedit does not accept command line switches (I have tried), so I
> can't check (easily) how the native regedit that ours is supposed to
> be command-line compatible with, does it.

Neither.  I just figured out why /? is not working.  I can't believe
that I did not think of this before.  The shell processes an unescaped
?.  In order for it to work, I have to use /\? ..  If I just do /?
then s ends up being /c /d and so ch ends up being c, which makes chu
C (which is missing from the ignored switches if statement)..

With the old code:

regedit /c returns "regedit: Undefined switch /C!"
regedit /? returns "regedit: Undefined switch /C!"
regedit /C returns "regedit: Undefined switch /C!"

The usage shows /c and /C as being valid switches.

So.. I changed the line

if (chu == 'S' || chu == 'V') {

to

if (chu == 'S' || chu == 'V' || chu == 'C') {

and so now:

regedit /c opens regedit
regedit /? shows the usage statement  !
regedit /C opens regedit

Is this a proper fix?  Can I submit it?  The diff is attached..

Further testing shows apparently not, because s is being shifted to the /d now.

Any ideas on how to properly capture /? vs having to escape it like /\?  ??

--
Thanks

Tom

Check out this new 3D Instant Messenger called IMVU.  It's the best I
have seen yet!



http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email

Re: [Bug 6788] midi sysex buffer errors

[Christian Costa]

Micha's patch has been applied. Just use version 0.9.36 or latest GIT.
To enable midi debug channel just type :
WINEDEBUG=+midi wine ...
instead of
wine ...

Bye,
Christian

Jos Plompen a écrit :

Where can I find that patch? How do I apply it?
And how exactly can I enable midi debug channel?
thnx,
gosh

On 4/24/07, *Wine Bugs* < [EMAIL PROTECTED] 
> wrote:


http://bugs.winehq.org/show_bug.cgi?id=6788





--- Additional Comments From [EMAIL PROTECTED]
  2007-24-04 16:18 ---
Could you enable midi debug channel with "WINEDEBUG=+midi wine
..." after
applying Micha's patch.

--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are a voter for the bug, or are watching someone who is.




--
MSN: [EMAIL PROTECTED] 
Skype: jos.plompen



  

Re: [programs/regedit] Fix command line processing for /? patch

[Tom Spear]

On 4/27/07, Tom Spear <[EMAIL PROTECTED]> wrote:

On 4/27/07, Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> You don't want to do that, even if you print usage, an invalid switch
> needs to cause an error.
So should we fprintf the usage statement and exit(1); or should we
print both the usage, and the error for the invalid switch.

Unfortunately I don't have a copy of win98's regedit, and winxp's
regedit does not accept command line switches (I have tried), so I
can't check (easily) how the native regedit that ours is supposed to
be command-line compatible with, does it.


Neither.  I just figured out why /? is not working.  I can't believe
that I did not think of this before.  The shell processes an unescaped
?.  In order for it to work, I have to use /\? ..  If I just do /?
then s ends up being /c /d and so ch ends up being c, which makes chu
C (which is missing from the ignored switches if statement)..

With the old code:

regedit /c returns "regedit: Undefined switch /C!"
regedit /? returns "regedit: Undefined switch /C!"
regedit /C returns "regedit: Undefined switch /C!"

The usage shows /c and /C as being valid switches.

So.. I changed the line

if (chu == 'S' || chu == 'V') {

to

if (chu == 'S' || chu == 'V' || chu == 'C') {

and so now:

regedit /c opens regedit
regedit /? shows the usage statement  !
regedit /C opens regedit

Is this a proper fix?  Can I submit it?  The diff is attached..

--
Thanks

Tom

Check out this new 3D Instant Messenger called IMVU.  It's the best I
have seen yet!



http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email


regedit.cmdline.patch
Description: Binary data

Re: Advertize software emulated Direct3D features?

[Stefan Dösinger]

I think I'll add a registry key for this. I do not think we should take users 
the possibility to use existing and working features which may get their 
applications running. This key does not enable / disable vertex blending, 
just the caps. Thus if an app doesn't check the caps properly it will get 
vertex blending even if this key is disabled(and a warning printed asking the 
user to enable vertex shaders)


pgpHIHmN2bZSx.pgp
Description: PGP signature

Re: [programs/regedit] Fix command line processing for /? patch

[Tom Spear]

On 4/27/07, Alexandre Julliard <[EMAIL PROTECTED]> wrote:

You don't want to do that, even if you print usage, an invalid switch
needs to cause an error.

So should we fprintf the usage statement and exit(1); or should we
print both the usage, and the error for the invalid switch.

Unfortunately I don't have a copy of win98's regedit, and winxp's
regedit does not accept command line switches (I have tried), so I
can't check (easily) how the native regedit that ours is supposed to
be command-line compatible with, does it.

--
Thanks

Tom

Check out this new 3D Instant Messenger called IMVU.  It's the best I
have seen yet!



http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-email

[Fwd: [Desktop_architects] DTL: Making Sound Just Work]

[Jeremy White]

I am relaying a request from the DTL work group on sound.

This is a great opportunity for us to let them know what
we need from Linux sound.  I encourage anyone involved
in sound issues to get involved.

Cheers,

Jeremy
--- Begin Message ---


The DTL Sound and Multimedia workgroup is underway!

I need all of your help if we are going to get this rolling quickly. If you
have a background in Linux sound, please get involved or forward to the
member of you organization who can contribute.

We have a wiki page for us to initially gather and store proposals and
ideas. To start things off, I have added several pages to the wiki   ->
http://www.linux-foundation.org/en/Linux_Sound_and_Multimedia

Please review and add info in the following areas:

Users impact: I am looking for more info on the top few pain points and use
cases. We need to focus on a few stacks and environments that cover like
80% of perceived problems. Said another way - we need to get to the point
where we can say "if we fix these 7 things - we'll have a passible solution
for most Linux users".

Business Impact: I would also like to have more info on
marketing/positioning - we need factual info to back up the business need.
It is a clear problem, everybody agrees to that - however, I have had a
hard time qualifying how much desktop opportunity is lost due to
sound/multimedia problems.

Architecture Overview: I am working on some architectural charts showing
how the various functional boxes hook together. This needs work. If you
ever had any question about how complex this is, try to chart it.  ;-)

Interfaces: I need some real feedback on just how hard it would be to
convert or migrate apps to a set of single interfaces. We need to see what
components would be impacted and size the effort. This will have to be an
evolution, but we need to define a path (over the course of the
discussions).

Configuration:  We have got to come to some consensus with the projects and
the distros, maybe a recommended or LSB compliant stack? This must be pre
configured and integrated. There is no reason why a user should have to
install 3 more packages, edit several sets of parameters in config files
and then restart to get sound to work. They will punt.

I believe that our priority should be to produce a strawman proposal for a
single, or maybe a couple of default sound stacks/configurations that "just
work" with the most possible environments. Then, we can focus on the things
that break, and how to fix them.

Thanks everyone. Stay tuned for an initial call to get these discussions
going.  Until then, send me some email or get out on that wiki and get
busy!


Regards,

Kurt R Taylor

International Business Machines, Corp.
11400 Burnet Rd. Austin, TX 78758(512) 838-2496T/L:  678___
Desktop_architects mailing list
[EMAIL PROTECTED]
https://lists.linux-foundation.org/mailman/listinfo/desktop_architects--- End Message ---

Re: Linuxtag 2007 in Berlin

[Stefan Munz]

Hi Michael,

thanks, this saves me some work :-)

Will you be at linuxtag?

cu,

Stefan

Am Donnerstag, 26. April 2007 21:27 schrieb Michael Jung:
> Hi Stefan,
>
> On Wed, Apr 25, 2007 at 05:44:57PM +0200, Stefan Munz wrote:
> > And maybe if anyone has a draft for Wine-posters, this would help too.
>
> I've attached the Inkscape file of the poster we've used at last year's
> LinuxTag.
>
> Bye,

-- 
Dipl.-Inform. Stefan Munz. . . . . . . . . . [EMAIL PROTECTED]
ITOMIG GbR . . . . . . . . . . . . . . . . . www.itomig.de
Sand 14  . . . . . . . . . . . . . . . . . . mobil: +49 178 729 72 72
D-72076 Tübingen . . . . . . . . . . . . . . 


pgpJLOXLX0TTS.pgp
Description: PGP signature

Re: review: add Video Memory text input to winecfg Graphics/Direct3D tab

[Frank Richter]

On 27.04.2007 09:23, Vit Hrachovy wrote:
> Hi,
> the attached patch adds new textbox input 'Video Memory size' for
> Graphics/Direct3D tab of winecfg. Updated every live locale resource to
> include this.

Some thoughts on the UI:
- Maybe make it an editable combobox with common sizes in the dropdown
(64, 128, 256 ...) for convenience.
- It looks like the field is left empty when no video memory setting is
found in the registry. Maybe it's better to show the default value from
wined3d then?

-f.r.

Wiki down

[Alexander Nicolaysen Sørnes]

Does anyone know when the wiki will be up again?  Currently it alternates 
between displaying a 500 internal server error and a python exception + 
traceback.


Regards,

Alexander N. Sørnes

Re: review: add Video Memory text input to winecfg Graphics/Direct3D tab

[Vit Hrachovy]

On Fri, Apr 27, 2007 at 12:14:47PM +0200, Stefan Dösinger wrote:
> On a quick look I see a number of whitespace issues in the patch. in the .rc 
> files you are using tabs while the rest of the code uses spaces at some 
> places, in other lines you're using spaces yourself. In the code you add some 
> trailing whitespace(Git warns about that in rebase and git-am
> 
> As for the German translation you could use "Größe des Grafikspeichers(in 
> Megabytes)"


Hi Stefan, 
thanks for comments, I'm including the fixed patch with added German
translation.
Thanks
Vit

diff --git a/programs/winecfg/Bg.rc b/programs/winecfg/Bg.rc
index 302bec5..a3d9860 100644
--- a/programs/winecfg/Bg.rc
+++ b/programs/winecfg/Bg.rc
@@ -84,12 +84,14 @@ BEGIN
 EDITTEXTIDC_DESKTOP_WIDTH,64,188,40,12,ES_AUTOHSCROLL | ES_NUMBER 
| WS_DISABLED
 EDITTEXTIDC_DESKTOP_HEIGHT,117,188,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 
-GROUPBOX" Direct3D ",IDC_STATIC,8,210,244,50
+GROUPBOX" Direct3D ",IDC_STATIC,8,210,244,60
 
 LTEXT  "Ďîääđúćęŕ íŕ Vertex Shader: ",IDC_STATIC,15,220,105,30
 COMBOBOX   IDC_D3D_VSHADER_MODE,115,218,125,70,CBS_DROPDOWNLIST | 
WS_VSCROLL | WS_TABSTOP
 
 CONTROL "Đŕçđĺřč Pixel Shader (ŕęî ńĺ ďîääúđćŕ îň 
őŕđäóĺđŕ)",IDC_D3D_PSHADER_MODE,"Button",BS_AUTOCHECKBOX | 
WS_TABSTOP,15,237,230,10
+LTEXT   "Video Memory Size (in 
megabytes):",IDC_STATIC,15,232,120,12
+EDITTEXTIDC_VIDEOMEMORY_SIZE,130,232,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 END
 
 IDD_DLLCFG DIALOG DISCARDABLE  0, 0, 260, 250
diff --git a/programs/winecfg/Cs.rc b/programs/winecfg/Cs.rc
index 5bba698..6a91d54 100644
--- a/programs/winecfg/Cs.rc
+++ b/programs/winecfg/Cs.rc
@@ -88,6 +88,8 @@ BEGIN
 COMBOBOX   IDC_D3D_VSHADER_MODE,105,197,140,70,CBS_DROPDOWNLIST | 
WS_VSCROLL | WS_TABSTOP
 
 CONTROL "Povolit stínování pixelů (spoléhá se na hardware 
podporu)",IDC_D3D_PSHADER_MODE,"Button",BS_AUTOCHECKBOX | 
WS_TABSTOP,15,216,230,10
+LTEXT   "Velikost videopaměti (v 
megabytech):",IDC_STATIC,15,232,120,12
+EDITTEXTIDC_VIDEOMEMORY_SIZE,135,232,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 END
 
 IDD_DLLCFG DIALOG DISCARDABLE  0, 0, 260, 250
diff --git a/programs/winecfg/De.rc b/programs/winecfg/De.rc
index 8c77b2b..cc6d43b 100644
--- a/programs/winecfg/De.rc
+++ b/programs/winecfg/De.rc
@@ -78,12 +78,14 @@ BEGIN
 LTEXT   "X",IDC_DESKTOP_BY,114,167,8,8,WS_DISABLED
 EDITTEXTIDC_DESKTOP_HEIGHT,123,167,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 
-GROUPBOX" Direct3D ",IDC_STATIC,8,189,244,38
+GROUPBOX" Direct3D ",IDC_STATIC,8,189,244,60
 
 LTEXT   "Unterstützung für Vertex Shader: ",IDC_STATIC,15,199,120,8
 COMBOBOXIDC_D3D_VSHADER_MODE,140,197,105,70,CBS_DROPDOWNLIST | 
WS_VSCROLL | WS_TABSTOP
 
 CONTROL "Pixel Shader aktivieren (wenn von Hardware unterstützt)", 
IDC_D3D_PSHADER_MODE,"Button",BS_AUTOCHECKBOX | WS_TABSTOP,15,212,230,10
+LTEXT   "Größe des Grafikspeichers (in 
Megabytes):",IDC_STATIC,15,232,135,12
+EDITTEXTIDC_VIDEOMEMORY_SIZE,150,232,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 END
 
 IDD_DLLCFG DIALOG DISCARDABLE  0, 0, 260, 250
diff --git a/programs/winecfg/En.rc b/programs/winecfg/En.rc
index 02d4850..84e77d9 100644
--- a/programs/winecfg/En.rc
+++ b/programs/winecfg/En.rc
@@ -79,12 +79,14 @@ BEGIN
 EDITTEXTIDC_DESKTOP_WIDTH,64,167,40,12,ES_AUTOHSCROLL | ES_NUMBER 
| WS_DISABLED
 EDITTEXTIDC_DESKTOP_HEIGHT,117,167,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 
-GROUPBOX" Direct3D ",IDC_STATIC,8,189,244,50
+GROUPBOX" Direct3D ",IDC_STATIC,8,189,244,60
 
 LTEXT  "Vertex Shader Support: ",IDC_STATIC,15,199,80,30
 COMBOBOX   IDC_D3D_VSHADER_MODE,100,197,145,70,CBS_DROPDOWNLIST | 
WS_VSCROLL | WS_TABSTOP
 
 CONTROL "Allow Pixel Shader (if supported by 
hardware)",IDC_D3D_PSHADER_MODE,"Button",BS_AUTOCHECKBOX | 
WS_TABSTOP,15,216,230,10
+LTEXT   "Video Memory Size (in 
megabytes):",IDC_STATIC,15,232,120,12
+EDITTEXTIDC_VIDEOMEMORY_SIZE,130,232,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 END
 
 IDD_DLLCFG DIALOG DISCARDABLE  0, 0, 260, 250
diff --git a/programs/winecfg/Es.rc b/programs/winecfg/Es.rc
index 34993c2..b4a 100644
--- a/programs/winecfg/Es.rc
+++ b/programs/winecfg/Es.rc
@@ -78,12 +78,14 @@ BEGIN
 EDITTEXTIDC_DESKTOP_WIDTH,64,188,40,12,ES_AUTOHSCROLL | ES_NUMBER 
| WS_DISABLED
 EDITTEXTIDC_DESKTOP_HEIGHT,117,188,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 
-GROUPBOX" Direct3D ",IDC_STATIC,8,210,244,50
+GROUPBOX" Direct3D ",IDC_STATIC,8,210,244,60
 
 LTEXT   "Soporte Vertex Shader: ",IDC_STATIC,15,220,80,30
 COMBOBOXIDC_D3D_VSHADER_MODE,100,218,150,70,CBS_DROPDOWNLIST | 

Re: review: add Video Memory text input to winecfg Graphics/Direct3D tab

[Stefan Dösinger]

Am Freitag 27 April 2007 09:23 schrieb Vit Hrachovy:
> Hi,
> the attached patch adds new textbox input 'Video Memory size' for
> Graphics/Direct3D tab of winecfg. Updated every live locale resource to
> include this.
>
> Adding this option was discussed on thread 'More Direct3D settings in
> winecfg (was: Enabling GLSL in winecfg)' at wine-devel.
>
> changelog entry: Add Video Memory textbox to Graphics/direct3D part of
> winecfg
>
> May I kindly ask someone for the patch review?
On a quick look I see a number of whitespace issues in the patch. in the .rc 
files you are using tabs while the rest of the code uses spaces at some 
places, in other lines you're using spaces yourself. In the code you add some 
trailing whitespace(Git warns about that in rebase and git-am

As for the German translation you could use "Größe des Grafikspeichers(in 
Megabytes)"


pgpzJzM2W8lCi.pgp
Description: PGP signature

Re: Advertize software emulated Direct3D features?

[Stefan Dösinger]

Am Freitag 27 April 2007 09:02 schrieb H. Verbeet:
> On 27/04/07, Stefan Dösinger <[EMAIL PROTECTED]> wrote:
> > I am working on vertex blending support for WineD3D. First I implemented
> > it using GL_ARB_vertex_blend in hardware, an extension that is
> > unfortunately only supported by ati cards, and not nvidia. So I took
> > Frank Richter's started software emulation for vertex blending, with that
> > it works everywhere.
> >
> > The question is wether we should report support for this feature in our
> > d3d caps. Because it is software emulated it forces wined3d into the
> > drawStridedSlow path which is, well, slow. Enabling this may cause a game
> > to choose this slower render path over something else, like vertex
> > shaders. On the other hand it can get applications run that wouldn't work
> > without this feature.
> >
> > For vertex blending it doesn't matter much. Its hardly used, and all
> > games using it provide a vertex shader path too and prefer it(exception
> > are the dx sdk demos). The other alternative the apps have is to either
> > disable the feature entirely, thus have lower graphics quality, or
> > calculate it themselves, which won't be slower than wined3d doing it. So
> > I think we should advertize vertex blending, but the general question
> > remains.
> >
> > What do you think?
> >
> > PS: Ideally we'd have a vertex pipeline replacement in form of a vertex
> > shader, but that wouldn't invalidate the point of this since not all
> > cards support vertex shaders. (And I personally dislike the idea of a
> > pipeline replacement for this reason).
>
> I'd rather not report caps we don't properly support, for the reasons
> you just mentioned. As for the pipeline replacement, I don't really
> see the issue. There are lots of things that older cards don't
> support. If it provides advantages for newer cards, I don't think that
> should be held back because older cards don't support it.
I take that "It won't be slower than the app emulating it" back. The 
skinnedmesh demo runs twice as fast with the apps "software skinning" than 
with wined3d's emulation. I have to investigate why that happens, the mesh 
doesn't look worse with the sw skinning.


pgpAmvmRbuZ4r.pgp
Description: PGP signature

Re: [PATCH] CMD.exe: Remove code duplication for _splitpath

[Alexandre Julliard]

Jason Edmeades <[EMAIL PROTECTED]> writes:

> Note: This makes cmd.exe pull in msvcrt, but so does native

Native doesn't have a choice, but we do. Unless there are good reasons
to import msvcrt it's better to stick to standard libc.

-- 
Alexandre Julliard
[EMAIL PROTECTED]

Re: [programs/regedit] Fix command line processing for /? patch

[Alexandre Julliard]

"Tom Spear" <[EMAIL PROTECTED]> writes:

> --- programs/regedit/regedit.c.old2007-04-25 11:53:24.0 -0500
> +++ programs/regedit/regedit.c2007-04-25 11:57:30.0 -0500
> @@ -104,13 +104,10 @@
>  case 'E':
>  action = ACTION_EXPORT;
>  break;
> -case '?':
> +default:
>  fprintf(stderr,usage);
>  exit(0);
>  break;
> -default:
> -error_unknown_switch(chu, s);
> -break;

You don't want to do that, even if you print usage, an invalid switch
needs to cause an error.

-- 
Alexandre Julliard
[EMAIL PROTECTED]

review: add Video Memory text input to winecfg Graphics/Direct3D tab

[Vit Hrachovy]

Hi,
the attached patch adds new textbox input 'Video Memory size' for
Graphics/Direct3D tab of winecfg. Updated every live locale resource to
include this.

Adding this option was discussed on thread 'More Direct3D settings in
winecfg (was: Enabling GLSL in winecfg)' at wine-devel.

changelog entry: Add Video Memory textbox to Graphics/direct3D part of
winecfg

May I kindly ask someone for the patch review?

Regards
Vit Hrachovy
diff --git a/programs/winecfg/Bg.rc b/programs/winecfg/Bg.rc
index 302bec5..8cdf341 100644
--- a/programs/winecfg/Bg.rc
+++ b/programs/winecfg/Bg.rc
@@ -84,12 +84,14 @@ BEGIN
 EDITTEXTIDC_DESKTOP_WIDTH,64,188,40,12,ES_AUTOHSCROLL | ES_NUMBER 
| WS_DISABLED
 EDITTEXTIDC_DESKTOP_HEIGHT,117,188,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 
-GROUPBOX" Direct3D ",IDC_STATIC,8,210,244,50
+GROUPBOX" Direct3D ",IDC_STATIC,8,210,244,60
 
 LTEXT  "Ďîääđúćęŕ íŕ Vertex Shader: ",IDC_STATIC,15,220,105,30
 COMBOBOX   IDC_D3D_VSHADER_MODE,115,218,125,70,CBS_DROPDOWNLIST | 
WS_VSCROLL | WS_TABSTOP
 
 CONTROL "Đŕçđĺřč Pixel Shader (ŕęî ńĺ ďîääúđćŕ îň 
őŕđäóĺđŕ)",IDC_D3D_PSHADER_MODE,"Button",BS_AUTOCHECKBOX | 
WS_TABSTOP,15,237,230,10
+   LTEXT   "Video Memory Size (in 
megabytes):",IDC_STATIC,15,232,120,12
+EDITTEXTIDC_VIDEOMEMORY_SIZE,130,232,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 END
 
 IDD_DLLCFG DIALOG DISCARDABLE  0, 0, 260, 250
diff --git a/programs/winecfg/Cs.rc b/programs/winecfg/Cs.rc
index 5bba698..4c82063 100644
--- a/programs/winecfg/Cs.rc
+++ b/programs/winecfg/Cs.rc
@@ -88,6 +88,8 @@ BEGIN
 COMBOBOX   IDC_D3D_VSHADER_MODE,105,197,140,70,CBS_DROPDOWNLIST | 
WS_VSCROLL | WS_TABSTOP
 
 CONTROL "Povolit stínování pixelů (spoléhá se na hardware 
podporu)",IDC_D3D_PSHADER_MODE,"Button",BS_AUTOCHECKBOX | 
WS_TABSTOP,15,216,230,10
+   LTEXT   "Velikost videopaměti (v 
megabytech):",IDC_STATIC,15,232,120,12
+EDITTEXTIDC_VIDEOMEMORY_SIZE,135,232,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 END
 
 IDD_DLLCFG DIALOG DISCARDABLE  0, 0, 260, 250
diff --git a/programs/winecfg/De.rc b/programs/winecfg/De.rc
index 8c77b2b..8c8f78e 100644
--- a/programs/winecfg/De.rc
+++ b/programs/winecfg/De.rc
@@ -78,12 +78,14 @@ BEGIN
 LTEXT   "X",IDC_DESKTOP_BY,114,167,8,8,WS_DISABLED
 EDITTEXTIDC_DESKTOP_HEIGHT,123,167,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 
-GROUPBOX" Direct3D ",IDC_STATIC,8,189,244,38
+GROUPBOX" Direct3D ",IDC_STATIC,8,189,244,60
 
 LTEXT   "Unterstützung für Vertex Shader: ",IDC_STATIC,15,199,120,8
 COMBOBOXIDC_D3D_VSHADER_MODE,140,197,105,70,CBS_DROPDOWNLIST | 
WS_VSCROLL | WS_TABSTOP
 
 CONTROL "Pixel Shader aktivieren (wenn von Hardware unterstützt)", 
IDC_D3D_PSHADER_MODE,"Button",BS_AUTOCHECKBOX | WS_TABSTOP,15,212,230,10
+   LTEXT   "Video Memory Size (in 
megabytes):",IDC_STATIC,15,232,120,12
+EDITTEXTIDC_VIDEOMEMORY_SIZE,130,232,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 END
 
 IDD_DLLCFG DIALOG DISCARDABLE  0, 0, 260, 250
diff --git a/programs/winecfg/En.rc b/programs/winecfg/En.rc
index 02d4850..eec9e11 100644
--- a/programs/winecfg/En.rc
+++ b/programs/winecfg/En.rc
@@ -79,12 +79,14 @@ BEGIN
 EDITTEXTIDC_DESKTOP_WIDTH,64,167,40,12,ES_AUTOHSCROLL | ES_NUMBER 
| WS_DISABLED
 EDITTEXTIDC_DESKTOP_HEIGHT,117,167,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 
-GROUPBOX" Direct3D ",IDC_STATIC,8,189,244,50
+GROUPBOX" Direct3D ",IDC_STATIC,8,189,244,60
 
 LTEXT  "Vertex Shader Support: ",IDC_STATIC,15,199,80,30
 COMBOBOX   IDC_D3D_VSHADER_MODE,100,197,145,70,CBS_DROPDOWNLIST | 
WS_VSCROLL | WS_TABSTOP
 
 CONTROL "Allow Pixel Shader (if supported by 
hardware)",IDC_D3D_PSHADER_MODE,"Button",BS_AUTOCHECKBOX | 
WS_TABSTOP,15,216,230,10
+   LTEXT   "Video Memory Size (in 
megabytes):",IDC_STATIC,15,232,120,12
+EDITTEXTIDC_VIDEOMEMORY_SIZE,130,232,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 END
 
 IDD_DLLCFG DIALOG DISCARDABLE  0, 0, 260, 250
diff --git a/programs/winecfg/Es.rc b/programs/winecfg/Es.rc
index 34993c2..6fb8293 100644
--- a/programs/winecfg/Es.rc
+++ b/programs/winecfg/Es.rc
@@ -78,12 +78,14 @@ BEGIN
 EDITTEXTIDC_DESKTOP_WIDTH,64,188,40,12,ES_AUTOHSCROLL | ES_NUMBER 
| WS_DISABLED
 EDITTEXTIDC_DESKTOP_HEIGHT,117,188,40,12,ES_AUTOHSCROLL | 
ES_NUMBER | WS_DISABLED
 
-GROUPBOX" Direct3D ",IDC_STATIC,8,210,244,50
+GROUPBOX" Direct3D ",IDC_STATIC,8,210,244,60
 
 LTEXT   "Soporte Vertex Shader: ",IDC_STATIC,15,220,80,30
 COMBOBOXIDC_D3D_VSHADER_MODE,100,218,150,70,CBS_DROPDOWNLIST | 
WS_VSCROLL | WS_TABSTOP
 
 CONTROL "Permitir Pixel Shader (si hay soporte por 
hardwa

Re: Advertize software emulated Direct3D features?

[H. Verbeet]

On 27/04/07, Stefan Dösinger <[EMAIL PROTECTED]> wrote:

I am working on vertex blending support for WineD3D. First I implemented it
using GL_ARB_vertex_blend in hardware, an extension that is unfortunately
only supported by ati cards, and not nvidia. So I took Frank Richter's
started software emulation for vertex blending, with that it works
everywhere.

The question is wether we should report support for this feature in our d3d
caps. Because it is software emulated it forces wined3d into the
drawStridedSlow path which is, well, slow. Enabling this may cause a game to
choose this slower render path over something else, like vertex shaders. On
the other hand it can get applications run that wouldn't work without this
feature.

For vertex blending it doesn't matter much. Its hardly used, and all games
using it provide a vertex shader path too and prefer it(exception are the dx
sdk demos). The other alternative the apps have is to either disable the
feature entirely, thus have lower graphics quality, or calculate it
themselves, which won't be slower than wined3d doing it. So I think we should
advertize vertex blending, but the general question remains.

What do you think?

PS: Ideally we'd have a vertex pipeline replacement in form of a vertex
shader, but that wouldn't invalidate the point of this since not all cards
support vertex shaders. (And I personally dislike the idea of a pipeline
replacement for this reason).


I'd rather not report caps we don't properly support, for the reasons
you just mentioned. As for the pipeline replacement, I don't really
see the issue. There are lots of things that older cards don't
support. If it provides advantages for newer cards, I don't think that
should be held back because older cards don't support it.