Re: [9fans] MacOS X drawterm doesn't toggle
On 12/11/08, Roman Zhukov [EMAIL PROTECTED] wrote: I run 9vx on Ubuntu too (8.04, i386). I've noticed that 9vx crashes sometimes when 8l is running. Same when abaco is running. And it is crashed always by nupas/fs. I'll try to give more information later. On Thu, Dec 11, 2008 at 10:22 AM, Russ Cox [EMAIL PROTECTED] wrote: Not sure where to raise 9vx queries, but almost every time I run 9vx it crashes out quite quickly and dumps core (or would if I hadn't set ulimit 0). This is on ubuntu 32 bit systems. [EMAIL PROTECTED]:~/pkg/9vx$ 9vx panic: sigsegv on cpu4 aborting, to dump core. Can you give more information? How far does it get before it crashes? If you did let it dump core, what would the stack trace look like? Russ This is under linux and I am not sure if this is of any help, but I see a lot of page faults if you ran stats. Even just moving the mouse, stats shows a high degree of page faults/sec. fernan
Re: [9fans] MacOS X drawterm doesn't toggle
2008/12/10 matt [EMAIL PROTECTED]: I thought we were suppsoed to use Inferno instead of drawterm uriel ? I can't install 9vx because my glibc is too low a version number but drawterm works just fine . also a win 2.7Mdrawterm-linux Not sure where to raise 9vx queries, but almost every time I run 9vx it crashes out quite quickly and dumps core (or would if I hadn't set ulimit 0). This is on ubuntu 32 bit systems. [EMAIL PROTECTED]:~/pkg/9vx$ 9vx panic: sigsegv on cpu4 aborting, to dump core. Why not forget drawterm and use 9vx or inferno instead of wasting more efforts on a dead end project? uriel
Re: [9fans] MacOS X drawterm doesn't toggle
Not sure where to raise 9vx queries, but almost every time I run 9vx it crashes out quite quickly and dumps core (or would if I hadn't set ulimit 0). This is on ubuntu 32 bit systems. [EMAIL PROTECTED]:~/pkg/9vx$ 9vx panic: sigsegv on cpu4 aborting, to dump core. Can you give more information? How far does it get before it crashes? If you did let it dump core, what would the stack trace look like? Russ
Re: [9fans] MacOS X drawterm doesn't toggle
I run 9vx on Ubuntu too (8.04, i386). I've noticed that 9vx crashes sometimes when 8l is running. Same when abaco is running. And it is crashed always by nupas/fs. I'll try to give more information later. On Thu, Dec 11, 2008 at 10:22 AM, Russ Cox [EMAIL PROTECTED] wrote: Not sure where to raise 9vx queries, but almost every time I run 9vx it crashes out quite quickly and dumps core (or would if I hadn't set ulimit 0). This is on ubuntu 32 bit systems. [EMAIL PROTECTED]:~/pkg/9vx$ 9vx panic: sigsegv on cpu4 aborting, to dump core. Can you give more information? How far does it get before it crashes? If you did let it dump core, what would the stack trace look like? Russ -- Roma
Re: [9fans] MacOS X drawterm doesn't toggle
On Fri, Oct 17, 2008 at 11:15 PM, andrey mirtchovski [EMAIL PROTECTED] wrote: i've attached the screen.c to put in gui-osx. give it a try. other changes with the current version in cvs (except the bugfixes) are only cosmetic. I notice your version has no ApplicationQuitEventHandler. Does this need to be merged in from the cvs version as well? Ian
Re: [9fans] MacOS X drawterm doesn't toggle
On Tue, Dec 9, 2008 at 2:12 PM, andrey mirtchovski [EMAIL PROTECTED] wrote: i suggest you use cvs since that's where all the changes go to. I'd like to do that but in the CVS version command-f no longer toggles the screen size. And my patch to remove the ctrl-opt _is_ in the CVS, which was after your fullscreen toggle patch. Ian
Re: [9fans] MacOS X drawterm doesn't toggle
On Tue, Dec 9, 2008 at 2:37 PM, Michaelian Ennis [EMAIL PROTECTED] wrote: Attached is my merge of the two versions. Yes I am a monkey. No I don't know what I am doing. Now that said, can you point me to why the application exits when I try to toggle full screen with command-F? Ian screen.c Description: Binary data
Re: [9fans] MacOS X drawterm doesn't toggle
Attached is my merge of the two versions. Yes I am a monkey. No I don't know what I am doing. Now that said, can you point me to why the application exits when I try to toggle full screen with command-F? Ian
Re: [9fans] MacOS X drawterm doesn't toggle
i'll send you the latest i have in private.
Re: [9fans] MacOS X drawterm doesn't toggle
Why not forget drawterm and use 9vx or inferno instead of wasting more efforts on a dead end project? uriel On Tue, Dec 9, 2008 at 8:38 PM, Michaelian Ennis [EMAIL PROTECTED] wrote: On Tue, Dec 9, 2008 at 2:37 PM, Michaelian Ennis [EMAIL PROTECTED] wrote: Attached is my merge of the two versions. Yes I am a monkey. No I don't know what I am doing. Now that said, can you point me to why the application exits when I try to toggle full screen with command-F? Ian
Re: [9fans] MacOS X drawterm doesn't toggle
Uriel, IMO drawterm is very good tool. I use it in my computer and in others, installation is not needed, not admin privilegies, ... Saludos. Uriel escribió: Why not forget drawterm and use 9vx or inferno instead of wasting more efforts on a dead end project? uriel On Tue, Dec 9, 2008 at 8:38 PM, Michaelian Ennis [EMAIL PROTECTED] wrote: On Tue, Dec 9, 2008 at 2:37 PM, Michaelian Ennis [EMAIL PROTECTED] wrote: Attached is my merge of the two versions. Yes I am a monkey. No I don't know what I am doing. Now that said, can you point me to why the application exits when I try to toggle full screen with command-F? Ian
Re: [9fans] MacOS X drawterm doesn't toggle
On Tue Dec 9 14:51:52 EST 2008, [EMAIL PROTECTED] wrote: Why not forget drawterm and use 9vx or inferno instead of wasting more efforts on a dead end project? uriel why not forget life on earth and go straight to our heavenly reward instead of wasting more efforts on a dead end project? - erik
Re: [9fans] MacOS X drawterm doesn't toggle
I thought we were suppsoed to use Inferno instead of drawterm uriel ? I can't install 9vx because my glibc is too low a version number but drawterm works just fine . also a win 2.7Mdrawterm-linux Why not forget drawterm and use 9vx or inferno instead of wasting more efforts on a dead end project? uriel
Re: [9fans] MacOS X drawterm doesn't toggle
this http://9fans.net/archive/2007/01/301 ? Russ fixed it and I believe I helped with the testing and contributed a small change to allow UTF characters to be pasted correctly. On Sat, Oct 18, 2008 at 2:48 AM, Steve Simon [EMAIL PROTECTED] wrote: Did you (or anyone else) find the bug in osd drawterm where the cut and paste buffer is not properly terminated so earlier long cuts appear at the end of new shorter ones. I haven't explained this very well but if you have seen it I am sure you will know what I mean. -Steve
[9fans] MacOS X drawterm doesn't toggle
Should I just be using p9p drawterm?
In the drawterm from cvs.pdos.csail.mit.edu:/cvs co drawterm
Command-F doesn't toggle from fullscreen to windowed mode. I pulled
the latest from cvs and poked around at it for a little while but I
can't figure out what the problem is. I tried to alter the switch
command on theHICommand.commandID to include this:
case kFullScreenCmd:
if (!amFullScreen)
full_screen();
else
leave_full_screen();
break;
that didn't help. In addition this particular case looked like
left-over code to me,
switch(kind) {
case kEventRawKeyModifiersChanged:
if (macKeyModifiers == (controlKey | optionKey))
leave_full_screen();
and Ctl-Opt does appears to work.
Ian
Re: [9fans] MacOS X drawterm doesn't toggle
funny, looking in the archive it was exactly a year ago that i sent a
patch to fix this. the patch doesn't seem to have been applied. it
does two things: does ctrl+F for both full screen and full-screen-less
and fixes a bug when if one is using two unequal displays (larger
secondary) then drawterm won't be able to resize properly on the
bigger screen.
i've attached the screen.c to put in gui-osx. give it a try. other
changes with the current version in cvs (except the bugfixes) are only
cosmetic.
andrey
On Fri, Oct 17, 2008 at 9:47 PM, Michaelian Ennis
[EMAIL PROTECTED] wrote:
Should I just be using p9p drawterm?
In the drawterm from cvs.pdos.csail.mit.edu:/cvs co drawterm
Command-F doesn't toggle from fullscreen to windowed mode. I pulled
the latest from cvs and poked around at it for a little while but I
can't figure out what the problem is. I tried to alter the switch
command on theHICommand.commandID to include this:
case kFullScreenCmd:
if (!amFullScreen)
full_screen();
else
leave_full_screen();
break;
that didn't help. In addition this particular case looked like
left-over code to me,
switch(kind) {
case kEventRawKeyModifiersChanged:
if (macKeyModifiers == (controlKey | optionKey))
leave_full_screen();
and Ctl-Opt does appears to work.
Ian
// in this file, _Rect is os x Rect,
// _Point is os x Point
#undef Point
#define Point _Point
#undef Rect
#define Rect _Rect
#include Carbon/Carbon.h
#include QuickTime/QuickTime.h // for full screen
#undef Rect
#undef Point
#undef nil
#include u.h
#include lib.h
#include kern/dat.h
#include kern/fns.h
#include error.h
#include user.h
#include draw.h
#include memdraw.h
#include screen.h
#include keyboard.h
#include keycodes.h
#define rWindowResource 128
#define topLeft(r) (((Point *) (r))[0])
#define botRight(r) (((Point *) (r))[1])
extern int mousequeue;
static int depth;
Boolean gDone;
RgnHandle gCursorRegionHdl;
Memimage*gscreen;
Screeninfo screen;
static int readybit;
static Rendez rend;
///
// menu
//
static MenuRef windMenu;
static MenuRef viewMenu;
static Ptr fullScreenRestore;
static int amFullScreen;
static int fromMenu;
static WindowRef oldWindow = NULL;
enum {
kQuitCmd = 1,
kFullScreenCmd = 2,
};
static WindowGroupRef winGroup = NULL;
static WindowRef theWindow = NULL;
static CGContextRef context;
static CGDataProviderRef dataProviderRef;
static CGImageRef fullScreenImage;
static CGRect devRect;
static CGRect bounds;
static PasteboardRef appleclip;
static _Rect winRect;
Boolean altPressed = false;
Boolean button2 = false;
Boolean button3 = false;
static OSStatus MainWindowEventHandler(EventHandlerCallRef nextHandler,
EventRef event, void *userData);
static OSStatus MainWindowCommandHandler(EventHandlerCallRef nextHandler,
EventRef event, void *userData);
void winproc(void *a);
static int
isready(void*a)
{
return readybit;
}
CGContextRef QuartzContext;
/* figure out which display is the largest and return its bounds so we can
* preallocate drawterm's screen to that
*/
Point
get_largest_screen()
{
CGDirectDisplayID *displaylist;
CGDisplayCount displaycount;
OSErr err;
int i;
Point max = Pt(0, 0);
Point curr;
err = CGGetActiveDisplayList(0, NULL, displaycount);
if(err != noErr)
sysfatal(can not enumerate active displays);
displaylist = (CGDirectDisplayID *)malloc(displaycount *
sizeof(CGDirectDisplayID));
if(displaylist == NULL)
sysfatal(can not allocate memory for display list);
err = CGGetActiveDisplayList(displaycount, displaylist, displaycount);
if(err != noErr)
sysfatal(can not obtain active display list);
for(i = 0; i displaycount; i++) {
curr.x = CGDisplayPixelsWide(displaylist[i]);
curr.y = CGDisplayPixelsHigh(displaylist[i]);
if(max.x curr.x)
max.x = curr.x;
if(max.y curr.y)
max.y = curr.y;
}
free(displaylist);
return max;
}
void
screeninit(void)
{
Point max; /* the largest screen, if we have multiple */
int fmt;
ProcessSerialNumber psn = { 0, kCurrentProcess };
TransformProcessType(psn, kProcessTransformToForegroundApplication);
SetFrontProcess(psn);
memimageinit();
depth = 32; // That's all this code deals with for now
screen.depth = 32;
fmt = XBGR32; //XRGB32;
max = get_largest_screen();
devRect = CGDisplayBounds(CGMainDisplayID());
gscreen = allocmemimage(Rect(0, 0, max.x, max.y), fmt);
dataProviderRef = CGDataProviderCreateWithData(0,
