Why use QView?
  



The Clarion development environment does not provide an easy way to examine queues at run-time. This can make debugging queue problems a tedious task, especially when they contain references to other queues (a "queue of queues"). OK, it is simple to display any queue in a list control using PROP:FROM but remember to watch out for arrays (run-time problems guaranteed). Clarion's implementation of linked lists is one of the language's many strengths, but until you can "see" your queues you will find it hard to take full advantage of their power.


QView gives you instant visual access to any queue, along with the ability to drill down into any referenced queues. Add the global template and with one line of code you can safely examine any queue. You can format fields using standard clarion pictures that will be remembered next time the library sees the queue and you can dump any queue out to a delimited file or the clipboard (great for pasting into Excel). You can sort a queue, filter it, edit it and write it back into your program. You can even save a queue and load the contents next time your program runs. Debugging queues is easy with QView...


Some queues:

ATypedQueue    QUEUE,TYPE
SomeStringRef    &STRING
SomeDates        LONG,DIM(10,2)
SomeTimes        LONG,DIM(100)
               END

MyTestQueue    QUEUE,PRE(MTQ)
SomeString       STRING(50)
SomeQueueRef     &ATypedQueue
               END



A line of code:

  QVEdit(MyTestQueue,'debugging')

A problem solved:

graphic