ostatus | Ruby implementation of the OStatus data specification

Just putting the value in select won't make the option selected. You have to add the selected attribute in an option to make it selected.

I've simplified the function to focus on the char** parameter. As your sample function was written it assumes memory was pre-allocated, but there is no interface to indicate the size of the array used for output or the individual strings in the array. In this example, the memory is pre-allocated for a 3-element array with a maximum of 20 characters per string, but in reality the user would have to pre-allocate enough strings with enough length to hold the return values in the real-life situation.

test.cpp:

I added the following code to your snippet:

You should call

Your code would be much easier to follow with explanations on what it is trying to do. The code looks suspicious, simply because it is a scalar subquery, but there is no guarantee that it never returns more than one row (say by using LIMIT or aggregation).

But, it appears to, suggesting that there is at most one customer per order. With that assumption, you can replace the logic with some sort of JOIN without affecting the calculations:

I assume you are not familiar with asynchronous calls in node. Calls that accept a callback are usually executed asynchronously, which means that the result of the call will not be available immediately (not even after the function call ended), but as soon as the result is available, the callback will be called.

You can modify your code to accept another callback, so that your function has a chance to do something with the query results, and then notify the caller:

Add an event listener for the event modelContextChange to your table.

Fired when models or contexts are changed on this object (either by calling setModel/setBindingContext or due to propagation)

Since you've now shared your other code I think I know what you want. You have multiple modals, each with a select list and shipping_notes textbox which should be enabled when the selection is Shipped for that particular modal. I've modified your HTML to get this working.

I've updated your HTML a bit. You have multiple elements with the same ID. HTML IDs should be unique. If you want to target multiple elements it's safer to use class (or data-) attributes. I've added class="order-status" to each select and class="shipping_notes_txt" to each textbox. I've used element.querySelector() and document.querySelectorAll() to select DOM elements.

The snippet below mimics two modals. When the select is updated, it only enables/disabled the textbox within the same form element.

Passing parameters within the view to the controller function is firstly supported as of version 1.56 (maybe you are using an older one): https://sapui5.hana.ondemand.com/#/topic/53b4b5ec2c83408a8da2cb6b9154c246