Now I have Mixxx showing hotcue names in main waveform. I think this
modification alone is not ready to trunk. There's some usability
inconsistencies and things to improve to deliver a better cue point
experience. I keep a list of all of them here: Cuepoins-2.0 Blueprint
<https://blueprints.launchpad.net/mixxx/+spec/cuepoins-2.0>.
Cue-points-2.0 branch
<https://github.com/ferranpujolcamins/mixxx/tree/cue-points-2.0> is my
"pull-request" candidate for all this issues, I'll merge there just when
something from the blueprint is fixed and I had tested it. I'd really
apreciate if someone could have a look at what I've done so far and give me
some picky feedback :)
Thank you all those who have helped me until now.
2015-01-16 18:52 GMT+01:00 RJ Ryan <russelljr...@gmail.com>:
>
> On Fri, Jan 16, 2015 at 6:56 AM, Ferran Pujol Camins <
> ferranpujolcam...@gmail.com> wrote:
>
>> Thank you RJ, I have a first working version, however, WaveformRenderMark
>> now inherits from QObject. Who should its parent be?
>
>
> It can have a NULL parent since renderers are created in the main thread
> (so they don't need a parent to get the thread they live in) and the
> waveform widget deletes its renderer stack.
>
>
--
Ferran Pujol Camins
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
