What happened to the Fedora packages? They have not been updated since
0.9.2!!!! Right now it is at 0.9.10!!! Nearly every other Linux distro
supported has the up to date packages!!! And why does the Red Hat packages
site not go to the SourceForge site as it does for SUSE packages and the
others?? I have not really had the guts to ask until now, because I thought
that maybe there was a slump, but now, its getting annoying!! And Fedora
just released Fedora Core 5 yesterday!!! Please tell me new packages will be
ready soon!!! Compiling WINE always crashes my computer, so I prefer to use
the RPMs...
Hi.
>From which configuration does the "ERROR_INVALID_NAME" came from,
when calling GetDefaultPrinter(NULL, &size) and no Printer is installed?
This Test is Present in the current "dlls/winspool/tests/info.c".
MSDN told us, that we receive an "ERROR_FILE_NOT_FOUND", if no Printer
is installed:
http://msdn.microsoft.com/library/en-us/gdi/prntspol_0hma.asp
I get the "ERROR_FILE_NOT_FOUND" on win98se, winme, w2k and win2003 in
this Situation.
--
By By ...
... Detlef
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I think after the 10 or more patches to the Wintab dll that I submitted
last month, I should say something about it's status...
And of course thank Alexandre for applying those patches.
P.S. I won't be available from the 15th for about a week or so.
So, if you have any questions, I'm afraid you might have to be patient.
Hope this is of interest to someone
-Rob.
******Applications: Current status***********
***In Painter 5
*Cursor pressure works. (Therefore is usable by most)
*Cursor orientation is a little odd: The orientation maths needs to be
re-done.
*No eraser. Haven't yet cracked what enables the eraser.
*Doesn't work in desktop mode: Need to map to desktop coordinates.
*Repeats windows bugs where cursor looses pressure/orientation info
almost bug for bug (Is this a feature? ;-)
*Cannot detect pressure/orientation int the "Brush Tracking" window: The
tablet context is attached to the main window, so no events get to the
popup, even if they overlap.
This is not how windows wintab functions.
***In Photoshop 6.
*Can only get tablet data in desktop mode: This is because the tablet
context is attached to the desktop. Which generates/receives no wine
events outside desktop mode.
* Eraser and pen pressure working. *But* to get them working, you must
have 3 XInput devices listed in your XF86Config file, They need to be
the last entries in the "ServerLayout" section and the following order:
eraser, tablet mouse. This is a far from ideal way of specifying the
devices Wintab should use :-/
I'll document this if someone can point me to a good place to put the docs.
*******To Do*************
1. Look at X11 errors. There appear to be some errors that deny some
users the
ability to access Wintab enabled apps. (I think I know how to fix this)
2. Improve orientation data. Orientation comes in as X-Y coords
(Implicit Z), and has to leave as spherical coords. This calculation
needs to be re-done.
3. When tablet context is on top, let it read XInput events from all the
app's top-level windows. (This simulates the fact that the context is
usually designed to cover the whole screen)
4. When tablet context is attached to desktop, read XInput events from
all the app's top-level windows.
5. Tests
~ --My current philosophy on tests is...
~ Use Photoshop & Painter, any formal tests
~ can be written if anyone else gets involved in patching Wintab, to
avoid regressions, and conflict.
**********Long term to do (Anyone interested?):*********
There's a lot of work that could be done here, but what gets done
and who does it probably depends upon whether anyone finds an app that
needs these features. I'd love to implement these, but realistically, I
don't
foresee doing this unless someone hires me to do so ;)
1. Improve configuration of wintab.
Wintab could probably do with some information entered into the
config file, to avoid the user having to
hack their Xfree86cfg file.
2. Handle Z-Order of context properly.
This entails
*sharing Z-Order between apps.
*Working out exactly what role windows have in
determining tablet context z-orders.
*Allow tablet contexts that don't cover the whole
screen/tablet.
*Handle inter-application clipping of tablet contexts
*Allow all application's windows to receive tablet events when tablet
context is on top
3. Implement non-system tablet contexts (Where system cursor not moved
by pen or mouse)
4. Unicodify
5. Implement various wintab extensions.
6. Implement wintab manager functions.
7. Tests.
*********Unknowns*********
1. How are wintab contexts are raised lowered?
Contexts have their own z-order independent of windows, and their own
viewport concept, based upon the tablet's coordinate system, not that of
the OS.
It appears that entering, or clicking on the window the tablet context
is attached to will raise/lower the context.
But I haven't done much testing on this.
In particular, what happens if more than one app request their tablet
context is attached to the desktop?
2. How Painter detects the eraser.
Have 3 possibilities
i. Windows can detect an eraser, and sends specific messages.
(I'm sure I've seen this, but can't work out where!)
ii. Only works if tablet and cursors are named correctly.
(Probably linked to wacom tablets only).
iii. I've missed something
3. Requirements of other applications
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCC8zI2vfwxdLxwWYRAsisAJ4q2gAYTgRc6f9wDI+Ruv943eDxOQCfcl3s
/ZKMUGwQOuw/SIIbOkIUbd0=
=R4M7
-----END PGP SIGNATURE-----
My one win app that makes me a devotee of WINE is TablEdit
(demo at www.tabledit.com/download/tabled32.exe)
has a custom font , tef260.ttf, that has failed to display since
somewhere after ver 9.6. The program installs the font into
c:\windows\font, but can not display it within the program, instead
displaying for the most part, empty squares.
I tried putting/removing tef260.ttf into /usr/local/share/wine/fonts,
/usr/local/share/fonts, and the wine windows/fonts directories in all
permutations. The only way I got it to display was to remove ALL fonts
from these three directories and install tef260.ttf into an X11 font
directory along with other win ttf fonts. This forces WINE to build a
cachedmetrics file like it used to, and the font is displayed properly
in the program.
Hope this is a clue for some developer, as I merely lurk here, looking
for clues about wine behavior. I can't do a regression back to ver 9.6
(the version I was using that last worked) because my upgrades to
freetype cause it to complain of missing functions.
current (pertinent ? ) specs
libfreetype.so.6.3.7 ] built from source
libfontconfig.so.1.0.4 ] built from source
fontforge 20060715 ] built from source
WINE 0.9.20 ] built from source
kernel 2.6.17.11
Slack current (10.2, with upgrades from "current" tree)
--
Timm
I've been trying to get the lpDx array to be properly calculated, but
unfortunately to no avail. I did find, though, that GetTextExtentExPointW is
never called with a maxExt value other than zero, and thus nfit is not
calculated.
Regarding that, would any of you know where I should look for the proper
method of calculating the maximum width (maxExt) of a formatted string? I'm
somewhat puzzled... neither lprect nor dc->BoundsRect seem to hold the
proper values for getting that value [1], or (more likely, I guess) I'm just
looking at it the wrong way.
Btw, I'd add that I've been testing this in Lotus Notes R5, just in case it
helps, and no, I haven't found a link to download a trial. [2] [3]
Cheers,
Pedro.
[1] I'm investigating the SetTextJustification, ExtTextOutW,
GetTextExtentPointW, GetTextExtentPoint32W, GetTextExtentExPointW, and
WineEngGetTextExtentExPoint functions from gdi32 (the latter in freetype.c,
the rest in font.c). I am yet to look into their *I counterparts, where
applicable.
[2] http://appdb.winehq.org/viewbugs.php?bug_id=50
[3] http://bugs.winehq.org/show_bug.cgi?id=7016
Vitaly Lipatov <lav(a)etersoft.ru> writes:
> Try 2, with ncursesw/ncurses detecting
> In order to build wineconsole run properly in utf8 locale, we use ncursesw,
> which can handle wchar strings.
Why would you need wchar strings if you use utf-8? Have you
configured your locale properly?
--
Alexandre Julliard
julliard(a)winehq.org
Hi all,
I've forward ported the old patches of Davin McCall (dsound.patch).
With them I have no more sound underruns etc, I'm therefore looking
for other people to test them as well. I'm welcoming comments on how
it works and possible issues with it.
I also attached my patch to alsa, I'm aware of the things I need to
fix for that, but I thought it might be good to test dsound with
winealsa, to see if other things still need to be fixed.
Cheers,
Maarten
The appdb says
"Only applications which install and run flawlessly on an out-of-the-box
Wine installation make it to the Platinum list"
But several platinum-rated apps seem to deserve
a silver or bronze rating.
For instance, Call to Duty,
http://appdb.winehq.org/appview.php?iVersionId=3603
has all sorts of caveats:
- Punkbuster enabled Multiplayer will not work
- Sound out of sync.
- Runs without crashes, but only if installed as root
- requires whacky third-party Loki installer; real installer
fails on cd change (http://bugs.winehq.org/show_bug.cgi?id=6594)
- "with alsa, the sound lags ~ 1 second behind the game.... if i
choose oss i got the 166 sound files missing error"
And Diablo II, http://appdb.winehq.org/appview.php?iVersionId=49,
also has lots of complaints / caveats / complicated howto's.
Should we impose some standards on appdb ratings?
- Dan
--
Wine for Windows ISVs: http://kegel.com/wine/isv
> Unfortunately, yes. The way the helper window is currently implemented,
> if you remove the WS_CAPTION style, the icon won't be centered when it
> gets docked (in GNOME at least.) I tried that when I put together the
> systray tooltips patch. Ultimately it caused more problems than it
> solved, so I gave up on it. But, it would be really great if you could
> figure it out. :)
I've tried kde, fluxbox and xfce4 (and fvwm, but it lacks systray).
Now I can see that xfce4 suffers from it. I did not noticed that before.
So, I suppose a new patch (attached). Does it work correct with
GNOME? In xfce is OK.
Thanks for pointing the path!
-- Kirill K. Smirnov