Lionel Ulmer <lionel.ulmer(a)free.fr> writes:
> The only problems I could see with this approach is that :
>
> - it cannot 'expect' more than one kind of error at the same time
I was thinking you could use a special value as a "wildcard" for the
error codes, in which case it wouldn't be tested for a match.
> - I am not sure that the parameters thing are really a good idea. Are we
> sure that the error code are the same on all X servers ? Are they
> standardized ?
They are part of the X spec AFAICT, so yes it should be pretty much
standard.
--
Alexandre Julliard
julliard(a)winehq.com
Hi there, I'm working in a telerobotics project and I need to link a
windows dll in order to use a Cybernet Joystick.
First I tried to use the winAPI functions LoadLibrary,FreeLibrary
and
GetProccessAddress as I were working on Windows, and I recompiled my program
with winelib:
*. winemaker /my_path/
*. ./configure
*. make all
but it didn't create any executable, what I obtained was a lib*.so,
because
winemaker thought I was trying to compile a dll, not to use one.
After that I tried to compile my program without winemaker, and I
obtained
a HEAP_PTR error when executing what I copiled. And If I tried to link the
lib*.so and load the main symbol I obtained the same error.
So my question is quite siple How can I link a native dll in a Unix
project? I've read somewhere that I have to use a parser, Is there anybody
who can give me some code?
Thanks for your precious time.
_________________________________________________________________
Descargue GRATUITAMENTE MSN Explorer en http://explorer.msn.es/intl.asp
Fully implement DrawText* functions.
- Travis Michielsen
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
Marco Bizzarri <m.bizzarri(a)icube.it> writes:
> While looking at the source code of wine, I looked into the synopsys of
> the CallWindowProc function. According to winproc.c, the hWnd parameter
> should be the handle to the window which has to receive the message.
>
> OTOH, if you look at MSDN, at
>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/hh/w…
>
> it looks like the hWnd is the windows procedure which should receive the
> message.
hWnd is clearly a window handle, not a window procedure. As a rule,
any resemblance between what MSDN says and what the code actually does
is purely fortuitous.
--
Alexandre Julliard
julliard(a)winehq.com
Hi
I tried Jul 23 cvs of wine and winex and tried with Nox and Half Life.
Both wine and winex work fine with the stock kernel sound drivers (es1371)
but they do not work well with alsa with oss emulation. The sound gets
played extremely fast in Half-Life like someone hit the fast-forward
button. It is strange because the timing on the alsa oss-emulation (and
commercial oss drivers) is better than the stock kernel drivers.
Winex does a lot of improvement in Half-Life and it is fully
playable (the splash, the menu and everything).
Nox works near perfect with wine but it does not work at all with winex.
FT
Hi there, I'm working in a telerobotics project and I need to link a
windows dll in order to use a Cybernet Joystick.
First I tried to use the winAPI functions LoadLibrary,FreeLibrary and
GetProccessAddress as I were working on Windows, and I recompiled my program
with winelib:
*. winemaker /my_path/
*. ./configure
*. make all
but it didn't create any executable, what I obtained was a lib*.so, because
winemaker thought I was trying to compile a dll, not to use one.
After that I tried to compile my program without winemaker, and I obtained
a HEAP_PTR error when executing what I copiled. And If I tried to link the
lib*.so and load the main symbol I obtained the same error.
So my question is quite siple How can I link a native dll in a Unix
project? I've read somewhere that I have to use a parser, Is there anybody
who can give me some code?
Thanks for your precious time.
_________________________________________________________________
Descargue GRATUITAMENTE MSN Explorer en http://explorer.msn.es/intl.asp
Hi all.
While looking at the source code of wine, I looked into the synopsys of
the CallWindowProc function. According to winproc.c, the hWnd parameter
should be the handle to the window which has to receive the message.
OTOH, if you look at MSDN, at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/hh/w…
it looks like the hWnd is the windows procedure which should receive the
message.
Can anyone help?
Thanks
Marco Bizzarri
m.bizzarri(a)icube.it
Ian Pilcher <ian.pilcher(a)home.com> writes:
> If all pointers have to be eliminated, I can't see any way to do it.
> In order for the code to have any kind of sanity, built-in font metrics
> and dynamically loaded font metrics have to use the same data model, and
> I don't think it's even remotely practical to get rid of the pointers in
> the case of the dynamically loaded metrics.
Well, if it's not feasible so be it. But if it's at all possible I
think it's worth some reasonable amount of trouble.
> I'm open to suggestions, but I think that the effort involved in doing
> this (assuming a sane way could be found) probably far outweighs the
> benefit (less swap usage if the data is paged out; is there any other
> benefit?).
The main benefit is sharing between processes; so if you have 10
processes that want to print you only have one copy of the font data
in memory. Plus it gets loaded on-demand so data that isn't used
doesn't need to be loaded from disk at all.
> Just in case I get inspired, though, what tool/command are you using to
> determine read-only vs. read/write data sizes? Can I just go by what
> objdump says about .data and .rodata?
objdump is fine yes. size works too, though I seem to remember some
versions not counting .rodata correctly.
--
Alexandre Julliard
julliard(a)winehq.com
Ian Pilcher <ian.pilcher(a)home.com> writes:
> Log message:
> Ian Pilcher <ian.pilcher(a)home.com>
> WINEPS: make built-in font data read-only
Unfortunately the data still isn't stored in read-only memory even
though it is declared const, because the structures contain pointers
that require relocation. Would it be possible to store offsets instead
of pointers?
--
Alexandre Julliard
julliard(a)winehq.com
On Tue, 24 Jul 2001 11:11:05 +1000 Mike McCormack
<mike_mccormack(a)start.com.au> writes:
> This is a multi-part message in MIME format
>
> ------=_NextPart_000_83577347
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 7bit
>
>
> This patch completes the seperation of the 16bit COMM code from
> KERNEL
> and moves it to USER. Seems to work with Terminal from WFW 3.11.
>
> Mike
If you get this, it seems to work for juno 1.49 too.
Lawson
---oof---
> ChangeLog:
> move 16-bit COMM code to USER dll
>
>
________________________________________________________________
GET INTERNET ACCESS FROM JUNO!
Juno offers FREE or PREMIUM Internet access for less!
Join Juno today! For your FREE software, visit:
http://dl.www.juno.com/get/tagj.
