> This is a feature I begged various developers to implement for more than
3 years now, but so far no luck.
If you want it that badly, helping the dev team understand the implications
(code-wise) to implement will help.
This may sound like a daunting task, but it is more like a research paper.
Making a discovery can be done by good research, and often happens without
being the resident expert on the subject.
I say this with equal high hopes as I did similar lobbying to get an Apple
build of the software, and 3 months later, we had one. I didn't do a whole
bunch of technical work, but rather spend time contacting those who were
familiar on certain topics, and a lot of scouring the internet. What I had
noticed was most of the Apple issues had been fixed downstream by a team of
MacPort developers and never made it upstream into our code. I learned how
to commit these and before long, the team had a limited Apple version.
There are many similar success stories like this and I want you to know,
this can be possible, bit we really do need the help. No one is trying to
pass the buck here, we really need ordinary yet ambitious people to help us
fix stuff, no matter how trivial of a fix it may seem. :)
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
