Evaluating/Purchasing TextControl

Do you have a timeline for the next version?

There are 269 predefined actions but we cannot access all of these with wpaGetFlags ... why is this?

The HTML code will change in the next release (when you buy now, you also will get the new version when available).

With the premium license there is also an inbuilt XML reader / writer which creates more streamlined code. It avoids the style tags which make it complicated to post process the text. You can send me a sample what kind of data you need.

wpaGetFlags only handles the states of predefined actions, no custom ids. But it should be possible to inbuild a command to disable all buttons at once.

Whilst evaluating TextControl (which we are in the process of purchasing) we have come across a number of issues which we are not entirely happy about:

1. The control writes code with much use of <div> blocks but when , for example, we have two tables with a space between them, it cannot read the HTML it has written correctly.
2. Whenever we try to correct this behaviour by swapping <div> for a <p><span> combination, which it does read correctly, the control then stuffs unnecessary - and incorrect - font information into the <p> tag. This means that what gets written does not match what was displayed.
3. When we disable and re-enable "buttons", the FontSizeSelection "button" changes value.
4. We are unable to disable and re-enable all "buttons" because the array that .wpaGetFlags() returns contains a single, 100-character, element yet the IDs for the buttons range up past 110.

Could we please have your comments