Re: Building wxt terminal for OS X

[Joe K. <jko...@co...>]

on 10/10/06 3:23 PM, Ethan Merritt at merritt@u.washington.edu wrote:

> On Tuesday 10 October 2006 02:04 pm, Joe Koski wrote:
>> 
>> On a Mac, as with X11, one window at a time has, what I think X11
>> calls focus, i. e., only one window is interactive at a time. The wxt
>> window refuses to become an interactive window, and you can't drag it
>> around the screen with the cursor on the border like you can other
>> windows.
> 
> ???   That last bit is really strange.  "Focus" controls where the
> input event go.  If you type on the keyboard, who is listening?
> If you click the mouse, who gets first chance to respond?
> 
When you have not selected a particular window, the Mac "Finder" is what you
are interacting with. There are keyboard shortcuts you can use, and you
always have your pull down menus at the top of the screen, the dock at the
bottom of the screen, the trash, etc. All of these remain fully functional
with the wxt window on the screen. You just can't select the wxt window and
do anything with it (or drag it).

> But dragging the window around the screen does not require the
> window to have focus; it is handled by the window manager / desktop,
> not by the program controlling the window.
> 
> Can you use 'top' or 'ps' to see if the process controlling the
> wxt window is burning CPU cycles?  Note that if it's a thread,
> you may have to give extra options on the command line:
> ps auxm

When you look at gnuplot while executing a script with top in another shell,
you see a burst of gnuplot cpu usage to near 100 per cent (full use of one
processor) for a brief time on my 2 cpu machine, then cpu usage falls to 0.2
per cent, and remains there while the wxt window is open. There is no big,
churning 100 per cent process when gnuplot is just paused for display. While
I was composing this, gnuplot continued to use 0.2 per cent of the cpu, and
accumulated a few seconds of cpu time over several minutes of real time.

When you enter ps auxm in another terminal shell while a wxt window is open,
you see what I captured in the attached text file. To my untrained eye, it
doesn't look like anything is wasting a large percentage of cpu cycles there
either.

In the past, I have also looked at the crash logs, and didn't see clues
there either.

I hope this helps, but I don't think so. My totally uneducated guess would
be that something is wrong with the initial wxwidget calls that set up the
wxt window with the Mac Finder. It's strange that everything else seems to
be working, including pm3d.

Joe