Hi Vasilis,
You are welcome and I am pleased I could help on this occasion!
As you say, only the first screen works, I am aware of that and I only got that far before I realised there were problems with 'invisibility'. The Screen you see at startup looks like this (or it should do) :-
Ok, so the problem I am having is this, at startup you should see the screen shown above, touch the 'R' button, this is re-draw all objects, and you will see the whole screen visibly shimmer as it redraws....... do this several times until you know what I am talking about......... then touch the -1&2 button, which will make the '1' , '2' and '-1&2' buttons disappear........... now touch the 'R' button........ several times.............. the 'R' button turns red to indicate it realises it is active............... but the corresponding redraw does not happen.............. And actually this is also the case if the screen is originally drawn with any invisible objects present...... I have not managed to track down why yet, and that is the main reason I have not continued to format the fan, clock and cal screens yet, ediaz has already done significant work on the input screen, and I understand it fits a 400240 screen correctly, but as you will be aware not quite perfect on 320240. My priority is/has been to try to resolve this invisible problem, and so far I have drawn a blank and become a little de-motivated to be honest, but I will keep chipping away at it, unless someone figures it out before I do.
The next idea I think would be good, would be to take advantage and use CTE fonts if they are available, or normal UTFT fonts if not. The current ediaz version is now only UTFT fonts. My problem with this idea is that as yet I don't have a CTE TFT with fonts and although I am planning to get the 5" 800*480 with fonts, it is not going to be for another month or 2, which kind of restricts my abilities to experiment in that area... =(
I very much like your idea of the PYTHON display design project and drop into DUEGUI to compile, that does sound great, and I must admit, while you might not believe it, it did actually take me quite a long time to produce that first screen with nice formatting and layout, which you may or may not be aware, does not contain everything of the original DEMO_02.
I had intended to carry on and redesign the remaining screens all to nicely fit 320*240, but I then decided was perhaps more important to try to resolve identified problems as/when they are discovered, I fixed the 2 digit date problem along the way but that was easy.... Since others are now showing interest and asking about the current state of this project, I figured the more the merrier and released what I have so far, Ed, I hope you don't mind as I do appreciate you did the bulk of the work and I don't wish to tread on your toes!!
This invisibility problem has taken a huge amount of my time already, as while I was playing/designing that first screen I had almost completed it when I decided to introduce invisible buttons, and then touch stopped working, but I didn't connect no touch with invisible objects immediately, so actually that first screen is the stage I was at basically early November!! =( :0
Lastly, but perhaps most importantly? Would be to deal with the touch calibration screen, dynamically adjusted to cope with ANY display size at the library level, currently ediaz has it hardwired for 400240, I modified that and hardwired it for 320240, but this is not an ideal long term solution for what hopefully is going to be a universal library.
Regarding your weak C abilities, don't worry about it, Google knows everything!!
XD experimenting and playing is a good way to learn, start with DUEGUI its already broke, you can only make it better!!
To those of you requesting SVN, git etc, until somebody else wants to take control and move it somewhere else, this is my first stab at a repo..... Do what you like with it....
GitHub - ghlawrence2000/DUEGUI: A place for DUEGUI library 0.13 by 'cowasaki' to live This is no longer functional, I have no more interest in this project.
Happy new year,
Regards,
Graham