 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Missing functions in the MM+ GUI
| Author | Message | ||||
kiiid Guru  Joined: 11/05/2013 Location: United KingdomPosts: 671 |
I am writing something now and discovered that some important functions are currently missing in the MM+ GUI. 
The first one is to check what type of control (if any) is defined for a given reference number. For example, if I have only a single a button with ref#1, and I call the function, it should give me something like "BUTTON" for parameter 1, and "" for any other parameter. The second missing function is to find out the current status of a control (hidden, disabled). http://rittle.org -------------- |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2948 |
Which version of firmware are you using?? |
||||
| kiiid Guru Joined: 11/05/2013 Location: United KingdomPosts: 671 |
The most recent one for MM+ 4.7b37 http://rittle.org -------------- |
||||
Geoffg Guru Joined: 06/06/2011 Location: AustraliaPosts: 3303 |
Interesting point but it seems to me that you as the programmer know what type of control is related to a reference number, because you must have assigned it earlier in the program. So, why would you need a function to tell you this? I guess that you are wanting to automate something but I cannot figure out what. The same applies to the state (hidden, etc) of a control. Geoff Geoff Graham - http://geoffg.net |
||||
| kiiid Guru Joined: 11/05/2013 Location: United KingdomPosts: 671 |
My situation: I have a subroutine which conditionally creates a control on the screen. The problem is that the same control might have been created already from another point, so I need to know whether it currently exists on the screen or not. The second function is part of the same problem. Another thing is that once the program becomes long and spanning over a few screens, it becomes increasingly difficult to keep track on the ref# ids as well, so I wanted to automate their creation and destruction. Not saying that it is impossible to live without these, but I was surprised to find out the lack any feedback from the gui, except for the touch. http://rittle.org -------------- |
||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
