From: Chris C. <ca...@al...> - 2002-01-10 19:08:23
|
How do you expect a negative RealTime to be stored? Say the RealTime corresponding to 1.3 seconds before zero. At the moment this is actually being stored as -2 seconds and +700000 microseconds. Even if you explicitly construct a RealTime at -1 seconds and -300000 microseconds, it'll be "normalised" to -2 and +700000 in the constructor. Is this likely to be a problem anywhere? It's still true that seconds + microseconds = time, but perhaps it would be more intuitive to require the sign of the microseconds to match that of the seconds. Chris |
From: Chris C. <ca...@al...> - 2002-07-15 18:21:39
|
How come Rewind and Record have the same keyboard accelerator? Chris |
From: Guillaume L. <gla...@te...> - 2002-07-15 19:48:29
|
On Monday 15 July 2002 20:19, Chris Cannam wrote: > How come Rewind and Record have the same keyboard accelerator? Because they both start with the same letter 'R'. -- Guillaume. http://www.telegraph-road.org |
From: Richard B. <bo...@bo...> - 2002-07-15 19:50:42
|
> How come Rewind and Record have the same keyboard accelerator? Yeah, there's that. And also rewind's accelerator doesn't appear to work for me when I'm focussed on the main window - instead I get a blank popup menu two elements high. I've no idea what's going on there. B |
From: Richard B. <bo...@bo...> - 2002-07-15 20:16:47
|
Richard Bown wrote: > > How come Rewind and Record have the same keyboard accelerator? > > Yeah, there's that. I've changed Record to spacebar like it should be. One thing we're missing at the moment though is the punch-in record - we should be able to tap space and insert a blob of MIDI or audio whereever we like. This'll come soon. B |
From: Chris C. <ca...@al...> - 2003-01-27 12:24:41
|
Why does RosegardenComboBox emit propagate() when the mouse wheel is scrolled, rather than activate()? Some of the places where it's currently used connect the activate() signal up to something, but not many of them also connect propagate(), and I suspect they should. Chris |
From: Richard B. <bo...@bo...> - 2003-01-28 07:24:37
|
On Monday 27 January 2003 12:20, Chris Cannam wrote: > Why does RosegardenComboBox emit propagate() when the mouse wheel > is scrolled, rather than activate()? Yeah I dunno - I think early exuberance when I'd just discovered signals and wanted to make one of my very own. I wondered about this myself the other week. BTW Guillaume if you do want to fix MIDI import then be my guest. Like I said I'm not able to work on anything for the next week or so. B |
From: Chris C. <ca...@al...> - 2003-01-29 15:55:24
|
Richard Bown wrote: > On Monday 27 January 2003 12:20, Chris Cannam wrote: > >>Why does RosegardenComboBox emit propagate() when the mouse wheel >>is scrolled, rather than activate()? > > Yeah I dunno - I think early exuberance when I'd just discovered signals > and wanted to make one of my very own. I wondered about this myself > the other week. Gosh, I imagine you did. I've just bought the latest Linux User magazine, and by sheer coincidence it contains an article about Qt by one Richard Bown, and guess what? As a worked example, it uses a subclass of QComboBox that emits a signal called propagate() on mouse wheel events. Imagine my surprise etc. Chris |
From: Mark K. <mar...@at...> - 2003-01-29 20:56:06
|
Life is funny that way, isn't it! ;-) On Wed, 2003-01-29 at 07:49, Chris Cannam wrote: > Richard Bown wrote: > > On Monday 27 January 2003 12:20, Chris Cannam wrote: > > > >>Why does RosegardenComboBox emit propagate() when the mouse wheel > >>is scrolled, rather than activate()? > > > > Yeah I dunno - I think early exuberance when I'd just discovered signals > > and wanted to make one of my very own. I wondered about this myself > > the other week. > > Gosh, I imagine you did. I've just bought the latest Linux User > magazine, and by sheer coincidence it contains an article about Qt > by one Richard Bown, and guess what? As a worked example, it uses > a subclass of QComboBox that emits a signal called propagate() on > mouse wheel events. Imagine my surprise etc. > > > Chris > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Rosegarden-devel mailing list > Ros...@li... > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel |
From: Richard B. <bo...@bo...> - 2003-01-29 22:18:59
|
On Wednesday 29 January 2003 15:49, Chris Cannam wrote: > Gosh, I imagine you did. I've just bought the latest Linux User > magazine, and by sheer coincidence it contains an article about Qt > by one Richard Bown, and guess what? As a worked example, it uses > a subclass of QComboBox that emits a signal called propagate() on > mouse wheel events. Imagine my surprise etc. That would explain things a bit wouldn't it? B |
From: Guillaume L. <gla...@te...> - 2003-01-28 11:11:58
|
On Tuesday 28 January 2003 08:25, Richard Bown wrote: > > BTW Guillaume if you do want to fix MIDI import then be my guest. Like > I said I'm not able to work on anything for the next week or so. Actually I might not get a chance to do that either before feb 6th either. I first have to finish that doc properties thing, and I'm off on sunday until next thursday (with no external email access, btw). -- Guillaume http://www.telegraph-road.org |
From: Chris C. <ca...@al...> - 2003-01-28 11:29:23
|
Guillaume Laurent wrote: > On Tuesday 28 January 2003 08:25, Richard Bown wrote: > >> BTW Guillaume if you do want to fix MIDI import then be my guest. >> Like I said I'm not able to work on anything for the next week or >> so. > > Actually I might not get a chance to do that either before feb 6th > either. I first have to finish that doc properties thing, and I'm off > on sunday until next thursday (with no external email access, btw). Gosh. It's gonna be quiet around here. Well, if I happen to have some time around then, I could take a look -- don't let that dissuade either of you from cracking on with it if you get a moment though. At some point I want to take a look at the document / file-io stuff myself anyway, as I want to implement a generic way to do file merging for any of the file types already supported for import. I'm assuming that'll be somewhat easier to do with the new framework than it was with the old, though I haven't actually looked at it yet. Chris |
From: Richard B. <bo...@bo...> - 2003-01-28 20:19:46
|
On Tuesday 28 January 2003 11:26, Chris Cannam wrote: > Gosh. It's gonna be quiet around here. My brain is active but my body hurts. I see these two weeks as a physical training ground for the Big Last Push to 1.0. I see some interesting stuff but don't have time to respond of course. B |
From: Richard B. <bo...@bo...> - 2002-01-11 07:49:42
|
[negative time] > Is this likely to be a problem anywhere? It's still true > that seconds + microseconds = time, but perhaps it would be > more intuitive to require the sign of the microseconds to > match that of the seconds. If the integrity of the RealTime operators is unaffected then it shouldn't be a problem - by the time it gets to the aRTS::TimeStamp the time will be rolled out to an absolute MidiPort one anyway. R |
From: Richard B. <bo...@bo...> - 2002-01-11 10:51:05
|
I'll go quietly Sequencer bug hunting now - I've just got a favour to ask. I'm implementing sub-bar movement of Segments (moving them units smaller than a bar). This works on the GUI ok but the Segments themselves of course are fixed within the bar resolution of updateSegmentTrackAndStartIndex(). What do we do here? Given the SegmentItem's x position and the length of a bar (in the same terms) we can perhaps pass a fraction to Composition to return a absolute position pair? As with getBarRange? I'm a bit scared of getBarRange to tell the truth. R |
From: Chris C. <ca...@al...> - 2002-01-11 14:14:16
|
Richard Bown wrote: > What do we do here? Given the SegmentItem's x position and the length of > a bar (in the same terms) we can perhaps pass a fraction to Composition to > return a absolute position pair? As with getBarRange? Not completely sure what the question is. Are you saying that updateSegmentTrackAndStartIndex is getting a SegmentItem whose x-coord is intentionally not on a barline, but that it doesn't know what to do with it because it only works in whole bars? If so, the fix looks straightforward -- surely stick something like this in the body of updateSegmentTrackAndStartIndex: int barNo = m_hHeader->sectionAt(int(i->x())); int leftX = m_hHeader->sectionPos(barNo); int rightX = m_hHeader->sectionPos(barNo + 1); double distance = (i->x() - (double)leftX) / (double)(rightX - leftX); std::pair<timeT, timeT> barRange = composition.getBarRange(barNo, false); timeT myStartIndex = barRange.first + distance * (barRange.second - barRange.first); Not that I've tried it, and I guess you'd need to cope with the case where there is no section barNo + 1 in the header. And there may be rounding issues. Chris |