[plt-dev] language dialog

On Jan 29, Robby Findler wrote:
> On Fri, Jan 29, 2010 at 10:06 AM, Eli Barzilay <eli at barzilay.org> wrote:
> > On Jan 29, Robby Findler wrote:
> >> On Fri, Jan 29, 2010 at 9:51 AM, Eli Barzilay <eli at barzilay.org> wrote:
> >> > On Jan 29, Robby Findler wrote:
> >> >> On Fri, Jan 29, 2010 at 9:48 AM, Eli Barzilay <eli at barzilay.org> wrote:
> >> >> > On Jan 29, Robby Findler wrote:
> >> >> >> On Fri, Jan 29, 2010 at 9:46 AM, Eli Barzilay <eli at barzilay.org> wrote:
> >> >> >> > On Jan 29, Robby Findler wrote:
> >> >> >> >> My impression is that this is something the OS deals with
> >> >> >> >> (each in its own way), and so shouldn't be done at the
> >> >> >> >> DrScheme level.
> >> >> >> >
> >> >> >> > (That's definitely not something that I've seen other
> >> >> >> > applications do...)
> >> >> >>
> >> >> >> Right. The OS does it, not applications. This is definitely what
> >> >> >> happens on the mac; there is a whole bunch of keyboard navigation
> >> >> >> stuff that is even configurable (and not on by default).
> >> >> >
> >> >> > But I'm on X, which means that it's all mred.
> >> >>
> >> >> Well, not a project I'm really willing to take on at this point.
> >> >>
> >> >> And are we sure that something like ubuntu doesn't have support for
> >> >> this?
> >> >
> >> > I'm not sure what "this" refers to,
> >>
> >> "this" refers to keyboard shortcuts for radio buttons. The thing
> >> you're asking me to implement.
> >
> > I don't think that it's something that you need to implement since
> > it's something in mred.  Perhaps you're missing some kind of property
> > somewhere, but the functionality is in -- it does work on the radio
> > button groups on the details panel.
> 
> Oh, I see what's wrong. These are not a single radio button, but two
> separate ones. Probably something at the mred level has to be told to
> merge them for the purposes of keybindings.
> 
> > And speaking about that, it seems that all radio buttons allow no
> > selection at all, which is either a bug or something that leads to
> > bugs when code doesn't expect it.  If I click the show details and
> > then click the "print" output style, it gets unselected, and that
> > leads to an internal drscheme error.
> 
> I'm not seeing this (on the mac) but I think that this is in Matthew's
> baliwick. Perhaps posting the stacktrace would help.

I don't think that the stacktrace will help -- the error message is

  =: expects type <number> as 1st argument, given: #f; other arguments were: 3

   === context ===
  /home/scheme/plt/collects/drscheme/private/language.ss:257:29

so the offending code is:

  (not (= (send rb get-selection) 3))

which assumes that `get-selection' always returns a number.

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                    http://barzilay.org/                   Maze is Life!