Hi all,
I have 2 consecutive builds that failed in travis-ci in the EngineBuffer
tests. Not at the same place (stalled builds killed by travis-ci) (Pull
Request 606).
https://travis-ci.org/mixxxdj/mixxx/builds/66159337
https://travis-ci.org/mixxxdj/mixxx/builds/66339484
I can see no
Hello,
Sorry being quiet for a while because lack of time for this project.
Having SL4 for testing would be easier (I could even just lent one not
for owning). I don't know are ALSA people interested with this kind not
mission critical device. As I have make little reasearch I could be
rather
So we have people who prefer 80 columns, and people who prefer unlimited
columns. There's not really a compromise position between these two
options, so how do we choose?
We have people who prefer 80 columns and we have people who prefer more.
I prefer 80 columns.
So there is no column issue
On Thu, 2015-06-11 at 14:08 +, Gavin Swanson wrote:
Compromise = 120 Columns
No, the people who prefer 80 columns have specific reasons for that
value -- specific window sizes, compatibility with existing code, etc
etc. My point is that this is a case where there is not a compromise
and we
Compromise = 120 Columns
My main issue with 80 column split:
Modern IDEs provide some kind of Tab Completion like capability which
lessons the pain of writing out (reasonably) long descriptive variable and
function names (which everyone should be doing). When your using these
longer names you
Thanks, I figured it was Alsa, Linux or something low level. Thought I'd
ask.
-Jamie
On 06/11/2015 01:51 AM, mixxx-devel-requ...@lists.sourceforge.net wrote:
Send Mixxx-devel mailing list submissions to
mixxx-devel@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide
It would be awesome if you lent Tuuka your SL4 for driver development.
The ALSA developers apparently have no interest in working on this
driver. As far as I can tell, there is no good reason for someone
interested in DJing with Linux to purchase an SL2/3/4, so no one has
written a Linux
Tukka, if you're interested in trying to get it to work, I'm more than
happy to send it to you. Let me know your address.
-Jamie
On 06/11/2015 07:08 AM, mixxx-devel-requ...@lists.sourceforge.net wrote:
Send Mixxx-devel mailing list submissions to
mixxx-devel@lists.sourceforge.net
To
Mappings included in Mixxx have the XML file named with hyphens
separating words but the script files are named with spaces separating
words. Having two naming conventions gets confusing and annoying,
especially when typing the file names in a shell. I suggest switching
the script files to
Le 11/06/2015 21:02, Be a écrit :
Mappings included in Mixxx have the XML file named with hyphens
separating words but the script files are named with spaces separating
words. Having two naming conventions gets confusing and annoying,
especially when typing the file names in a shell. I suggest
Hello,
With Mixxx I use astyle:
astyle --style=java --pad-header -s4 --lineend=linux
--max-code-length=80 --break-after-logical --convert-tabs file.cpp
it seems that they also have Google style and pico style (what ever
that means but I'll start to use it). I prefer 120 because hey it's
2015. I
My interest is that I'm a huge fan of FOSS and would love to contribute
but don't have time or skill to contribute code. I like Rane hardware,
they are a US (my country) company (made in US too) but their stuff is
not cheap. I think I paid over $900 for the SL4 ,vinyl, and Serato
license
Hello,
I'm with auto formatting people. Before we had code auto formatting it
was mostly complaining coding style. Now like RJ said nobody can argue
because there is one to rule them all system. I also like to see
cppcheck and flawfinder style hooks to check code for dummy mistakes.
Never
So we have people who prefer 80 columns, and people who prefer unlimited
columns. There's not really a compromise position between these two
options, so how do we choose?
On Wed, 2015-06-10 at 09:28 -0400, Owen Williams wrote:
On Wed, 2015-06-10 at 09:16 -0400, RJ Ryan wrote:
The
14 matches
Mail list logo
