mtx_man wrote:Other important things are control interdependancy handling, i.e. "master feature bits", thinking out-loud that would be items like different types of warmup mgmt, water injection, traction control, nitrous mgmt, etc). i.e. if bit X is set, then these controls in this symbolic group name need to be en/disabled. Also should be able to handle compound cases (multiple bit combinations). In MegaTunix I do this by assigning user manipulatable controls (referring to ecu memory locations) to symbolic groups as needed, and enable and disable them as needed, it works, but the implementation could be improved.
Currently there is no requirement for this, however, there possibly will be, in some ways. I'd prefer something like "has valid pin or hw interface assigned" if yes, use/configure/run, if no, dont. I'm unsure how that might work. What is true, though, is that that stuff is a function of the data itself as the FreeEMS firmware will need to know that too. I'll keep it in mind. Thanks.
I'd also suggest "help information" the gui will use this for tooltips (context sensitive help). This is end-user facing information and should be worded appropriately with that in mind.
That's what I meant by description/comments. If we can use the same thing in the gui and the code comment, great, it might want a seperate field, though.
Fred, you also forgot offset within that locationID
No I didn't! :-)
What I said was that I expect you to know that one plum, two apples and one watermelon take up (1 + 4 + 4 + 30) = 39 units of size. If each field has an offset, it's asking to break all the time when editing. Lets make it dynamic on parse.
Code: Select all
{
char flags = 45;
short length = 339;
long[4] times = {893, 324, 23, 982};
}
If that psuedo code was represented in XML then as you parsed it you could tally up the byte count. This is MUCH better than explicitly stating offsets. If we do the other, if you edit a field at the beginning of the block, you need to adjust them ALL, which is totally unacceptable and annoying. I've heard you complain about that in ms land with james/ken editting stuff. Lets fix the process as I'll probably edit stuff too.
a variables' "size" i.e. signed/unsigned 8/16/32/64 bit. For example in MTX, I use a textual representation, like:
_S08_,_U08_, _U16_, _S16_,, and so on and so forth.
Yes, I mentioned this too, we could do it that way, maybe, or some other, it's an item that needs discussing.
Fred.