Viewml status ?? / success stories ??

Hi all,

I am seriously considering to use viewml in my project. But before I choose 
to do so I would like to hear about people's experiences with it.

Is it already used in some embedded device ? 
Are there problems with stability ? 
I read some messages about memory leaks, is this solved ?

My own experience is that it looks pretty stable, but I am working on a 
feature (animated gif) that relies on the use of QTimer objects. And I found 
out that there can only be 100 instances of a QTimer.


#define MAXTIMERS 200

QObject::__timerobj * QObject::m_TimerList[MAXTIMERS];

QObject::__timerobj * QObject::CreateTimer(int interval)
{ 
  __timerobj * t = new __timerobj(this,interval);

  if(!m_bInit)
    InitializeTimers();

  for(int i=1; i<MAXTIMERS; i++)
  {
    if(m_TimerList[i] == NULL)
    {
      m_TimerList[i] = t;
      t->setId(i);

      return t;
      break;
    }
  } 
  return NULL; << This causes a crash
}	

As we can see timers are provided with an id , some integer number, that is 
the index of an array of 100 elements. That means that instantiation of 
timers is limited to 100. I think this limit can be eliminated by the use of 
a linked list of __timerobj elements. I'll be working on it, but I wanted it 
to be under your attention, as this could be a stability issue.

But as I mentioned before, could anyone provide me with success stories ??

To Jason Kingan, I read a question in the archives, someone asking about the 
development of viewml, you replied with the message that you recently didn't 
have much time to work on viewml, will you be working on it again soon ?

Thanks for your info,

Bye

Lambert Duijst

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[email protected]>.
To unsubscribe, E-mail to: <[email protected]>
To switch to the DIGEST mode, E-mail to <[email protected]>
To switch to the INDEX mode, E-mail to <[email protected]>
Send administrative queries to  <[email protected]>