evezor / edgeide Goto Github PK

each board gets a color. the lines coming out from a board get the board's color.

this would help with lines overlapping. If only 1 red goes in and out of a overlap, it is clear what the red line does.

Maps should have inputs and outputs labeled as they're shown in the IDE. Inputs on the left and outputs on the right, this is how the flow of information goes. I understand that buttons are input devices, but buttons "output" messages.

if input and output are not viable then broadcast/ subscribe, or sender/ receiver, or just about anything else imaginable would be better than this nonsense

mix.py can "mix" the inputs and outputs to show them as they're generated in the drivers.

Tested with ! (exclamation point) If included in the name field the parameter table will crash next time the user attempts to open it. Need to figure out which characters can cause this crash and either filter to prevent them being entered or fix the code so it won't crash on these characters. (has to do with div id being based on the name)

Per our last meeting we've established the need to set boolean values.

Can we get these into the relay board.

1 called something like invert logic for each of the buttons
and 2 for the relays, one called initial value and one called invert logic

It has come to my attention that it will probably be a good thing to be able to invert the logic of an (output (like an led)) The pin that turns on and off the stepper motor driver is inverted. If we wanted to have a button control the motor turning on we'd want to have the button drive the input LOW and on startup we want this pin to be put HIGH as soon as it's initialized

lots of parameters, not enough space = save button is outside the window.

Add the ability to change the name of a function or parameter.
ie. change button_0 to Forward and button_1 to Reverse if those are the desired end result of the programming

Also is this how you'd like me to add feature requests?

Duplicating board names leads to corrupted parameter tables. This occurs even if the names of one of the boards has since been changed or if the old board was deleted.

Pan with mousewheel click would be awesome too!

drag 2 B3 boards out.
open parameter box on first, set name to A, (don't save)
open parameter box on second, the first one closes, and A is not saved.

also, this dose not seem consistent - if I drag a 3d B3 out, while a parameter box is open, I can open the 3rd boards parameter box and have 2, which seem to function correctly.

having 2 boards named "A" is no good.

When a board is dragged onto the work area, set it's name to model name _ index like "b3_1" and when someone changes it, don't let them change it to something that already exits.

It would be handy if the map file had the guid in it. right now that is stored in some little commission.json, and it is tedious work trying to get it right.

idea: option to read in board model/name/guid

basically read in my commission.json file (I would need to add model name)

Right now I have to set the board name to match what is in commission.json and it isn't obvious at all what board is what line, guid, name, anything.

Even if this doesn't make sense for real world usage, it will make testing easier. We don't need to test what happens when someone doesn't get these things right: it doesn't work.

Add a toggle to change between the right angle line connections a la Kicad to the spline type connections

If I'm remembering correctly Joe, you're generating the 'parameter table' from scratch. In the previous issue I posted about the need for a checkbox.
Some other elements would likely be useful in the future such as dropdown boxes and radio buttons.
Would you create some examples that have these (the linear stepper could use an element like this to switch between in and mm)

At the base level I want to satisfy all members of the team that these are viable options to choose from when constructing modes of functionality.

One board should be able to connect its input to it's output.

drag 2 b3 boards A and B, connect button0 to led0, button1 to led1 - move B down.

The 2 lines overlap and it isn't clear what is connected to what.

If you drag a group too fast, the connection vertexes lose track of where they are supposed to be and the shape gets messed up. Sometimes it fixes itself on next drag, but not if you really mess it up.

Local file system development view won't display correctly because of CORS. Need to either disable for browser, or add documentation about spinning up webserver (locally) so that it intuitively works from the beginning.

https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSRequestNotHttp

https://medium.com/swlh/avoiding-cors-errors-on-localhost-in-2020-5a656ed8cefa

grab and move a line elbow
open and close the secret squirrel menu

the line moves to somewhere else.
default path I am guessing.

Carl has the relay board, the 16*2 LCD board, the mosfet board, the 7 segment display board, the stack light board, and the potentiometer board.
Let's start working with proper manifests

The double click action to open the parameter table only works when you click on the label. Need to make it tolerant of clicking anywhere on the parent shape as well.