Sounds about just like the older Fake Fullscreen mode, but instead uses the
10.7+ Fullscreen instead of just putting up a shield window to black everything
out.
On Oct 2, 2012, at 10:17 PM, Ken Thomases wrote:
>
> I think you've misunderstood his request. He's looking for the
> new-since-L
e.ref);
> lastUsedMode = pQuartzScreen->currentMode;
> CFRetain(lastUsedMode.ref)
>
>
>> ---
>>
>> It also looks like you may be using lastUsedMode uninitialized.
>>
>> It was probably the case that CG just returned an error in Lion and is
>> cra
s long as I can use them to trigger the bug.
>
> Thanks,
> Jeremy
>
> On Aug 26, 2012, at 05:47, doh123 wrote:
>
>> I'm just looking for a bit of help, plus a suggestion (this "feature" I add
>> should be put in XQuartz)
>>
>> I add somethi
he crash log.
>
> Also, would you mind posting the patches that you described, so I can try it
> out on my system? It doesn't matter if they're not generalized enough to be
> integrated yet... as long as I can use them to trigger the bug.
>
> Thanks,
> Jeremy
>
I'm just looking for a bit of help, plus a suggestion (this "feature" I add
should be put in XQuartz)
I add something to my custom build (WineskinX11) thats very minor thats not
normally in XQuartz, but you should really add it. My problem is that the
current way I have it working, it has alwa
well that one compiles, but it didn't change the crash any… :-(
On Apr 28, 2012, at 6:52 PM, Jeremy Huddleston wrote:
>
> On Apr 28, 2012, at 12:24, doh123 wrote:
>
>> well this line doesn't work…
>>
>> while (0 == d->unlock(d));
>>
>&g
95a17534c2694760300701fee59a320950f271
>
> A proper fix would involve rewriting all the complicated locking logic, but
> here's an ugly hack that I'd like you to try:
>
> <0001-darwin-Eliminate-a-possible-race-condition-while-des.patch>
>
> Please give that a whirl
When I run Oblivion with Wine in this RC, its not working. I went back to Beta4
and it works in beta4 fine, but in RC 1 I get this…
fixme:coreaudio:get_channel_mask Unknown speaker configuration: 16
fixme:coreaudio:get_channel_mask Unknown speaker configuration: 16
fixme:win:EnumDisplayDevicesW (
It doesn't look like this fixes the bug I thought it might… when a Wine program
starts out in a maximized state, often the actual Windows program looks normal
but the quartz-wm window is fully stretch out with the contents small in a
normal window size, with the rest of the actual maximized wind
I have a minor issue, that affects me a lot in Wineskin, but its reproducible
in XQuartz… I was wondering if maybe I can get a pointer of where to look in
the code.. of what might be causing it.
I'll try to explain the situation. Running Oblivion through Wine, if XQuartz
is already running, th
I've seen this in the past… check if its the same thing… your /tmp/.X11-unix
sometimes gets messed up. Delete it in terminal and see if XQuartz starts.
On Feb 11, 2012, at 9:11 AM, Phoenix Gabriel wrote:
> Endless crash-loop (opens, closes, opens, closes...). No error messages shown.
>
> This
o disable them anyways.
XQuartz has come a long way in the last couple of years :-)
On Sep 29, 2011, at 2:47 PM, Jeremy Huddleston wrote:
>
> On Sep 29, 2011, at 12:35, doh123 wrote:
>
>> Only got 3 game I can find I already have here that have an option to change
>>
blems
> with fullscreen applications. You said you've been using early 2.6.x, but
> those had known issues with fullscreen. I forget if 2.6.3 had all the fixes
> or not. I'd recommend trying 2.7.0_beta2 because I know it has all the
> quartz-wm fullscreen fixes and a shin
. You said you've been using early 2.6.x, but
> those had known issues with fullscreen. I forget if 2.6.3 had all the fixes
> or not. I'd recommend trying 2.7.0_beta2 because I know it has all the
> quartz-wm fullscreen fixes and a shiny new libGL for GLX.
>
>
3e10
>
> Try applying that patch on top of 1.10.2.902 to see if your issue goes away.
>
> On Sep 28, 2011, at 23:17, doh123 wrote:
>
>> I'll test more fullscreen apps, but I've had tons of people complain about
>> fullscreen apps not working right in Wineskin
part my problem goes away and the focus works fine without quartz-wm… but I'm
trying to figure out why x_was_active is set to NO, then automatically checked
if its YES …? I'm probably missing something I'm sure.
On Sep 28, 2011, at 12:00 AM, Jeremy Huddleston wrote:
>
> O
ommit/?id=c8b80a82d97d92d445c1c0af6dba42c9de7c56cd&h=server-1.10-apple
On Sep 28, 2011, at 12:00 AM, Jeremy Huddleston wrote:
>
> On Sep 27, 2011, at 7:49 PM, doh123 wrote:
>
>> Thanks for the help. I have narrowed down the the problem does not exist in
>> 1.10.0,
e back, or the window
will draw in the wrong areas, or the graphics will become corrupted, or often
the screen just goes solid white and can usually still hear the sound there is
just no picture.
On Sep 27, 2011, at 8:34 PM, Jeremy Huddleston wrote:
>
> On Sep 27, 2011, at 17:
with some Mouse handling code is in
darwin.c, and it does have some major changes since the 1.9 branch.
I guess I'll figure it out eventually :-)
On Sep 27, 2011, at 5:07 PM, Jeremy Huddleston wrote:
>
> On Sep 27, 2011, at 13:38, doh123 wrote:
>
>> well I went ahead
If I learn to type and Proof-read… the problem does NOT happen with 1.9.3,
only when I throw in the 1.11.1 server. Since the new build was having the
problems I thought just for a test I'd drop in the old server executable.. and
it works fine.
On Sep 27, 2011, at 3:38 PM, doh123 wrote:
t; build in which
the problem appears. Since I already have some of my own patches that will go
on for a final build, I do not mind if I can modify something in the source to
fix the problem.
On Sep 27, 2011, at 1:48 PM, Jeremy Huddleston wrote:
>
>
> On Sep 27, 2011, at 10:25 AM, d
xorg-server, I'm confused
why this is happening to me when I build it myself. Any suggestions of where
to look to fix the problem would be appreciated, as I know very little about
how its initializing or handling the mouse and keyboard focus.
Thanks!
-doh123
aranteed to work across
> versions of the OS. The *new* exception to this is that I expect
> /opt/X11/lib/libXplugin.1.dylib from 2.7.0 to work on both Snow Leopard and
> Lion.
>
> --Jeremy
>
> On Sep 15, 2011, at 3:49 PM, doh123 wrote:
>
>> ahhh… thanks! thats gre
uddleston wrote:
>
> On Sep 15, 2011, at 7:02 AM, doh123 wrote:
>
>> A quick question…
>>
>> What (or where in the code) determines what quartz-wm window decorations
>> look like. Meaning… where does it determine if it looks like 10.5, or 10.6
>> or 10.7?
A quick question…
What (or where in the code) determines what quartz-wm window decorations look
like. Meaning… where does it determine if it looks like 10.5, or 10.6 or 10.7?
I ask because in Wineskin, I use primarily a 10.5 build, and running it on 10.6
or 10.7, the windows still look like 10
That is odd... my libpixman-1.0.dylib is also 21.0.0, but quartz-wm has no
problems with it...
On Jul 21, 2011, at 9:35 AM, Christof Wolf wrote:
> Hi Jeremy,
>
> I've updated from 10.6.3 rc2 to 10.6.3
>
> quartz-wm crashes because of the wrong libpixman-1.0.dylib. Please see the
> console lo
; On Jun 23, 2011, at 20:19, doh123 wrote:
>
>> I don't use startx... just run the main xserver executable directly (the
>> X11.bin file in XQuartz.app).
>
> Well, that actually executes startx (or triggers launchd to execute startx)
> ...
>
>
>
/tmp is a temp folder for use by programs... its full
read/write there to be used in ways such as this. If you find another way to
get xkb to initialize properly with a dynamic path, be sure to let me know :-)
On Jun 23, 2011, at 7:54 PM, Tony Bernardin wrote:
> thanks for the reply
always be, but they like it in /opt :-)
Oh I'd recommend probably editing the source to read the xmodmap from somewhere
in through /tmp/whatever too, since by default it only uses ~/.Xmodmap, and you
never know what some user might have that messes thing up.
-doh123
On Jun 23, 2011, at 5:
I just want a little input, as I'm not sure exactly where this bug lies...
I can only reproduce this when using Wine on Xquartz with quartz-wm.
The problem is, if you maximize a window ever with the green button... even if
you press it again to restore former size, manually resize.. whatever...
ustom build for
Wineskin, but since thats not being used as a general purpose X11 server, it
doesn't make it a big deal...
On Jan 30, 2011, at 1:17 PM, Dave Ray wrote:
>
> Doh123 wrote:
>
>> That is actually very easy to do.
>>
>> just set a $DISPLAY, then r
(hopefully this message will go through... having trouble with the list)
That is actually very easy to do.
just set a $DISPLAY, then run X11.bin directly for that $DISPLAY.. then you can
launch any wm you want on that same $DISPLAY...
like...
cd into Xquartz/Contents/MacOS
do a... export DISPLA
t appears to be stuck on input on the
secondary monitor, and clicks and movements are mainly over there... which is
odd. I think if i fix the first problem, the second problem here might fix
itself.
On Jan 27, 2011, at 1:45 PM, Jeremy Huddleston wrote:
>
> On Jan 27, 2011, at 10:20, do
he primary monitor so that it has and
can use all the primary monitor's resolutions, as well as the rootless two
screen resolution... this is what it seems that Codeweaver's does with
Crossover too.
On Jan 25, 2011, at 12:40 AM, Jeremy Huddleston wrote:
>
> On Jan 24, 20
Thanks for the info!
I have screen capturing working right (for Wineskin anyways), and I'm able to
use CMD+Opt+A to switch out of fullscreen to a unmovable window in Rootless,
then I'm also able to press that same key combo in rootless to take it back to
fullscreen at the last resolution if the
RandR changes modes, unless changing to
rootless... so I can call that mode anytime someone is in Rootless and presses
the key combo. I'm just not sure where to put lastKnownRandRMode that it will
... survive.
On Jan 24, 2011, at 1:29 PM, doh123 wrote:
> When I CMD+Alt+A it seems to draw
in that do the same
thing) toggle correctly to go back to a captured fullscreen.
On Jan 24, 2011, at 2:20 PM, Pelle Johansson wrote:
> 24 jan 2011 kl. 20.29 skrev doh123:
>
>> Since it switches from Fullscreen to a little fullscreen block stuck on the
>> desktop, I'd su
you can
tell me to look for this stuff would be appreciated... or if you have a better
idea of how it should work.
-doh123
On Jan 24, 2011, at 12:32 PM, Jeremy Huddleston wrote:
> If we are to do something like this, I'd like to maintain consistency with
> what CodeWeavers does.
wrote:
>
> On Jan 23, 2011, at 23:20, doh123 wrote:
>
>> Question...
>>
>> Where/How would I go about putting a shortcut key command in Xquartz?
>
> Check out sendEvent in X11Application.m
>
>> basically when the display is captured, theres no way to
not ideal
:-)
attached is the current screen capturing patch that seems to work ok so far.
dcapture.patch
Description: Binary data
On Jan 23, 2011, at 6:49 PM, Jeremy Huddleston wrote:
>
> On Jan 23, 2011, at 16:37, doh123 wrote:
>
>> yeah, the captured display is always like
robably be great
for fullscreen gaming in X with multi monitors
On Jan 23, 2011, at 6:49 PM, Jeremy Huddleston wrote:
>
> On Jan 23, 2011, at 16:37, doh123 wrote:
>
>> yeah, the captured display is always like a 2 billion level on the shielding
>> window... I'm ju
, 2011, at 6:49 PM, Jeremy Huddleston wrote:
>
> On Jan 23, 2011, at 16:37, doh123 wrote:
>
>> yeah, the captured display is always like a 2 billion level on the shielding
>> window... I'm just not sure how to actually code the changes to tell it to
>> change t
the shield.
On Jan 23, 2011, at 5:49 PM, Jeremy Huddleston wrote:
>
> On Jan 23, 2011, at 15:16, doh123 wrote:
>
>> ok... first, I've been playing with Display Capturing some, though I haven;t
>> really gotten anywhere. Every time I have it capture the display it
in Xquartz if the Crossover X
server can do it.
-doh123
On Dec 10, 2010, at 11:22 AM, Jeremy Huddleston wrote:
>
> On Dec 10, 2010, at 07:13, doh123 wrote:
>
>> I know the display capturing issues are complicated... I'm going to spend
>> some time on my Christmas
30 AM, Jeremy Huddleston wrote:
>
> On Dec 9, 2010, at 23:22, doh123 wrote:
>
>> Multi Monitor fix is nice...
>
> It just fixes the mode-change regression... it doesn't add support for the
> extended resolution changes.
>
>> does it actually use display c
Multi Monitor fix is nice... does it actually use display capturing? I'll try
it out in the next couple of days hopefully
On Dec 10, 2010, at 12:28 AM, Jeremy Huddleston wrote:
> I just released the first release candidate of XQuartz 2.6.0. This is the
> first pre-release built for Leopard as
46 matches
Mail list logo
