PUI converter error

Use this board to ask questions or have discussions with other Rich Displays users.
Post Reply
grmarks
Profound User
Posts: 30
Joined: Thu Apr 29, 2010 9:32 pm
First Name: Glenn
Last Name: Marks
Company Name: Pacific Brands
Country: Australia
Contact:

PUI converter error

Post by grmarks »

I have found a bug in the PUI converter/editor. After converting our "order entry" dds then saving to a dds member I found it would not compile. the problem is the QPUI000000 field. It has been defined 4 times in one record format (2 time in another). There are 34 indicators, in all, over the 4 fields. Is this just a "dummy" field to link indicators to ? If I rename the additional fields to QPUI000001,QPUI000002 etc it compiles OK. But is the V5R4 (or V6r1) "open access" compiler expecting to use these fields ?

The dds has 56 record formats and 11 sub-files so its big and complicated with lots of indicators and function keys (so many function keys that the side bar of buttons is twice as long as the "container" they are surposed to be in!).

I have noted they only appear in sub-file record formats.
User avatar
Alex
Profound Logic Staff Member
Posts: 233
Joined: Fri Jan 04, 2008 12:10 pm
First Name: Alex
Last Name: Roytman
Company Name: Profound Logic Software
Contact:

Re: PUI converter error

Post by Alex »

We are aware of this problem and it will be fixed for next release. In the mean time, renaming the additional fields in the DDS is ok. These are dummy fields and are not actually used by the preprocessor or open access.

We are also investigating and will be addressing the issue of many function keys that overflow the side bar. Our idea on this is to create a special button toolbar that will allow scrolling when the buttons overflow.
Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests