I pushed a fix into R devel.
On Wed, May 9, 2018 at 8:56 AM, Paul Shannon <
paul.thurmond.shan...@gmail.com> wrote:
> Hi Michael,
>
> Thank you for this work and the explanation. It’s good to know that my
> problem will feed back into improvements in the methods package.
>
> I opted for a simple
Hi Michael,
Thank you for this work and the explanation. It’s good to know that my problem
will feed back into improvements in the methods package.
I opted for a simpler workaround, for now, renaming my abstract class to avoid
the collision.
- Paul
> On May 8, 2018, at 8:25 AM, Michael La
Thanks Paul.
I've made improvements to the methods package so that there will no longer
be any messages about AnnotationTrack being duplicated, but I'll need to
work through some failures this is causing in tests.
The first issue is interesting though. Since Gviz defines an initialize()
for Annot
Hi Michael,
> On May 4, 2018, at 1:36 PM, Michael Lawrence
> wrote:
>
> Do you have a reproducible example of this? It's probably a bug in the
> methods package.
>
Sorry I did not get to this sooner. Here are two symptoms of the cache class
name collision:
1) igvR::displayTrack, if cal
Do you have a reproducible example of this? It's probably a bug in the
methods package.
Thanks,
Michael
On Fri, May 4, 2018 at 10:52 AM, Paul Shannon <
paul.thurmond.shan...@gmail.com> wrote:
> I just discovered a class name collision - AnnotationTrack, in Gviz and my
> new package igvR. wish
Hi Paul,
Luckily you caught this only 3 days after the release so renaming the
class now is probably ok and shouldn't be disruptive.
Cheers,
H.
On 05/04/2018 10:52 AM, Paul Shannon wrote:
I just discovered a class name collision - AnnotationTrack, in Gviz and my new
package igvR. wish to g
I just discovered a class name collision - AnnotationTrack, in Gviz and my new
package igvR. wish to get wise counsel before proceeding with a fix. Here’s
the error message:
Found more than one class "AnnotationTrack" in cache;
using the first, from namespace ‘igvR' Also defined by ‘Gv
