Re: [Tuxpaint-dev] new direct PostScript printing code
Albert Cahalan <[EMAIL PROTECTED]> wrote in news:[EMAIL PROTECTED]: > I keep an eye on the web archive, which updates quickly enough. > I also run "cvs update"... but my editor doesn't notice. > Then I save again, and the "cvs update" gets clobbered. CVS will > assume this was intentional. Then I recommend that you change your editor. Doesn't almost all editors nowadays warn you when a file has been changed from outside the editor? -- Karl Ove Hufthammer ___ Tuxpaint-dev mailing list Tuxpaint-dev@tux4kids.net http://tux4kids.net/mailman/listinfo/tuxpaint-dev
Re: [Tuxpaint-dev] new direct PostScript printing code
On Mon, 2005-01-10 at 13:24, Bill Kendrick wrote: > On Mon, Jan 10, 2005 at 09:14:11AM -0500, Albert Cahalan wrote: > > On Mon, 2005-01-10 at 02:29, Bill Kendrick wrote: > > > I'm curious, did you mean to kill my "#ifdef DEBUG_FONTS" stuff!? :^( > > > > Nope. Sorry. Was that the only thing? > > I can't recall. :^/ I THINK so, though. I just checked. The grey modification was lost as well. I was thinking of switching to a different style of disabled button. You can see it in the screenshots I posted for layout. How do you like that? The lighter grey goes well with it. > When in doubt, run "cvs update" before "cvs commit". > (And/or, if you're subscribed to tuxpaint-commits mailing list, just keep > an eye on it ;^) ) I keep an eye on the web archive, which updates quickly enough. I also run "cvs update"... but my editor doesn't notice. Then I save again, and the "cvs update" gets clobbered. CVS will assume this was intentional. > Either a runtime option, or a "built for debugging" version would be good, > at least for the next release or two, to get any kinks worked-out. > (The feature's great, but ends up relying on the quirkiness of the users' > systems more than any other feature in the past. :^) ) The info isn't just for debugging Tux Paint. It'll also help troubleshoot "why won't this neat new font load" problems. ___ Tuxpaint-dev mailing list Tuxpaint-dev@tux4kids.net http://tux4kids.net/mailman/listinfo/tuxpaint-dev
Re: [Tuxpaint-dev] new direct PostScript printing code
On Mon, Jan 10, 2005 at 09:14:11AM -0500, Albert Cahalan wrote: > On Mon, 2005-01-10 at 02:29, Bill Kendrick wrote: > > I'm curious, did you mean to kill my "#ifdef DEBUG_FONTS" stuff!? :^( > > Nope. Sorry. Was that the only thing? I can't recall. :^/ I THINK so, though. When in doubt, run "cvs update" before "cvs commit". (And/or, if you're subscribed to tuxpaint-commits mailing list, just keep an eye on it ;^) ) > I expect many of those messages to be deleted before the release. > The rest should probably be a run-time option, in case anyone > has trouble. Either a runtime option, or a "built for debugging" version would be good, at least for the next release or two, to get any kinks worked-out. (The feature's great, but ends up relying on the quirkiness of the users' systems more than any other feature in the past. :^) ) -bill! ___ Tuxpaint-dev mailing list Tuxpaint-dev@tux4kids.net http://tux4kids.net/mailman/listinfo/tuxpaint-dev
Re: [Tuxpaint-dev] new direct PostScript printing code
On Mon, 2005-01-10 at 02:29, Bill Kendrick wrote: > I'm curious, did you mean to kill my "#ifdef DEBUG_FONTS" stuff!? :^( Nope. Sorry. Was that the only thing? I expect many of those messages to be deleted before the release. The rest should probably be a run-time option, in case anyone has trouble. ___ Tuxpaint-dev mailing list Tuxpaint-dev@tux4kids.net http://tux4kids.net/mailman/listinfo/tuxpaint-dev
Re: [Tuxpaint-dev] new direct PostScript printing code
I'm curious, did you mean to kill my "#ifdef DEBUG_FONTS" stuff!? :^( -bill! ___ Tuxpaint-dev mailing list Tuxpaint-dev@tux4kids.net http://tux4kids.net/mailman/listinfo/tuxpaint-dev
