Hi

if you open the project XXX_driver.c file in a text editor, you will see all the information about every screen and every button/label/etc/etc on those screens. With this information it is quite possible to recreate the vtft file.

rus51

Hello Filip I thank you for your reply. What you say is true and I have acknowledged in my mail that the integrated VTFT (V4.6.2) does not have many of the problems of the standalone V4.6.1. I found the operation of the integrated VTFT (V4.6.2) faultless in MikroC for Arm. However, could you please ...

Hi

Further to my email above, if anyone wants to use Visual TFT to design screens for non ME compilers and/or non ME graphics libraries (including SPI connected ILI9486 and ILI9488 TFT screens) then please write me an email at auslame@outlook.com.

rus51

Hello All If I use VTFT for a MikroC for ARM project, I now always use the integrated version of VTFT. From my experience, I can say that the Visual TFT version integrated with MikroC for ARM works without problems and is very fit for purpose. However, this is not the case with the standalone versio...

Hi Mikroelektronika

Was the reason for this behavior ever explained by Mikroelektronika? I would like to know why this fault and many other VTFT faults have never been fixed.

rus51

Hi Saschech

Ja, das stimmt.

rus51

Hi I do not often use Visual TFT these days but I just went to modify a project I wrote a few years ago and I got the "TFT is not a valid integer value" fault. I also must shut the program down using the windows task manager. This is a long standing fault which has not been fixed. I notice that the ...

Hi You wrote: There must be a way to generate the VTFT code for a certain display controller and transfer it to your custom one There appears to be plenty of ILI9486 and ILI9488 SPI/8 Bit/16 Bit libraries on the internet or you can write your own. It is also fairly easy to use these libraries with M...

Hi Toley I agree with you. For many years we have heard the promises and the excuses from mE about the failings of their IDEs and compilers. With Necto, I was also ready to give them one more chance and I bought a full Necto Licence, but mE have since shown that the situation is even worse now than ...

Hi Toley Even though I have decided not to not use mE ARM compilers again, I will keep reading this forum for one reason. I hope one day to find out from MikroElektronika exactly who the compiler "developers" are. I would not be surprised to find that they live in the Ape House of the local Zoo. The...

Hi The same thing happened to me. MikroC for Arm Pro would disappear from the screen but the process would still be running and I would need to close the process with the windows task manager before I could restart it. I also have major problems with ARM AI on Necto. I have decided to give up on bot...

Hi Toley Hi nlukic I support Toley in this matter. I feel that calling a software licence 'perpetual' and then charging an annual fee for updates is deceptive behaviour to say the least. It may even be false advertising which is a criminal offence in many countries. There is a further point I wish t...

Hi Filip

Thank you.

Regards
rus51

Hi mE

Could you please provide the procedure which I must follow to obtain the Necto IDE/ARM C Compiler for an 80% discounted price.
I have read the discount offer in the forum but I can find no mention of it anywhere else.

rus51

Hi Jovana I have found a way around the problems I had with the FT800 library. First of all, the second problem I had (the inability to compile a new FT800 project) was caused by removing the FT800 V1.2.0.1 library, replacing it with the FT800 V1.0 library and then removing this and replacing it (on...