wine-devel

wine-devel@winehq.org

4 participants
84464 discussions

Start a nNew thread

[Fwd: [BUGZILLA] Security Advisory]
by Shachar Shemesh 02 Oct '02

02 Oct '02

Who is maintaining our Bugzilla system? Shachar

2 1

VB app broke again
by Fabian Cenedese 02 Oct '02

02 Oct '02

Hi I recently had a problem with a simple VB app, available as project and exe: http://www.winehq.com/hypermail/wine-devel/2002/09/0627.html I tried again with today's cvs and now the app doesn't even start. There is just an error "not enough memory" and the program quits again. So some recent changes must have broken something. bye Fabi

1 0

Re: some rpcrt4 stuff
by Ove Kaaven 02 Oct '02

02 Oct '02

On Tue, 1 Oct 2002, Greg Turner wrote: > > CHANGELOG: > > * dlls/rpcrt4/rpcrt4.spec: Greg Turner <gmturner007(a)ameritech.net> > - flesh out some stubs. Implementations of these and much more can be found in this patch submission, which was apparently never applied: http://www.winehq.com/hypermail/wine-patches/2002/06/0103.html You can probably try to extract what you need from that patch if you want more rpcrt4 stuff.

1 0

wine ToDo's Final
by Thomas Wickline 01 Oct '02

01 Oct '02

Hello, Here is the ToDo's to put on the status page. If anyone is aware of something that is wrong or out of place please let me know .. If everything looks good I will call it Final.......... Tom Wine ToDo's as of 10/01/02 Contact : twickline2(a)triad.rr.com Wine ToDo OverView Window management: * Window management needs proper inter-process handling of activation, focus, repaint. National Language Support: * Make sure ASCII functions call the Unicode one and not the other way around. * BiDi support * Add support for Hebrew and Arabic * Add support for more keyboard layouts to x11drv * Figure out what should be done for better support of Chinese, Korean, Japanese Winsock: * Winsock1 calls,in particular select(),use direct system calls instead of using related wine APIs * More unit tests need to be written * Make sure OOB data is handled properly. Check client-size blocking. * WS2: Support other kind of services, like IrDA. * Fix stubs left in ws2_32.spec. DirectSound: * Make the latency configurable (tunable). * More intelligent prebuffering. * Complete support for hardware secondary buffers through the HAL (for a future ALSA multimedia wave audio driver). * 3D sound buffers. * Sound capture (recording). Sound drivers: * Alsa driver (on final 0.9 interface) Video: * Implement native codecs (RLE...) GDI: * Write a DIB engine * DIB engine to do 32-bit graphics manipulation GDB: * Add the MSC/PDB info support to gdb Winedbg: * Speed up PDB support DDE: * Enhance memory management issues (interprocess sending) Wineconsole: * Add a (n)curse backend so that we can run CUI programs without using USER32 (and X11 behind) Native programs: * Winhelp: fix invocation thru WinHelp * Winedbg: make winedbg use dbghelp DLL File management: * Implement NT file namespace * UNC support * Allow flexibility in FS "mounting" (for example, SMB shares) Fonts: * Support for non-TT fonts (eg Type1, bitmap, ...) * Support for client side rendering on non-RENDER enabled XServers * Subpixel rendering - a.k.a. ClearType. * Integration with libfontconfig * Reduce per font startup time. * Libfontconfig support Printers: * Write a printer configuation applet * Fix the Type1 font downloader for HP4000 printers Tools: * Wine installation process should install and configure wine * Winemaker fixes * Run C regression tests on Windows with MSVC * Compile Wine with -DSTRICT * Work on WRC as it does not find system headers Instructions: * Write a proper Users Guide Introduction * Documentation updates Aspect or Component: * More DLL Separation * Review of Wine Server Protocol * Finalize Server Protocol * PAM (Pluggable Authentication Modules) * Visual C++'s native COM support * Create replacement of browser component (Internet Explorer/I Porting issues for Mingw/Cygwin/MS_VC * Better seperation of win16/32 code. * Remove/rewite win16/9x api dependancy on newer code * Remove/rewrite wineisms from code * Rewrite/fix unixisms in most WINE dlls * Documentation fixes low priority items: * VxD support with dynamic loading Add links to: Tasklets: http://bugs.winehq.com/buglist.cgi?keywords=tasklet tasklist: http://bugs.winehq.com/buglist.cgi?keywords=tasklist For a full list of .9/1.0 task's

1 0

Re: winapi: new tool winapi_test for generating tests (again)
by Alexandre Julliard 01 Oct '02

01 Oct '02

Patrik Stridvall <ps(a)leissner.se> writes: > You have not applied it or replied. > > I would very must like an answer and > that you at the very least apply the > nocontroversial parts (winapi.*). Sorry, I have applied it now. The only change is that I don't think we should have multiple generated_xxx.c files for each dll, we should put all generated tests for a dll into the same file, so I have renamed the file to just generated.c. I'll let you change the corresponding winapi part. BTW as discussed recently, if you could please do diffs against /dev/null instead of attaching tar files, that would make it easier for me (and may prevent your patches from getting forgotten...) -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Care for write protected resource in propsheet
by Alexandre Julliard 01 Oct '02

01 Oct '02

Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: > Changelog: > dlls/comctrl32/propsheet.c: > Hack around write protected in-memory resources Please let's not add more hacks on top of the existing ones. This thing needs to be fixed properly once and for all. -- Alexandre Julliard julliard(a)winehq.com

2 2

Re: Re: [Version] in ~/.wine/config
by chrismorgan＠rcn.com 01 Oct '02

01 Oct '02

I wasn't able to find any documentation on how the detection works in /documentation. Something is lacking as ie6 setup runs fine if if a version is set and complains about not having a current windows version if not. It might be reading a key that doesn't exist by default, maybe //software//microsoft//windows nt//current version although I didn't capture the trace after I set [Version]. Chris > > From: Andreas Mohr <andi(a)rhlx01.fht-esslingen.de> > Date: 2002/10/01 Tue AM 03:39:52 EDT > To: Chris Morgan <cmorgan(a)alum.wpi.edu> > CC: wine-devel(a)winehq.com > Subject: Re: [Version] in ~/.wine/config > > On Mon, Sep 30, 2002 at 10:20:58PM -0500, Chris Morgan wrote: > > Any reason why we don't default the windows version to something recent like > > Win2K and let the user change this to an older version if necessary? > As has been said some times before, this value is a *forced* value, > which thus overrides Wine's version detection mechanism in case no value is > forced. > IOW: a bad thing to do per default. > > -- > The Declaration of Software Freedom: > http://freedevelopers.net/freedomdec/index.php > > >

1 0

WM_{ERASEBKGND/PAINT} <-> ScrollWindowEx race
by Dimitrie O. Paun 01 Oct '02

01 Oct '02

Hi folks, Some time ago I reported a drawing problem that appeared often in the Common Control Spy. The reason it happens there, is that that application has a listbox which lists messages, and notification received/sent by the control. Well, this listbox scrolls automatically (quite fast at that) as there are quite a few messages/notifications sent, and if you obstruct it partially with a dialog box that you drag around, you can easily replicate the bug. What happens is that a part of the dialog's caption is scrolled up, and not erased. I've attached a snapshot of the problem -- please take a look at it. I was thinking about it, and I think I know what the problem is: 1. you drag the dialog box down 2. this invalidates a portion of the listbox (this invalidated portion contains part of the old caption of the dialog) 3. for whatever reason, the listbox gets new items, and is scrolled (using ScrollWindowEx), *before* it gets a WM_ERASEBKGND/WM_PAINT message. 4. ScrollWindowEx scrolls the content of the window *including* the invalidated area which contains the portion of the caption. *5. ScollWindowEx fails to extend the "scroll" update the portion of the update region (wndPtr->hrgnUpdate). As you can see, the bug happens at step5. That is, if we scroll a rectangle that intersects the update region, we have to "scroll" the update window as well (in the portion that it intersects). For example, say we have a simple update region: [0,50,100,100], and we scroll the rectangle [0,0,100,60] by 30 units up, we have to end up with an update region of [0,20,100,100]. I don't think that we do, right now. Can anyone familiar with the code (dlls/x11drv/scroll.c) take a look, and see what's going on? -- Dimi.

2 1

[Version] in ~/.wine/config
by Chris Morgan 01 Oct '02

01 Oct '02

Any reason why we don't default the windows version to something recent like Win2K and let the user change this to an older version if necessary? Chris

2 1

So long, and thanks for all the fish!
by Guy L. Albertelli 01 Oct '02

01 Oct '02

Hello All, Unfortunately I need to stop most of my work on Wine. This is due to family demands and also that it is not fun anymore. I would recommend that Dimitrie Paun to take over the Common Controls. He has done a great deal of work on them and deserves the honor. I may continue to "lurk" on the lists but do not forsee any activity. Good luck all, and thanks for the friendship. Guy Albertelli <<galberte(a)neo.lrun.com>>

2 1

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