|
From: Guilherme B. T. <gui...@gm...> - 2020-04-10 19:29:45
|
Hello, I suggest you take a look at the "qt-19" branch I just pushed to the main repo. It received a recent merge from develop branch. I will not do big rebases, too many things diverged and I am got tired of resolving conflicts. I gutted out a bunch of the old code and relocated another bunch. A lot of work is still needed... I was hoping to clean it up further before pushing. Sorry for the mess. I have a pretty good idea on which way to go. Perhaps we can discuss coordinate the work before people start forking the qt5 code in multiple directions. Priority is finish the Qt5 port and have functionality as close as possible to the legacy application. All other improvements can wait. Including some of the refactor from " refactor+qt5" are already colliding with "qt-19". I will try to close old issue and open a new one to track this thing. Regards, Guilherme On Thu, Apr 9, 2020 at 7:39 AM Felix Salfelder <fe...@sa...> wrote: > On Thu, Apr 09, 2020 at 11:22:09AM +0100, Derek Kozel wrote: > > So your suggestion is to work off your refactor+qt5 branch as the most > > recent starting point? > > Hi Derek. > > That's one way of doing it. You may as well try from scratch, and use > refactor+qt5 as a cheat sheet. But it won't tell you how to solve the > mouseactions i'm afraid. > > > Is this the mouseactions issue you're talking about? > > https://github.com/Qucs/qucs/issues/560#issuecomment-453266519 > > Yes. If you are willing to help to some extent, I wouldn't mind a chat > as well. > > cheers > felix > > > _______________________________________________ > Qucs-devel mailing list > Quc...@li... > https://lists.sourceforge.net/lists/listinfo/qucs-devel > |