Hi Guys at mE,
Here is another request/suggestion for something that can help users and save us time when working in V-TFT/V-GLCD that I hope you consider for adding (and do add
):
Since it is very important that every object used in a project that a user wants to have react to TP activity be set in V-TFT
before doing the code work in a compiler, it would be very useful if there was an easy to see indicator(S) located on the status bar
*
at the bottom of V-TFT that would indicate when an object is selected if there is an action event assigned for it or not and
selected object(s) Static state(s).
*(There is still some unused space free on it 
)
Even something simple of a graphic nature that we can glance at to rapidly check the objects on a project screen without the need to
switch the components view tab between properties and events (and then sometimes required to
*open the events to see if one is assigned), would be a huge time saver for us.
*(for some reason/conditions, sometimes an objects events actions are collapsed when there is an action routine assigned, but others are expanded to show routine assigned when changing from objects properties view tab to event view tab??)
It is not any fun to find out after loading project in the compiler that you have to go load it back in to V-TFT and assign an event routine
because the object got overlooked or missed somehow in the process of assigning event routines.
Or that the wrong type of memory was being set for use on objects and either consumed too much of one than expected or the users code causes compile errors trying to perform illegal operations on object(s) properties due to wrong settings (Static=True when False needed).
The Static property on most components is usually off screen in the component properties viewer and requires scrolling (and changing Windows mouse focus if not already there) to see its current setting.
Current design in any layout I like using in V-TFT (& possibly any layout configuration?) requires many operations to
check/set/clear some important object settings and properties because on different
tabs/screens/windows/sub menus that causes
longer/harder set ups and easy to miss doing required or wanted projects design configurations.
Visual indicators that are easy to see without requiring users to do addition mouse operations to check state and more operations again
to get V-TFT back to the state it was in previously to continue with editing will help users be more successful and quicker making applications.
I'm sure there are many hours that have been totaled up by the users doing mouse or software operations to return the software's state to a condition needed to continue work in that can be reduced if doing any unnecessary actions can be reduced also.
The larger the project and more objects used in it, the more time and mistakes this could prevent from happening.
As to how to accomplish these indicators when multiple objects are selected I think will be tricky to implement or maybe
impractical to do, but having them for a single object selection would be very helpful to us.
+ Until the issues have been resolved, the less often a project has to be reloaded into V-TFT the better things go with building one.
Too easy to forget getting correctly prepared to preserve any Users code that V-TFT will overwrite when project gets rebuilt.
***Would like to also re-suggest that all V-TFT generated common HW configuration code routines be removed from the driver file and placed in its own project module file please, please, please.
(A file that has to have its entire code changed/rewritten with ANY and EVERY EDIT DONE in V-TFT but also contains CRITICAL code that should never be changed, unless the User requires it edited, was/is a bad concept/practice by any standard sorry to say
and a very serious issue every V-TFT customer is waiting on to be resolved in some manner still)
The current project output file organization if left as is, can not accommodate many design implementations that a V-TFT
User can easily and safely find a way to implement the required code due to the file restrictions and limits and no way to have
V-TFT incorporated with options to accommodate the vast possible HW and device(s) configurations you have made possible with HW available.
(it will only get worse if not resolved and even more HW is added to the possible mix)
For your considerations and review, and hope you find helpful as always, Robert.
