> By the way, you're really helpful :-)
> Thanks!
Thanks. I'm not great with C++, but I've debugged a few issues to
completion which has helped me discover quite a bit of the codebase.
These small issues I find particularly interesting because they add an
element of polish to the interface yet g
Hello,
My name is Sam, and I am interested in joining the development of LMMS. I
have been using it for a while now, and it has come far. I would like to
help push it further.
I know C++ but am still learning the Qt framework, so I may only be able to
make limited contributions now, but as I l
Yep. This is exactly the place I was looking at.
Since the instrument dialogs are fixed size (I tried them all) I think
the Maximize option in their context menu should be disabled - and the
Size option too -.
I will give Lmms a debug run with some breakpoints to be sure it is the
rigth place t
Yes, same behavior then. From what I can observe, every single QMdiArea
child dialog in the software behaves this way. The modal dialogs render
their title bar from the OS window manager and do not suffer this bug.
I'm not sure if this is the same thing we are looking at, might shed some
light:
Perhaps the way I described the problem was not this clear :-)
Yes I was speaking about the "Maximize" option in the context menu
(there is no maximize button on the window).
Do you mean the context menu icon and the Close an Minimize buttons are
working after you clicked the Maximize from the c
That is very strange. I've never encountered it before, so it may be a bug
specific to the QT version you are using (or perhaps the TDE desktop
environment).
I took a look at the instrument windows and they certainly have the option
to maximize via context-menu, but not via the window corner.
Cl
Hi Lmms crew,
I just noticed a somewhat bad behaviour of the SF2 instrument windows in
version stable-1.1.
If you click on the window menu icon and choose the "Maximize" option,
the window is simply moved to coordinates (0,0) of the Lmms workspace
(however it is not resized, which is ok)
Then,
:(
Yes it is unfinished, and so is undo. Undo isn't supported in the Song
Editor at all now! Delete selection and undo would be great, but deleting
isn't a problem. No one makes songs by deleting segments, but one can make
songs quickly by duplication!
diiz wrote
> Well, there's still some issue
On 11/21/2014 05:18 PM, Stian Jørgensrud wrote:
> Actually, if you are going to focus on LMMS 2.0 and not bother build official
> LMMS 1.2 I don't see any point in waiting with introducing the function to
> duplicate several TCO's in the Song Editor. To be honest, this is the most
> wanted feature
On 11/21/2014 03:58 PM, Stian Jørgensrud wrote:
> Yeah, I agree that it will be more autotracks, and that could be a bad thing.
> There is a solution, and that is grouped tracks, like a folder with tracks
> inside, hopefully that will be implemented together with the new autotracks.
Well probably
Actually, if you are going to focus on LMMS 2.0 and not bother build official
LMMS 1.2 I don't see any point in waiting with introducing the function to
duplicate several TCO's in the Song Editor. To be honest, this is the most
wanted feature from my side, I don't really know how I will feel if I h
On Nov 21, 2014 10:08 AM, "Jonathan Aquilina"
wrote:
>
> The first one you linked :)
So all apple bugs?
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Busines
The first one you linked :)
On Fri, Nov 21, 2014 at 3:47 PM, Tres Finocchiaro <
tres.finocchi...@gmail.com> wrote:
> > I am wondering if we shoudl use http://www.stack.nl/~dimitri/doxygen/
>> this will using doxygen coding standards will also allow us to generate
>> documentation from the code hi
On Fri, Nov 21, 2014 at 8:53 AM, musikbear wrote:
> This is not a bug, so there is no reason for a bug-thread on gitHUb.
> Thanks for your assistance.!
>
Well, just because it is a wontfix, doesn't mean it's not a bug. XP is EOL
so it's unlikely to be fixed, but the record of it happening and e
>
> > I am wondering if we shoudl use http://www.stack.nl/~dimitri/doxygen/
> this will using doxygen coding standards will also allow us to generate
> documentation from the code hitting two birds with one stone here.
Jonathan, which bug did you choose to start in on?
-Tres
- tres.finocchi...@
Yeah, I agree that it will be more autotracks, and that could be a bad thing.
There is a solution, and that is grouped tracks, like a folder with tracks
inside, hopefully that will be implemented together with the new autotracks.
Andreas Ecker-5 wrote
> Restricting an autotrack (the whole track n
@ Spekular DeRobyJ Chrissy McManus. Thanks for your tests!
I can conclude that the problem is a winXP only.
In xp the zasfx UI hangs for ~ 10 secd and then zasfx crashes lmms, -eg,
/'no longer responds'. /
And i also know the reason.
The preset uses one of the advanced sine-waves (whitch, i cant
We already do.
2014-11-21 6:40 GMT+01:00 Jonathan Aquilina :
> I am wondering if we shoudl use http://www.stack.nl/~dimitri/doxygen/
> this will using doxygen coding standards will also allow us to generate
> documentation from the code hitting two birds with one stone here.
>
> On Fri, Nov 21, 2
On 11/21/2014 12:30 PM, Andreas Ecker wrote:
> Restricting an autotrack (the whole track not the pattern) to only one
> knob would be a big showstopper for most of my LMMS projects.
>
> I am using in most of my songs a single one automation track for the
> song mixup/mastering - where I e.g. switch
On 11/21/2014 07:05 AM, Spekular R wrote:
>
> Haha. I've commented for myself when doing stuff but I was gonna
> remove it before committing anything since it's usually really basic
> stuff. Should I keep my comments around, even ones that just explain
> what really basic stuff is?
>
Yes
Restricting an autotrack (the whole track not the pattern) to only one knob
would be a big showstopper for most of my LMMS projects.
I am using in most of my songs a single one automation track for the song
mixup/mastering - where I e.g. switch on/off and fade in/out the FX
channels individually.
21 matches
Mail list logo
