ma-laforge
ma-laforge
Hi @timholy **GtkUtilities** Yes... I noticed that just recently (after I made my own rubber-band/box zoom using right-mouse-button drag). I have not yet implemented a "minpixels" on my box zoom......
> there are really two issues: one is precompiling for specific types, and the other is caching the lowered code. For the latter, I can't think of a reason why...
Thanks for the crash course. I will try to comment now. > If you have neither [`precompile` statements or `__init__` function], then basically the cached module will not contain any...
> Right. It won't generate native code unless you make it. [...] Excellent. Thanks for showing me this. I wonder: why _doesn't_ Julia automatically precompile functions with concrete signatures? Is...
When I first developped InspectDR, I might have been unaware that GLVisualize existed (but I believe I was unable to get it running at that time). Here are the differences...
Unfortunately, this error is due to the fact that InspectDR is still evolving - and I don't really have a perfect solution to match revisions of InspectDR with those of...
That's very odd... Is it possible the `Pkg.Pin` operation did not work correctly? Would you mind checking which versions you are using: ``` julia> Pkg.installed("InspectDR") v"0.2.0" julia> Pkg.installed("Plots") v"0.12.0" ```...
I have just confirmed that the (Plots v0.12.0, InspectDR v0.2.0) combination works well using the actual Julia v0.6 release in Windows 7 (Also works in Linux). If this is still...
Not certain what you mean in this last question. What I was suggesting above was to confirm if the InspectDR/Plots installations **truly** were at the desired versions by running `Pkg.installed`...
Great it works! I think I know why you were confused: There are 2 known configurations that work: (Plots, InspectDR) = (v"0.12.0", v"0.2.0") or (master, v"0.2.2") Note that to get...