leaflist | Disposable lists for your use | Frontend Framework library

Instead of creating a new JComboBox each time the ActionListener gets active (using new JComboBox(...)) you should update the existing location2/location3-instances.

For location2 you can do that by first calling location2.removeAllItems(). Afterwards you should iterate over your mdList and call location2.addItem() for each mdList-item.

The depth of gnuplot's evaluation stack is capped at at 250 to prevent run-away recursion. In order to increase that you would have to edit the source and recompile the program. If you really want to do that, the relevant definition is here:

Both the color and the shape can be encoded in arrays. The array must be as large as the largest index value you expect to have. Here I use the data you show above and two length 4 arrays that encode [circle, circle, square, square] and [yellow, green, yellow, green]

The correct interpretation is 1. The "if any" refers to key values, not YANG key statements. It is okay for a RESTCONF GET to fetch more than one instance of a list, but only in JSON encoding (well formed XML does not allow multiple root elements). This is also the only way to retrieve key-less non-configuration (state) list instances.

If only a single list entry would be allowed to be obtained via GET, its corresponding RFC section would explicitly state this with a MUST - if you take a look at the wording for DELETE in section 4.7, p3, such text exists, but there is no equivalent for GET.

It is also okay to retrieve multiple leaf-list instances. This may be the only way to retrieve some such instances, since (in YANG 1.1) duplicate values are allowed for non-configuration leaf-lists. The missing "if any" is most likely an editorial omission.

Note that the text in 3.5.3 only explains how URIs are formed, it does not say anything about how RESTCONF operations utilize those URIs.

Here's one way of doing it (hopefully I have no typos):