May 2009 - Xquartz-dev - lists.macosforge.org

X11 2.3.3 crash
by Jamie Kennea 15 May '09

15 May '09

Hi, I just had a crash with the new X11 2.3.3. I've attached the crashlog. I wasn't doing very much special, I had a gtk based matplotlib window open, and I closed it, which lead to a beachball, and then crash. Cheers, Jamie

2 2

FYI: major issuie with 2.3.3 and Mac OS X 10.5.7
by Lawson English 13 May '09

13 May '09

I opened this ticket for the issue: http://xquartz.macosforge.org/trac/ticket/263 This is a duplicate of ticket #262 except that I AM running the latest version of x11 already. I had myriad permissions errors but fixed those with the disk utility. I reinstalled x11 2.3.3 and rebooted several times but the symptom remains: when x11 starts up, the app that launched it (e.g. WingIDE) never appears, but if I click on the x11 icon in the dock, the WingIDE window appears, but all MacOS X windows (inluding x11's menu) disappear and a grey background appears. Just a heads up, and wondering if anyone else is seeing this? Lawson

1 1

Can't reopen ticket on MacosForge
by Platon Fomichev 13 May '09

13 May '09

Dear Jeremy I can't reopen ticket #261 on xquartz.macosforge.org. I get 'Warning: No permission to change ticket fields.' As for the ticket - still fails on 2.3.3, so needs to be reopened. Best regards, Platon

4 4

Porting XCopyArea to plain OS X
by Platon Fomichev 13 May '09

13 May '09

Dear Jeremy > I just realized I forgot to ask... have you tried the SIMD > accelerated blt in pixman? Do you suggest that I should grab pixman library and use it in OS X for blitting stuff? In the end I will still have to use CoreGraphics stuff.. Or is there already an OS X specific stuff in this library? Best regards, Platon

2 1

Porting XCopyArea to plain OS X
by Platon Fomichev 13 May '09

13 May '09

Dear Jeremy Here is a bit more wordy explanation about what I am interested in: First of all I am completely oblivious to internal X server code structure so please bare with me. What I am looking at is at xorg- server-1.4.2-apple42/hw/xquartz/xpr/xprFrame.c file where there is a pointer callback structure: static RootlessFrameProcsRec xprRootlessProcs, where there is a xp_copy_bytes function supplied as an accelerated version for blitting stuff. All in all the code in xorg-server-1.4.2-apple42/hw/xquartz is heavily filled with xp_ funcs. So I guess the first question is - what code I should be looking at? Next one is as follows: if not xp* funcs what technology do you use to blit fast to screen? I don't think you're allocating and dropping CImage's or something in that way - it's too slow, thus you're probably using something to do quick drawings and you can somehow get to the 'raw' pixel data for window backing store somehow. Am I right? If yes, how do you do this? The last question was about not XCopyArea for X11 which is O.K. but about an analogue of XCopyArea written for OS X without any X11 support. Suppose I am porting X11 application to pure OS X what can you advise me to use to emulate XCopyArea with source being the window. Here I desperately need your expertise because there does not seem to be a convinient way to do so on OS X (or may be I am mistaken). Last question how do I get very quickly the bitmap bits for the particular window on screen? Getting it using Cocoa is very slow. Using QuickDraw is not an option.. So what to do? Best regards, Platon

2 2

Porting XCopyArea to plain OS X
by Platon Fomichev 13 May '09

13 May '09

Dear List members I've been looking inside the XScreenSaver package to understand some specifics about X11 stuff and I stumbled upon pretty big performance problem in port where the author himself acknowledges he is currently unaware what to do. The author replaced XCopyArea with something like this If source is 'WINDOW' // get the bits (desired sub-rectangle) out of the NSView via Cocoa. // NSBitmapImageRep *bm = [NSBitmapImageRep alloc]; [bm initWithFocusedViewRect:nsfrom]; unsigned char *data = [bm bitmapData]; int bps = [bm bitsPerSample]; int bpp = [bm bitsPerPixel]; int bpl = [bm bytesPerRow]; releaseme = bm; Then CGDataProviderCreateWithData(.. data .. ) CGImageCreate CGContextDrawImage It's quite an overkill - check http://jwz.livejournal.com/628118.html for more information. So the question is - what to do in order to move bits faster in window backing store or whatever i.e. get as close to the real buffer as possible. Lots of stuff hint as libXPlugin as a source of 'acceleration' for X Server. Is there any way to get a public API for it as well as documentation. May be there is some info on CGBlt_copyBytes function in CoreGraphics as well? I am also quite at a loss - I looked at SDL code - they use QuickDraw to get access to video buffer content, yet QuickDraw is deprecated.. So what's the fastest possible memory to draw to window, access and modify it's internal backing store? Best regards, Stauff__

2 1