If statements

If statements have been implemented sufficiently to do the testing.

This also shows how I've made inputs and outputs be represented on the state or if blocks that they connect to.

Delete Marker

The above pictures demonstrate my working delete marker design. The first shows the markers linked in a random way and the second shows how once the delete marker crosses a link it removes it. I've also fixed a few other bugs over the last few days (a memory issue, the dtserver not being closed when the program stopped and a couple of others.) I've also started to formulate the vague structure of the report and am thinking about the if markers.

Further thoughts on if statements and deleting links

Here are some ideas of how to do the if statements and deleting links.

Ideas to do with the if statement and how to implement it

Ideas for how to do delete links between markers

Linking works now!!

I have got the linking working. You can now link any markers and place them wherever you like and they will be linked with a red line to demonstrate it.

How some of the markers will link together

I've scanned in some pictures I've drawn of how some of the markers will link to each other (graphing tools were difficult to get a good representation of what I wanted). 

This will mean breaking the marker types into which marker they represent. For instant marker types 1-5 could represent state markers, 6 the default marker, etc... I'll probably need to design new markers at some point (particularly in the case of the if markers) this would then make it more intuitive.

ASM detail & linking update

Quick update: In terms of linking I've got two markers linking but have a few bugs to resolve (for instance it is currently only linking one set of markers.

In terms of fleshing out the ASM charts that were posted last time. All three were taken from my logbook from last year. However only the final one (lift controller) has been taken straight and not simplified. This is because for testing purposes I want simple designs that demonstrate the capabilities not the the extras of a complicated ASM chart. The lift controller works on the basis that the lift is either at a floor or in a going up or down state. It's a simple controller so there are only 2 outputs of goUp or goDown. In the going up or going down states the correct output is emitted causing the lift to go up or down. The three ASM charts give a very simple idea of what is required to make a simple ASM chart. In the next post I will go into how I plan to design the TUI to make an ASM. 

ASM Charts

I'm still working on the linking. However I've drawn a few basic ASM charts to give an idea of the aim. They may be too large but give an idea of the different links/functions in an ASM chart

A very simple ASM chart consisting of only states (rectangles) and if blocks (diamonds)

An ASM originally based on the one above but includes conditional outputs (ovals)

A more complicated ASM chart made of states and if blocks