-
Notifications
You must be signed in to change notification settings - Fork 229
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
ebf1e5a
commit 144c99e
Showing
1 changed file
with
9 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
144c99e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what this change was supposed to do. The pull request that I provided to you worked and now I can't seem to get it to work...
Did you test this? I can't seem to get it to return the data correctly...
144c99e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, you took out a feature...
I had to change
to this
This is acceptable, but complicates the call for anyone else that might only have one type of output (most common)
144c99e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The last line should have been
to have the desired behavior, sorry.
The idea was to make it easier to expand the code for more output formats
harness.png
(line 203 and 209 in original file)lower()
function, which was not consistent.. this way, it's done once and for all :)Please try the new code (de1e45f), I've added SVG output to test the case of more than one
return_type
144c99e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, good deal. That meets the intent of what I was looking for.
Any idea when the
dev
branch will be included in themain
branch? I don't want to build too much an an immature API, but I don't want to hold you back either. Right now, I'm basically including the dev-branched copy in my code directly.144c99e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For now, I think it's best to keep using the dev branch, since the project is in an early stage, and there's no real meaning to a 'master' release yet, anyway.
I doubt the API your GUI uses will change much, but
So, thanks a lot for your effort in building a WireViz GUI, just be aware of the above points! π
144c99e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eagerly awaiting the the next release, not going to do much to build on until then...