QuoteAny updates on getting it to run on macOS?Unfortunately no. If anything will happen it'll most likely be captured there https://github.com/horizon-eda/horizon/issues/271#
Long story short: I don't have a mac os machine at hand and don't have any personal interest in getting it to run on mac os.
I have tried it as well for a couple of days and i would like to give my two cents as well.
Unfortunately, I am a little bit worried to actually share my thoughts, since most of the time feedback and criticism seems to be totally burned down.
But I am just not seeing it with this one, I am very sorry.
A lot of work needs to be done to the user interface ans user experience.
It's very unclear what exactly is going on, what is happening and how and what to do, where to find things.
Yes, those things can be found in manuals and such, but these things just need to be intuitive, without the user spending so much extra time to search and read.
In other words, the interface is just way to different that what is usual as well as very inconsistent.
If that i your goal and taste, it's fine I guess.
I just don't really see a lot of people enjoying it this way.
Just giving my professional thoughts about it, nothing more.
I have tried it as well for a couple of days and i would like to give my two cents as well.
Unfortunately, I am a little bit worried to actually share my thoughts, since most of the time feedback and criticism seems to be totally burned down.
But I am just not seeing it with this one, I am very sorry.
A lot of work needs to be done to the user interface ans user experience.
It's very unclear what exactly is going on, what is happening and how and what to do, where to find things.
Yes, those things can be found in manuals and such, but these things just need to be intuitive, without the user spending so much extra time to search and read.
In other words, the interface is just way to different that what is usual as well as very inconsistent.
If that i your goal and taste, it's fine I guess.
I just don't really see a lot of people enjoying it this way.
Just giving my professional thoughts about it, nothing more.
Can you be more specific? Feedback like this isn't really actionable and doesn't do any good. Anyhow, I've heard exactly the opposite from some people.
I quickly tried the symbol editor and had this question: What is the box shown (I marked it with a blue line) for, it moves into this position when I add pins, and how do I move it out of the way, because it is intersecting with the symbol outline. I couldn't find a menu item (in the spacebar menu) that seemed relevant to it. Closing and reopening the symbol didn't change it, and clicking on the line doesn't select it either.
Ok, adding shortcuts doesn't hurt that much. Should they zoom in/out relative to the screen center or where the cursor is?
Install Altium, diptrace, Proteus, Ultiboard or even ave a look at EasyEDA, hack even the old PADS and have a look how the user interface is and works.
QuoteI quickly tried the symbol editor and had this question: What is the box shown (I marked it with a blue line) for, it moves into this position when I add pins, and how do I move it out of the way, because it is intersecting with the symbol outline. I couldn't find a menu item (in the spacebar menu) that seemed relevant to it. Closing and reopening the symbol didn't change it, and clicking on the line doesn't select it either.
The box indicates the pin bounding box to aid consistent pin placement. All pins should be on this line, the pins at the bottom aren't.QuoteOk, adding shortcuts doesn't hurt that much. Should they zoom in/out relative to the screen center or where the cursor is?
Done: https://github.com/horizon-eda/horizon/issues/479#issuecomment-675710884QuoteInstall Altium, diptrace, Proteus, Ultiboard or even ave a look at EasyEDA, hack even the old PADS and have a look how the user interface is and works.
I guess that you're missing the Windows 95-style File/Edit menu bar. The omission of such menu bar is deliberate and is here to stay. Instead, we have
- Spacebar menu that's searchable (has everything)
- Action buttons on the left
- Hamburger menu at at the top left
There have been some ideas on making the spacebar menu more obvious: https://github.com/horizon-eda/horizon/pull/396
This is probably a low priority, and difficult to solve in all circumstances maybe. A solution would really improve usability.
I don't want you to think I am nit-picking, I am just trying to speed up commonly used tasks and reduce the behaviour from getting in the way of the user enjoying your software.
. They are absent from the schematic and PCB view, but they would not take up a lot of space.
Clicking on an item should bring up the parameter window always surely.
Another issue is that the parameter window does not allow the pad size to be modified.
are long strings like "7dac098e-afb4-4074-80d2-d5a5983a45dc".
The ability to have the padstack within the same file as the package file would also help here, to save having to generate two files.
It's very irritating that the mode swaps like this. Personally I would prefer to see a configurable option to disable the existing behaviour and enable a hybrid mode which could optionally just faintly highlight components and wires as the mouse moves over it, and then clicking to select,
No, I am missing the part that the user can choice whatever he likes
But my point mostly is, that is very different from any professional EDA out there.
No, I am missing the part that the user can choice whatever he likes
But my point mostly is, that is very different from any professional EDA out there.
Yes, that's intentional. Most of the applications you mentioned have a moderately (diptrace) to really long (altium) history. It shouldn't come surprising that a project started in 2016 would make different design choices than a project started in the 90s.
Since the project is mostly a one man show, I don't have the bandwidth to support everybody's favourite UI style.
User experience,interface as well as compatibility (Mac, Windows and Linux) is key, the rest will come later (unless you heavily fail on it)
These are also things that are very well defined and actionable.
Like I said, i am just giving my very well meant feedback, based on people who have been working for years with these kind of programs.
Polishing the UI to speed it up, trying commonly-encountered devices like a mouse with scroll wheel and you'll soon find centre-clicking is not pleasant, so a keypress is helpful for such circumstances.
Is there a way to re-scan or refresh the pool database? For instance, if I create (using text editor or scripts or custom code) a new folder and new package.json file for a new package, how do I see it in the pool?
Why would one need the scrollbars though? I don't recall having used the scrollbars on any 2D graphics application.
Good luck with your project.
and adding a little bit of configurability like the zoom step size
Quote
Polishing the UI to speed it up, trying commonly-encountered devices like a mouse with scroll wheel and you'll soon find centre-clicking is not pleasant, so a keypress is helpful for such circumstances.
I am using a mouse with a scroll wheel and have no problem with the middle mouse button. If you don't like it, you can hold shift and drag with the left mouse button.
EDIT: One reason for the hover select mode is being able to hover over something and just press delete to delete it as it's possible in kicad.
EDIT2: You can try out the alternate behaviour with https://ci.appveyor.com/project/carrotIndustries/horizon/builds/34728877 once the build has finished.
panning should not need a hard centre mouse scroll wheel to be pressed, other software does this but they also provide other methods to pan.
for instance Visio will allow hover and then drag, or single click to select and then use cursor keys to move
if I double-click on text to edit it, then the mode goes into click mode
I have a question, if my circuit looks like the attachment, because I dragged R1 up, where should I click and drag to make the two connecting wires horizontal?
Finally for now, when the exit button is clicked, Horizon uses back-to-front buttons. Normally with Windows software the Save option is on the left
I would also suggest working with people who are trying to give feedback, instead of against.
build/obj/build/gen/help_texts.o
build/horizon-imp
build/horizon-eda
/usr/include/opencascade/BRepAdaptor_Surface.lxx:270: error: undefined reference to 'GeomAdaptor_Surface::IsVRational() const'
/usr/include/opencascade/BRepAdaptor_Surface.lxx:260: error: undefined reference to 'GeomAdaptor_Surface::IsURational() const'
/usr/include/opencascade/BRepAdaptor_Surface.lxx:249: error: undefined reference to 'GeomAdaptor_Surface::NbVKnots() const'
~~~~~~
build/obj/src/util/step_importer.o:step_importer.cpp:vtable for GeomAdaptor_Surface: error: undefined reference to 'GeomAdaptor_Surface::BasisCurve() const'
build/obj/src/util/step_importer.o:step_importer.cpp:vtable for GeomAdaptor_Surface: error: undefined reference to 'GeomAdaptor_Surface::BasisSurface() const'
build/obj/src/util/step_importer.o:step_importer.cpp:vtable for GeomAdaptor_Surface: error: undefined reference to 'GeomAdaptor_Surface::OffsetValue() const'
collect2: error: ld returned 1 exit status
make: *** [Makefile:817: build/horizon-imp] Error 1
make: *** Waiting for unfinished jobs....
What is the problem here ?I hope the component creation process can be shortened for single-gate parts,
although some things still feel inconsistent or unintuitive.
I've just tried to compile Horizon EDA v.1.21 on my Slackware Linux 64-bit, but an error terminated the job:
I've just tried to compile Horizon EDA v.1.21 on my Slackware Linux 64-bit, but an error terminated the job:
Looks like your version of opencascade might be built differently than the one packaged by other distros. Try appending -lTKG3d to the LDFLAGS_OCE variable in the Makefile.
Quote1. Is there a way to route tracks at any angle, instead of 45 deg? If any angle is not possible, then 22.5 deg or 12.5 deg step modes could be useful and meet most requirements where 45 degree is not sufficient. If I had a choice this would be a high priority for me. Eventually curved tracks may also be good but this may be a major feature?
2. A button to override the rules during routing could be useful, because sometimes it is helpful to lay down tracks for layer refinement. This is useful when quickly testing to see if traces and positioning may be fine. For me this is a medium priority.There's the draw track tool, but it's fairly basic. IIRC the kicad router used in Horizon EDA supports routing arbitrary angles without DRC and disabling DRC, so it's just a matter of adding the glue logic.
I have tried it as well for a couple of days and i would like to give my two cents as well.
Unfortunately, I am a little bit worried to actually share my thoughts, since most of the time feedback and criticism seems to be totally burned down.
But I am just not seeing it with this one, I am very sorry.
A lot of work needs to be done to the user interface ans user experience.
It's very unclear what exactly is going on, what is happening and how and what to do, where to find things.
Yes, those things can be found in manuals and such, but these things just need to be intuitive, without the user spending so much extra time to search and read.
In other words, the interface is just way to different that what is usual as well as very inconsistent.
If that i your goal and taste, it's fine I guess.
I just don't really see a lot of people enjoying it this way.
Just giving my professional thoughts about it, nothing more.
Can you be more specific? Feedback like this isn't really actionable and doesn't do any good. Anyhow, I've heard exactly the opposite from some people.Be more specific?
Install Altium, diptrace, Proteus, Ultiboard or even ave a look at EasyEDA, hack even the old PADS and have a look how the user interface is and works.
My apologies, but I don't see how this is not obvious and this feedback is actually VERY actionable.