Show Posts
Pages: 1 2 [3] 4 5 ... 7
31  Products / Arduino Due / Re: Due GUI (Graphical user interface) - [now community project] on: December 31, 2013, 09:37:19 pm
So unless some with good  knoledge of C. C++ lead this project it will end up with everybody with cut and past makes his version only for himself.

No! That is absolutely not what I envisage, whoever or wherever this library is hosted is not important, who wishes to be lead contributor, and or lead coordinator is not important,  'Kernighan Ritchie' levels of understanding of C, kind of seems to imply less knowledgeable mortals have nothing to offer, which I absolutely disagree with, and finally the whole point of a community project is that ALL suggestions from ANY angle are to be accepted, appreciated, discussed and dealt with appropriately, with the result being uploaded to git? Is that not what an ideal community collaboration is all about?

@cowasaki has already handed over the reigns due to limited time, Henning I think you will find has enough on his plate with his existing projects and maintenance of his various libraries and resources. Git gives us the ability to fork, branch, and monitor any/all changes/variations/additions/deletions and produce useful documentation collaboratively! The repository is public as such is available as a 'free for all' with no control from me, I just hosted it because nobody else had......... I don't see that this has empowered me or nominated me in any way? You may have noticed that  @ediaz and myself have been in dialogue a little while now, and I think it would be more appropriate to have a staging area / brain storming arena away from this forum where trivialities and any/all comments can be made without swamping the forum with tooing and froing of questions/suggestions/test reports etc?

One of the most urgently required imminent updates to this needs to be the dynamic calibration screen, while I accept maybe I am no K&R prodige, I do consider it to be within the realms of my abilities to do this, the major limitation I have, is that I only have 1 display. I am hoping and will need, other people with different flavours of shield and or display to verify the modifications when I have made them, which actually brings this full circle, @ediaz gave me his code to test on my display. He and I already agree something needs to be done about this, and here we are, this is the point you have joined in. Come the time I have dealt with the invisible object problem, and the touch calibration screen, I will be looking for as many as possible different people to test this, not only myself and @ediaz, thus ensuring the ultimate flexibility of the DUEGUI library.

What individuals then chose to do with that library of course will very much be on a 'each to themselves' arrangement. My demo was made by me, for me, on my own display, as a start point to then get down to doing some remedial work on the library itself. The sketch I gave was a work in progress, and in hindsight, maybe I should not have given it you if you are not intending to bring anything back?  smiley-mad smiley-sad

Regards and a VERY Happy New Year everyone!!  smiley-grin

32  Products / Arduino Due / Re: Due GUI (Graphical user interface) - [now community project] on: December 31, 2013, 11:01:45 am
Hi Vasilis,

You are welcome and I am pleased I could help on this occasion! smiley-grin 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 400*240 screen correctly, but as you will be aware not quite perfect on 320*240. 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...  smiley-cry

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!!  smiley-cry smiley-mad

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 400*240, I modified that and hardwired it for 320*240, 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!!  smiley-mr-green smiley-lol 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....   This is no longer functional, I have no more interest in this project.

Happy new year,


33  Products / Arduino Due / Re: Due GUI (Graphical user interface) - [now community project] on: December 30, 2013, 04:48:40 pm

"DueGUI_demo_02.ino: In function 'void setup()':
DueGUI_demo_02:382: error: conversion from 'int' to 'String' is ambiguous
C:\Program Files\Arduino\hardware\arduino\sam\cores\arduino/WString.h:61: note: candidates are: String::String(const __FlashStringHelper*)
C:\Program Files\Arduino\hardware\arduino\sam\cores\arduino/WString.h:59: note:                 String::String(const char*)

So please where is the final code so far? can it run in 1.5.5? I want to help in any way
I know is Christmas but this project is joy or not?
Happy new year to everybody

Vasilis, Hi  smiley

Yes more people joining in with this would be good, I must admit I have had a few weeks of other stuff to do, but the immediate 'cure' for that particular error is

//  (c) 2013 Darren Hill (Cowasaki)
#define VERSION "0.13"  <--------------------  NOTE quotes!
//  This program is not as yet complete.  There are a number of missing features and features not fully implemented.

I cannot as yet comment on suitability of IDE 1.5.5 as I am still on the previous release.
While I was busy creating the zip and making sure it worked, I got 1.5.5. and can confirm that it works fine  smiley-grin. FWIW, this is the current library, complete with working example for a SSD1289 based 320*240 display and CTE shield.

There is much more to be done with this as only the main screen is correctly formatted as yet, there are problems with invisibility which is as far as I got, since my touch screen is also not working correctly, and I got bogged down with a few other things too, but HOPEFULLY, this should give something at least visible and working on screen.

@marbeuhan08, I have not got as far as trying to play with image buttons yet, maybe ediaz could comment further, as far as I am aware he was looking into image storage in flash, but my own thoughts are SD (since I already modified UTFT_tinyFAT to retrieve images using sdfatlib)...... More input/discussion is needed on several aspects of this project, but sadly to date, all modifications from cowasaki's original library are entirely the work of ediaz, I can not take any credit for the work done so far.

@fadik, ediaz is currently the leading light on this project, although I am dabbling in a few areas myself at the moment, it would be great to have more eyes on this project, github is another possibility for collaboration, I don't know if Ed has any thoughts?

@ed the only differences between (ediaz) and (ghl-tweaked) versions, is that I added back in all the spaces you removed so I could do line by line side by side comparison to original cowasaki version, and also slight change to 'posCentre' parameter, and also 2digit date format.

The included archive as it stands, and the ghl_DueGUI_CTEshield_320x240_SSD1289 example is formatted nicely. The ediaz version of the library will rapidly show the differences  smiley-wink

HAPPY NEW YEAR everyone !!!  smiley-grin


34  Products / Arduino Due / Re: ITDB32 / SSD1289 With Due on: December 27, 2013, 03:39:18 pm

There seems to have been extensive problems with Sainsmart 3.2" TFT, not only with DUE, but MEGA also. You do not need external psu with this display.

My own setup is :-

Arduino DUE ( clone apparently smiley-sad  )
CTE TFT LCD/SD Shield for Arduino Due v1.04
Sainsmart  TFT_320QVT

If you are using the CTE shield, have you uncommented the code in UTFT\hardware\arm\HW_ARM_defines.h ?

// CTE TFT LCD/SD Shield for Arduino Due
// -------------------------------------
// Uncomment the following line if you are using this shield
#define CTE_DUE_SHIELD 1      < -----------------   !!! uncomment this line
// For this shield: RS=25, WR=26, CS=27, RST=28

Failing this, maybe you could include your init code?

Again for the CTE shield, and Sainsmart 3.2" TFT, the following code works for me.

#include <UTFT.h>
#include <UTouch.h>
#include <UTFT_Buttons.h>
UTFT myGLCD(ITDB32S,25,26,27,28);
UTouch myTouch(6,5,32,3,2);
UTFT_Buttons myButtons(&myGLCD, &myTouch);
extern uint8_t SmallFont[];
extern uint8_t BigFont[];

void setup()
// Open serial communications and wait for port to open:
while (!Serial) {
Serial.println("Initialising LCD.");
int butskip=myButtons.addButton( 85,  219 ,70,  20, "Skip");
Serial.println("LCD initialised.");
Serial.println("Waiting for Skip button.");
int skip=2;
while(skip==2) {
Serial.println("Skip button detected");

void loop()


35  Products / Arduino Due / Re: Printf in Arduino Due on: December 06, 2013, 10:35:59 am
Well I eluded to this in my previous post, but my 'tuppence worth, is that if you do need to issue "\r\n" then do so, but if the choice is taken away programatically such that "\n" will issue CR/LF regardless.............. what if a user actually requires independent control of "\n" , "\r", "\n\r" or am I missing the point here?


36  Products / Arduino Due / Re: Due GUI (Graphical user interface) - [now community project] on: December 06, 2013, 10:29:20 am

Are you still following this thread?

Now I have a preliminary tentative working sketch, I have a few points, one of which I think we perhaps need to collaborate on, the others I only mention that I have discovered, not that I have tried to diagnose or resolve yet.

1st) Touch is flipped on the X axis, but as you will be aware the


command no longer works as you stripped out the gubbins relating to it.

2nd) Unhide does not appear to work, as yet i have not persued why.

3rd) Text input formatting errors, such as ##, Cap and Space are all stacked and overlapping, again not persued yet, maybe this will resolve itself once I have done more with available font sizes.

My feeling is that we need to resolve the touch side of things more universally than at present, but I did not start to do anything about that yet, if you are still interested in trying to make this a universal project it has to be the way to go.

It would have been nice if there was more interest in this project, besides you, myself and of course Darren!!  smiley-cry


37  Products / Arduino Due / Re: Printf in Arduino Due on: November 30, 2013, 08:58:05 pm
This seems to be a long running issue in a variety of different areas, not just Arduino printf.

[Ctrl] J 10 0A  LF Line Feed FE A format effector which advances the active position to the same character position of the next line.
[Ctrl] M 13 0D  CR Carriage Return FE A format effector which moves the active position to the first character position on the same line.

Try playing with an old EPSON FX80 dot matrix printer, you will find it behaves in the manner as defined above as does Windows Hyperterminal, such that if you want to go down a line AND start at the beginning of that line, you NEED to issue both CR AND LF.

The serial monitor in the IDE doesn't care, but that does not mean that people should not be aware of what CR, CR/LF or LF is actually 'supposed' to do.


38  Products / Arduino Due / Re: Printf in Arduino Due on: November 30, 2013, 08:38:59 pm
 smiley-wink smiley-evil All the time it has taken to write all these forum messages, I am thinking CR/LF could have been implemented in less time smiley-wink


39  Products / Arduino Due / Re: Due GUI (Graphical user interface) - [now community project] on: November 30, 2013, 11:29:20 am
Hi All,

I am still tinkering with the text/font side of things, while doing so I came across this slight gremlin if anybody else is still playing with this?.....smiley-roll smiley-razz

Just a small bug in date format, 2 digit did not work correctly, here's the fix:

void DUEGUI::setObjectDate(int objectNumber,int yyyy, int month, int day, bool dateNorm, bool dateFour){
  if (dateNorm){
  } else {
  if (dateFour){
    GUIobject_top[objectNumber]=GUIobject_top[objectNumber]+"/"+String(yyyy,10)+" ";
  } else {
    GUIobject_top[objectNumber]=GUIobject_top[objectNumber]+"/"+String(yyyy,10).substring(2)+" ";


40  Products / Arduino Due / Re: Aduino Due + TFT Display on: November 29, 2013, 12:20:04 pm
@ sunilkumarambala5700

One of these will do you fine........
41  Products / Arduino Due / Re: Printf in Arduino Due on: November 29, 2013, 09:34:59 am
Actually I need to use the printf because as I am targetting to include similar the below
printf("Result Point is %Zd,%Zd",R.x,R.y);

to be honest I don't know how can I do it in the Serial.print

Out of interest, does %Zd format work on Arduino?


42  Products / Arduino Due / Re: Due appears as COM6 port but gives error "No device found on COM6" on upload on: November 27, 2013, 05:03:54 pm
I had been running my programs fine all day until I finally encountered this problem. This thread seemed to be the most helpful, but it seems like this has been going on for a while.
Since I'm relatively new to arduino, would it be better/easier if I seek a refund on my board?

If you have a clone board, it is situation normal, if you have a 'genuine' arduino board, I think you should try to PM Federico with date of purchase, serial number, and supplier you got your board from.

43  Products / Arduino Due / Re: Screen capture from CTE display buffer? on: November 23, 2013, 06:02:37 pm

I would also like to hear the outcome of this question!

I Don't currently have a CTE display yet, funds being one issue, but not the biggest deciding factor. Have you seen the new CTE display with frame buffer? Sufficient to pre-draw 8 screens in buffer memory for almost 'instant' screen draw!

Now if Henning decides to support this, I would suspect 'proper' screen captures would be possible with this thing, and I would like one for the 'pre-draw' capability...

However, what I actually came here to ask you was prompted by something I am trying to do with DUEGUI. Since you have various/several CTE displays, I wondered if you would be so kind as to supply me with the FONT IC font sizes, such as BVS_34, BVS_28. I understand the suffix to be pixel height, but what about width? Any help you could offer would be much appreciated!

Thanks and regards,

44  Products / Arduino Due / Re: Due GUI (Graphical user interface) - [now community project] on: November 21, 2013, 10:50:47 am

Btw, I noticed that in last post I failed to mention how to instantiate the DUEGUI object, for others to see:

#include <UTFT.h>
#include <UTouch.h>
#include <DUEGUI.h>    

UTFT myutft(HX8352A,22,23,31,33);                  
UTouch touch(25,26,27,29,30);
DUEGUI DueGUI(&myutft, &touch);

Thank you Darren for your support. Time is a precious thing, and I can relate to having to many projects and to little time. smiley


Hmm, what shield are you using with your display? That is not a combination of pins I have seen before....

My tuppence for what it is worth, I think the coldtears DUE shield was probably the first to come out, and naturally mates well with the CTE displays so far favoured by this project until now. As such I think it is worth mentioning the initialisation code for that situation.

UTFT       myGLCD(ITDB32S,25,26,27,28);
UTouch  myTouch(6,5,32,3,2);
DUEGUI  DueGUI( &myGLCD , &myTouch);

The DUEGUI UTouch->getX and getY have to be fudged. I noticed that on my display UTouch doesnt work quite right. So the getX and getY functions take the absolute values and corrects for X and Y.

Is this also the case with the genuine Henning library examples? Also what about the calibration routine? I was just thinking if possible it would be better to cure the cause, not the symptom. Since the underlying aim is now to produce a hardware independent DUEGUI, I just wonder if this fix could potentially cause problems as yet unknown on different hardware?

Was just wondering where the error may have cropped up.

I am still tinkering and going through the changes you have made, I also have yet to finish my test sketch which will essentially just be a modified version of Darren's original demo.

HOWEVER...............This is where I got distracted and went off at a tangent...... I don't like the single 16x16 font option, I was thinking it would be nice to assimilate a variety of fonts which would be a close approximation to the CTE Font ic fonts. The first problem with that idea is 34 point is not divisible by 8... similarly, neither is 28 which are the two principle font sizes in DUEGUI so far that I have encountered.

I was also thinking this is specifically to you Edward, is there anything in particular you want me to try/test/do for you, as I suspect I am likely to go off on several tangents with this thing..... smiley-roll


45  Products / Arduino Due / Re: Due GUI (Graphical user interface) - [now community project] on: November 20, 2013, 06:41:44 pm
I've just changed the thread title too......

Let me know if it needs changing again to reflect versioning etc.

Its nice to see you are still around, and if you feel inclined to stay involved that would be good! smiley-grin

mmmm  rover of any description land or otherwise, they never were great in the wet!!  smiley-lol

Pages: 1 2 [3] 4 5 ... 7