wine-devel

wine-devel@winehq.org

84463 discussions

Re: DSTRICT: cast1
by Alexandre Julliard 18 Oct '02

18 Oct '02

Michael Stefaniuc <mstefani(a)redhat.de> writes: > Michael Stefaniuc <mstefani(a)redhat.com> > - silence some warnings due to casts between pointer and > intergers of different size Note that HINSTANCE handles in general cannot be converted by simply truncating the handle, so the places where we do that should be fixed properly. The fact that we get warnings for them with -DSTRICT is a feature, so please don't silence them without making sure the code is right first. -- Alexandre Julliard julliard(a)winehq.com

1 0

tab control work
by Andreas Mohr 18 Oct '02

18 Oct '02

Hi all, I just wanted to let you know that I'm currently doing some tab control work for some German company. If anyone intends to also work on tab stuff, then I'd be happy to know what exactly you intend to do. Thanks, Andi

1 0

winedbg
by Dimitrie O. Paun 18 Oct '02

18 Oct '02

Hi folks, Even though I never use a debugger, I had winedbg startup automatically a few times, and I noticed that I get no text in the console. Actually, I do (as I can select it and copy it), but it doesn't get rendered. I tried changing the font, but the only option I get is "Courier New". Tried different size, but nothing helped. Strange thing is that the sample "This is a test" in the font selection tab works just fine. Any tips for fixing this are highly appreciated. -- Dimi.

3 8

multithreading winelib app
by Malte Starostik 18 Oct '02

18 Oct '02

Hi, before I make some major mistakes: can a winelib app safely use pthreads and run WinAPI functions from multiple threads or will it have to use Windows threads? Thanks, -Malte

3 2

Re: Find the main winelib app with GetModuleHandle
by Alexandre Julliard 18 Oct '02

18 Oct '02

Malte Starostik <malte(a)kde.org> writes: > Check if the name passed to GetModuleHandle() is the name > of the main executable. As those normally don't have an extension > ".DLL" was appended and the search failed. Actually you should give your executable a .exe extension, there are a number of places where we expect that (the Unix wrapper script doesn't need an extension of course, but the .so does). -- Alexandre Julliard julliard(a)winehq.com

3 2

FYI
by Eric Pouech 18 Oct '02

18 Oct '02

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnucmg/htm… didn't read it yet, but could be an interesting introduction for new Wine developpers A+

2 1

Re: FYI
by John K. Hohm 18 Oct '02

18 Oct '02

Thus spake Eric Pouech <eric.pouech(a)wanadoo.fr>: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnucmg/htm… > didn't read it yet, but could be an interesting introduction for new > Wine developpers I got a kick out of the two graphs in chapter 2; one shows increasing Windows versions going up and right with time increasing to the right, the other shows Unix versions going down with time increasing downwards. No subtle clues there, right?

1 0

pragma packing on sparc solaris
by Juraj Hercek 17 Oct '02

17 Oct '02

Hi, I'm trying to get wine working on solaris running on sparc. I have troubles with structure packing, since sparc solaris throws SIGSEGV when writting to structure members not aligned to 4-byte boundary (for example: loader/ne/resource.c:280, where &pTypeInfo->resloader is not aligned to 4-byte boundary). Since I'm new to wine, I'd like to know about packing policies (pragma pack 1,2,...) in wine: 1) When do we use packing and why (optimisation?)? 2) What would happen if pragma packing is ommited or always set to 4? Next, I'd like to know if there will be also non i386 COM proxy implementation (dlls/rpcrt4/cproxy.c and related), since I'm unable to compile newest wine on sparc solaris (currently, I'm using version from October 1st). Thanks for reply. Juraj

6 5

Press: CodeWeavers/Xandros Deal: "Let the Revolution Begin!"
by Dimitrie O. Paun 17 Oct '02

17 Oct '02

>From LinuxWeeklyNews: http://www.consultingtimes.com/articles/codeweavers/codeweaversxandros.html -- Dimi.

1 0

re: d3d8 textures
by Ann and Jason Edmeades 17 Oct '02

17 Oct '02

Hello, Funnily enough I took a look at that last night. I am not convinced d3drs_wrap0 should map to the glTexParameteri(GL_TEXTURE_1D, GL_TEXTURE_WRAP_S, GL_REPEAT) type call, since I was thinking that is what the D3DTSS_ADDRESS{U,V,W} modes seem to map against. If you set it for the TextureStage (D3DTSS_*) then I am guessing you need to reapply the current stage's values during SetTexture. However, I then couldnt find any equivalent to d3drs_wrap0 type calls, so gave up and went to bed... All help on d3d8 very gratefully accepted! Regards, Jason

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel