frauzufall on instancing-improvements-debo
Renderer: Add createRenderer me… Add SelectCommand test * the t… Add Node::outputNode() insead o… and 7 more (compare)
Domino2357 on packaging
Same as the last one- IntelliJ … (compare)
Domino2357 on packaging
Added the Mesh class to geometr… (compare)
skalarproduktraum on gradle
Bump dokka to 1.4.20 and make a… (compare)
elect86 on gradle
debug (compare)
elect86 on gradle
debug (compare)
indeed there was a significant roll in that method after I rebased it (and its branch) on the current master, but the roll was not there on the "old" master... which brings me to the question:
#279 has some conflicts when one rebases it on the master, I've resolved them locally, shall I start a new PR that would merge easily (the rebased one), or shall I just add the fixing commit to the #279 and you deal with it somehow when potentially merging it?
UIManager.setLookAndFeel( new FlatLightLaf() );
in the Main.java (the GUI look didn't change after that..)@xulman wrote:
I've resolved them locally, shall I start a new PR that would merge easily (the rebased one)
You can force-push your locally rebased branch to xulman:PR_UXchanges_takeTwo
and the PR will be updated accordingly. That’s how we do it for projects in the scijava
and imagej
orgs usually.