Quantcast

Fix for new layers issue

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Fix for new layers issue

Steven Yi
Hi All,

Just FYI, I'm not sure how long this has been going on--probably since
moving to the LayerGroups system--but I found an issue just now where
if a new layer was added and there were another  new layer previously
added, the new layer would not function correctly.  It had to do with
object identity and the indexOf function in the ArrayList class, which
is to say, it's sort of a surprise bug.  What could happen then is if
you say, started a new project and added two layers, trying to add a
new object to the 2nd layer wouldn't show anything but the operation
would occur.  Switching to another project then coming back to the
original would then show the object.

Suffice to say, it was an odd one I didn't know how to reproduce and
fix until now.  I have fixed in the 2.6 branch.  If I do a 2.5.11
release, I will be backporting the fix.

Thanks!
steven

------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Bluemusic-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bluemusic-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Fix for new layers issue

menno
might be the same problem as bug 83?!
but, then again, it might not :)
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Fix for new layers issue

Steven Yi
I'm not sure it is related.  However, one of the things that has taken
me so long for 2.6 is that I've had to totally rewrite all of the
actions and internal coding for object selection to handle the
heterogenous layers (i.e. copying/moving/pasting of both SoundObjects
and AudioClips).  I imagine #83 will go away once this is complete.

I'm working with the Milestone system now on Github and have added the
SF bug 83 to Milestone 2.6.0:

https://github.com/kunstmusik/blue/issues/235
https://github.com/kunstmusik/blue/issues?milestone=1&state=open

As I get closer to 2.6, I'll do some reviews of the issues and assign
to 2.6.0 so that they can be properly tested and verified before 2.6.0
goes out for final release.

Thanks!
steven

On Tue, Feb 18, 2014 at 1:30 PM, menno <[hidden email]> wrote:

> might be the same problem as bug 83?!
> but, then again, it might not :)
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Fix-for-new-layers-issue-tp5732610p5732659.html
> Sent from the Csound - Blue - User mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
> _______________________________________________
> Bluemusic-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Bluemusic-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bluemusic-users
Loading...