Replies: 3 comments 1 reply
-
My vote would be to discontinue support for the legacy HNN GUI, since it would probably require much more than just a few quick fixes. |
Beta Was this translation helpful? Give feedback.
0 replies
-
+1 … is there a reason you’re trying to get the old GUI working?
On Mon 23 Jan 2023 at 16:54, Ryan Thorpe ***@***.***> wrote:
My vote would be to discontinue support for the legacy HNN GUI, since it
would probably require much more than just a few quick fixes.
—
Reply to this email directly, view it on GitHub
<#593 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADY6FIQWNHUXESQOYV5HRIDWT342NANCNFSM6AAAAAAUEH52GQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: <jonescompneurolab/hnn-core/repo-discussions/593/comments/4761062@
github.com>
--
Sent from my iPhone
|
Beta Was this translation helpful? Give feedback.
1 reply
-
your GUI should be the new GUI with no version ambiguities :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It seems hnn (old gui) only works with hnn-core v0.1 as in v0.2 some attributes changed, e.g., from
net.params
tonet._params
. Should we add some quick fix to the old repo or change the instruction there?Beta Was this translation helpful? Give feedback.
All reactions