Great game, little glichy in windowed mode. can't seem to make a input go in the top or bottom of a component (for selector lines for example)
Thanks! I'll look at the crash reports you've submitted and hopefully the bug will be fixed in the next version :)
Regarding I/O pins at the top/bottom of the component. It's in my list of things to implement at some point, but it's low priority at the moment (also, I have to figure out what to do with the name of the component in this case).
Currently I/O pins appear only one the sides of the component (left pins are always inputs and right pins are always outputs). Also, their order is the order you created them in the first place. This is also in my TODO list (being able to change the order of appearance) but I haven't decided what would be the easiest and most intuitive way to implement it (e.g. separate component symbol editor/popup or select I/O index from the port's context menu?).
you mentioned you were thinking of a way to place the name of a component if the pins were out of top or to fix the order. i was thinking, what if you added a button in the component library next to delete where a new window would open and you can edit the apperence of the component (where default would be the current layout and the inside chip would be same, just placement of pins outside would change). in the window you could maybe move the name around relative to the chip, move pins around outside edge (with limits and therefore be able to place pin on top or change order) and maybe even move the vertex of the shape to resize, make a trapezoid for MUX, or even a V shape for a ALU. obv easier said then done but a editor window might help put pressure off you to make many different options and let them customize themselves. just an idea
FYI, the bug you were facing when creating a new component + package has been identified and will be fixed. Thank you again for your detailed steps to reproduce it. Apparently, I've never written the component name *before* opening the new package dialog, that's why I've missed it for so long.
In the meantime, try to create your new package before giving a name to the new component.
Awesome. Ya a easy to miss bug, tho the glitchiness I meant earlier is when in windowed mode. everything visual seems to be shifted up one unit so it's a little hard to make connections. might be the start menu bar messing with the dimentions it thinks it's is. Also what iststs you make like like a priority value for inputs or outputs in the right click menu to change the order?
I just saw the windowed mode bug you described. Again, I've never tried running in window mode with the same dimensions as the native resolution, that's why I missed it (I usually run it in window mode, one resolution lower than the desktop resolution; i.e. my desktop is set to 1680x1050 and I run DLS in a 1600x900 window most of the time). Thanks again :)
Don't know if I'll be able to fix this because both window dimensions and cursor position come from GLFW. I'll search for a fix, but I cannot promise anything yet.
Regarding I/O priority/order. That's one of my thoughts. Don't know if I manage to implement it for the upcoming version (0.13) but it'll be done at some point.
The bug related to the new component/package dialogs has been fixed in the latest version (0.13.0) I just uploaded. Unfortunately, I didn't have enough time to search for a solution to the windowed-mode issue. Hope to fix it some time soon.