are apparently independent of Win32 attributes. If
Cygwin doesn't have anything like this, I think it would be a good Win32
utility to include (i.e. sort of like regtool).
Thanks,
Joe Krahn
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http
updating some packages with files in
/usr/X11R6, I ended up with new files installed in /usr/X11R6 while the
symlink name of the same name still existed.
Joe Krahn
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
by default?) and
are linked with -lOPENGL32. The X11 headers are under /usr/X11R6/include
and are linked with flags as you describe above.
Joe Krahn
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation
' for your X in Windows needs. Actually I am
currently working on a Linux on Windows product that has its own X
Server port via a frame buffer driver. Very cool! Don't port your
Linux code, run it natively!!!
Joe Krahn wrote:
What is the history of internal versus external Win32 WMs? It seems
I cam across this description of an X server design within windows:
http://research.compaq.com/wrl/DECarchives/DTJ/DTJL03/DTJL03.HTM
It has a Win32 WM interface that is functionally seperate, and uses
Win32 Hooks to proxy Win32 WndProc messages; essentially the same as I
recently suggested.
What is the history of internal versus external Win32 WMs? It seems that
Cygwin/X is favoring the internal WM, even though the external WM is a
better fit to the X server design.
I was looking into adding some NET_WM/EWMH features (mainly icons for
now), and realized that most things have to
Colin Harrison wrote:
Hi,
Another decision is what executables and dlls are built in distributions?
Do we provide:-
1) Support for GL and Mesa only by two builds (current situation), where GL
version is faster but less universally applicable?
There should be one build with both renderers,
Peter Valdemar Morch wrote:
Joe Krahn jkrahn-at-nc.rr.com |Lists| wrote:
3) Decide if Win95/Me/NT/2000 need continued support.
Win 2000 - yes please...
OK, I was thinking this might be the one case where it may be needed for
a while. Can you build and/or test code changes?
Thanks, Joe
Alexander Gottwald wrote:
On Fri, 2 Sep 2005, Joe Krahn wrote:
GetModuleHandle(NULL) is also in several places. Maybe it's OK, but why
not use the hInstance global?
Global variables are bad(TM). With GetModuleHandle(NULL) there is no need
to maintain a global hInstance. The other reason
Colin Harrison wrote:
Hi,
All your diffs seem to work almost correctly (see below), but still testing.
In windialogs.c:-
Should SM_CXICONSM be SM_CXSMICON, SM_CYICONSM be SM_CYSMICON ?
Also had to remove the conditional on XWIN_MULTIWINDOW to get X icons
It looks like that part of the code
Colin Harrison wrote:
Joe Krahn wrote:
When I use the CVS defaults, only multi-window mode is built, so I didn't
see the #ifdef XWIN_MULTIWINDOW code compiled. Why is only one version
built? Is it rootless mode that gets excluded?
Mystery to me..the code is loaded with many ifdef's, the use
I didn't get around to finishing ARGB type icons yet, but here's some
related patches for MultiWindow mode.
See icon_and_class.diff at http://joekrahn.homelinux.com/XWin/
The code was changed to use a single Window class for all windows. Icon
changes are sent to the Window instead of changing
-designed enough to do such
things, even if the remote host has a different binary format. You'll
never see that from MS...
Joe Krahn
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http
not. Maybe just try an ARGB
icon patch and see if someone can test it?
Joe Krahn
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com
There are several GetDC(NULL) statements. Should these really be
GetDC(hwndScreen)? It might make a difference for two screens with
different pixel layouts.
GetModuleHandle(NULL) is also in several places. Maybe it's OK, but why
not use the hInstance global?
These probably are just too low
Soong, SylokeJ wrote:
How to indecisively start more than one X display on my XP system?
Currently I have a startxwin.bat:
SET DISPLAY=127.0.0.1:0.0
..
run XWin -screen 0 1750 1350 -whateverelse
run wmaker
as well as startxwin1.bat:
Joe Krahn wrote:
...
It looks like can go from a device dependent X Pixmap (DDPixmap) to a
device dependent Win32 bitmap (DDBitmap), then use Windows functions to
scale when needed. This can only work if pixel data formats are the same
between Windows and Cygwin/X. Does anyone know
Joe Krahn wrote:
Soong, SylokeJ wrote:
How to indecisively start more than one X display on my XP system?
Currently I have a startxwin.bat:
SET DISPLAY=127.0.0.1:0.0
..
run XWin -screen 0 1750 1350 -whateverelse
run wmaker
as well as startxwin1.bat
Colin Harrison wrote:
Hi,
Here are my screen dumps
http://www.straightrunning.com/test/icons_working.png
http://www.straightrunning.com/test/icons_faulty.png
Ignore the taskbar entries for [EMAIL PROTECTED] they are my PuTTY shells.
Shows icon stripes and crappy X icon on exit window (exit
run the right X program.
Joe Krahn
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
the file name (just as with CPP).
Joe Krahn
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Alan Hourihane wrote:
I've just committed a couple of fixes which should cure the immediate
problems.
Let me know if something still doesn't work right.
Alan.
Yes! the whole build went OK, except for a patch to xedit/lisp to work
around the problem of #including the wrong xedit.h.
I also
Has anyone gotten a full build to work recently? I got past the
compsize.c changes in building the GL libs, but ran into similar
problems in server GLX code.
What is the relationship of Cygwin xc/ to the main Xorg xc/?
Joe Krahn
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe
on the GCC
version. Cygwin (and others?) does not support this either, but it is
less critical because it seems to only cause attribute ignored warnings.
Joe Krahn
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation
as xedit.h.
This occurs from bash and tcsh, so it must be in some low-level
unix-to-win32 path name processing.
Joe Krahn
Cygwin Configuration Diagnostics
Current System Time: Sun Aug 21 17:35:58 2005
Windows XP Home Edition Ver 5.1 Build 2600 Service Pack 2
Path: C:\cygwin\home\krahn\bin
path validation could be a significant slow-down, but
dir/.. is not part of most path names, so doing it 'right' should have
a minimal performance impact.
Joe Krahn
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
attempts at accelerated OpenGL
support. Any ideas? Could this relate to the version of headers in
/usr/include/GL?
I was hoping to tweak the Tray icon a bit. When I exit X, the icon stays
as a 'zombie', and disappears on mouse-over.
Joe Krahn
gcc -shared -Wl,--out-implib=libGL-1.dll.a
-Wl
slowed down.
I noticed that csrss.exe is new with XP SP2.
Maybe it's involved in querying process information,
and does not play well with CygWin?
Thanks,
Joe Krahn
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation
The following prototype in wingdi.h should not have the
CONST qualifier for COLORREF. Perhaps it was mis-copied
from the wglSet... function?
WINGDIAPI int WINAPI wglGetLayerPaletteEntries(HDC, int, int, int,
CONST COLORREF *)
--
Unsubscribe
29 matches
Mail list logo
