Connecting new music player won't allow oggs

Jeff Mitchell kde-dev at emailgoeshere.com
Tue Oct 30 00:51:34 UTC 2007


On Monday 29 October 2007, Seb Ruiz wrote:
> On 30/10/2007, Jeff Mitchell <kde-dev at emailgoeshere.com> wrote:
> > On Monday 29 October 2007, Mark Fraser wrote:
> > > Thanks Jeff, at least I now know it's not something I'm missing. In the
> > > meantime I've been doing what Greg mentioned in his post.
> >
> > Mark,
> >
> > Certainly it's something that must have worked, at least on and off, at
> > times. Such an obvious mistake surely wouldn't have gotten by the people
> > that wrote it.
> >
> > In my debugging so far, actually, I have no good solution or idea why
> > it's happening.  It is literally the following, dumbed down to
> > pseudocode:
> >
> > debug << "putting in " << item;
> > popupMenu->insertAtPos( item, 1 );
> > debug << "item at pos 1: " << popupMenu->itemAtPos( 1 );
> >
> > With the following output:
> > putting in ogg
> > item at pos 1: &ogg
> >
> > There's something really weird here, and I'm hoping it's not a regression
> > in Qt.
>
> Looks like Qt is automatically adding in shortcut accelerators.

Yeah, I thought about that too, but recreating the code in a small test 
program did not provide the same results.  The test program does not, 
however, use a .ui file, so I'll have to troll through the documentation 
and/or the generated code and see if anything looks suspicious.

--Jeff





More information about the Amarok mailing list