Menu
▾
▴
Re: [MACTCL] [PD] pd-gui-rewrite testing
|
From: Rich E <ric...@gm...> - 2010-01-17 18:20:09
|
On Tue, Jan 12, 2010 at 3:35 PM, Kevin Walzer <kw...@co...> wrote: > Hi, > > A lot of things in this message, I'm not sure where to begin, so I'll just > go through it item by item. > > > > > On 1/12/10 8:44 AM, Rich E wrote: > > >> On Jan 9, 2010, at 5:37 PM, Rich E wrote: >> >> >>> Still in OS X 10.6.  I don't have one of these problems with >>> >>> Pd-devel-0.43 (dec 15) nightly build, so it must all be because of >>> the tk/cocoa version that you mention.  I'm not sure how to >>> >>> report it a tcl mailing list, as I don't know where the code is >>> that implements these things.  >>> >>> >>> Does it make sense that the arrow keys are detected differently in >>> Tk/Cocoa, so they are just sent to pd's gui C code as spaces?  >>> >> > What exactly is the issue here? It's not clear from your description. It > might be best to file a bug at SF with a short script to reproduce the > issue. > I am trying to figure out what to report as a bug. It is definitely related to the Cocoa Tk included in OS X 10.6, but I could use some direction in localizing the problem. Maybe Hans can help clarify the internals of Pd, or give suggestions as to how to make an example script for submitting to the bug tracker. The text is being drawn in a Canvas, but I don't know if this matters. I do know that from the 'key' and 'keyname' objects in Pd, I get different results for the arrows: - Tk Cocoa give numbers 63232-63235 from the 'key' object, nothing from 'keyname' - Tk Carbon gives nothing from the 'key' object and the symbols "Up, Down, Left, and Right" from the "keyname" object The arrows-give-spaces problem only occurs in the canvas, from what I can tell. Moving between text letters/numbers with the arrows works in both Pd's console and dialogs. >> Not to me... it should be the same, that's why its worth reporting >> to tcl-mac.  You don't need to know the exact code that's causing >> the problem.  I read that list too, so I can fill in the details. >> >>  I just don't have access to a 10.6 machine these days. >> >> As for the text color issue in the audio settings, you'll have to >>> point me towards what is controlling that.  I'll send you a >>> screenshot after this email. >>> >> >> Check out dialog_audio.tcl.  Its still mostly the original code, so >> it can be scary. ;) >> >> Do you know how I can force configure to use Tcl/Tk 8.5.7/Carbon? >>> >> >> If you put a version of Tcl/Tk 8.5.7/Carbon frameworks into >> /Library/Frameworks, it should use them over the build in ones. >> > > Correct. Tk 8.6 from CVS is Cocoa-based, and a Cocoa backport of 8.5 is > here: > > http://github.com/das/tcltk/tree/de-carbon-8-5 > > > >>> • In Audio Settings, the text in the drop down menus is >>> >>> hardly visible because it is very light grey >>> >> > This may be because Tk-Carbon ignored custom menu settings, but Tk-Cocoa > picks it up. It may not look "right" or "native" on OS X, but might look OK > on other platforms. > > • there is a new menu item called 'apple' with "about >>> >>> pd" and preferences" >>> >>> >>> Known issue with the Tk/Cocoa, haven't found a workaround yet. >>> >> > The simplest workaround for this is to remove the Apple menu altogether and > re-implement these two procedures: > > tkAboutDialog {} { > ##put your "about dialog" stuff here > } > > > proc ::tk::mac::ShowPreferences {} { > ##put your preferences menu stuff here > } > > If you need to put anything else in the Apple menu space, you'll have to > leave the Apple menu, and call this statement after building everything > else: > > . configure -menu .mymenu > > You can't configure the main menu first anymore. > > > >>> >>> • editing an object name: >>> ‣ moving with arrows adds a space to the end, but does >>> >>> not move within the object name >>> >>> >>> Hmm, can't reproduce, Tk/Cocoa issue? >>> >> > Can't reproduce this under Tk-Cocoa either. > >> >>> >> > As I mentioned, filing bugs at SF is the best way to go. Daniel Steffen, > the Tk-Mac maintainer, doesn't do much on the mailing list anymore because > of time issues. > > --Kevin > > -- > Kevin Walzer > Code by Kevin > http://www.codebykevin.com > |