next topic »

[Reply #30 on:]

Hi!
As i like libraries, i have done one for Timers on the Arduino DUE.

You can check it out here: https://github.com/ivanseidel/DueTimer

All 6 timers are fully implemented, and ready to play with...

May I ask you how I can use your file? I cannot include any library from out side. Is there anyway to run within one file? I would like to use a timer and change the REG by Serial Monitor.

Hi,
If you want to include the library to your project, than all you nees to do is to copy DueTimer.h and DueTimer.cpp to your sketch folder and include it normaly (#include "DueTimer.h").
What do you mean by change REG? And might I ask why can't you install the library?
Thanks,
Ivan

[Reply #31 on:]

I ported Ken Shirriff's IRremote library to work with the Due with a few improvements:
https://github.com/enternoescape/Arduino-IRremote-Due

Note: Don't forget to use a transistor to drive the IR LED. It might work powered directly, but probably not for long.

[Reply #32 on:]

I updated the RF24 (Nordic nRF24L01+) library to run on the Due.  I ran the basic ping/pong dyn example for testing.

Code: https://github.com/mcrosson/RF24

[Reply #33 on:]

Hi!

Finaly, I made the code independent from my own aplications, and could sucessfuly comment EVERY line of code.

What am I talking about?

Well, it's the First, Object Oriented User Interface for Arduino, with an Advanced controller of Touch and Views

https://github.com/ivanseidel/ArdUI/wiki

All based in Events and Callbacks, and also inspired on real Android code, you can easily implement whatever you want with it.

Some key features:
* Touch is handled BOTH in interrupt and Timer
  (Once a touch is triggered on the interrupt, Timer is the one who start trigering the event. Once no touch is detected, controll is passed to the Interrupt)

* Callbacks. Every view has it's own callbacks and events. onClick, onTouch, onChange.

* Touch Events. Like Android, touch events are implemented, such as: ACTION_DOWN, ACTION_UP, ACTION_MOVE, ACTION_HOVER_ENTER, ACTION_HOVER_EXIT

* Views are implemented extending main class View, or other that implements View. Object oriented allows user to extend a class and improve whatever he wants to.
Views already implemented: SeekBar, ProgressBar, Button, CheckBox, TextView and ViewGroup, that allows many views in a single views.

* Tree Rendering: Once a render is triggered, the view start rendering it's own tree. For example:
If you have 5 views inside a ViewGroup, and one of the 5 is also a ViewGroup containing more 10 views, calling a "render()" on the top view of the tree, will start rendering all the views. Also, calling a "render(false)" will start rendering ONLY the "invalidated" views (only what is necessary).

* Relative rendering: If one view is inside the other, it's relative to the other. One position in a view is ALWAYS relative to it's parent. Moving a view that has views inside, cause it's childs to move with it. Rendering, and Touch are handled relative also.

* Changing Between rootViews is very easy (for example, running another function, state,...). Prepare all your views, and then register the current one on ArdUI. He will make the rest...

Documentation is not done yet, and there is a lot to be done (and improved). I'm using it currently on my robots: TendaDigital.net and it seems to be VERY robust and thrustable.

This is the kind of library, that does everything, you just need to know how to use it (Yet, a little complicated, since I'm still documenting).

[Reply #34 on:]

Hi,
I always use this library for myself, and I personaly think that is VERY usefull. Its clear that Arduino doesen't support real parallel processes, but we can "sort" of do it with scheduled tasks.

Yes, there is already an class called "Scheduller", but for big projects (likes the ones I do, with more than 15.000 lines), it's not "good" enought...

I LOVE Object Oriented stuff, and this follows it pretty much.

Check out the library here: https://github.com/ivanseidel/ArduinoThread

It also works for ANY arduino, but I implemented thinking on the DUE, since it's capable of more stuff (I use it with my ArduinOS, and it's just perfect =] )

Any suggestions are welcome!

[Reply #35 on:]

First version of the DueGUI library is now downloadable...


http://forum.arduino.cc/index.php?topic=164788.0