[JohnGB]

As a Paw user, I can say that I have found it extremely useful, and well worth the cost. However, it has been a disappointment to me that (at least the last time I asked), "dynamic values" are actually "dynamic string values" with no integer dynamic values supported.

I find dynamic value really useful, but in most of my use, it's dynamic integer values that I need, and so the feature is much less useful than it could be. Could you please comment on when you plan on implementing dynamic integer values into Paw?

Also, it appears that you have changed which versions of OS X you support, but I had to overwrite my old version of Paw with the new one to find this out. I strongly suggest making it clear which version of OS X the new version of Paw requires before someone installs it.

[mittsh]

Thanks for the feedback, John! As you're referring to dynamic values as integer values in JSON requests, it's clearly something we will fix. It was planned for Paw 3, but we had to drop features to keep a reasonable timeline. What we will be adding at the same time, is the ability to have dynamic values that return "objects" (or lists) so in a JSON, so you can dump a subtree.

About the OS X support, we haven't changed the requirements at all for this release. Paw is OS X 10.10+ (Yosemite+) since Paw 2.3. So maybe you had an earlier version? If you were prompted to update with no warning, that's a bug. Sorry about it! Will investigate…

[JohnGB]

No, I wasn't prompted to update without any warning. I downloaded v3 from the Paw website, but there was nothing there listing the version requirement, so I assumed it had not changed since the last version which I had.

Any ETA on being able to use integer values from JSON request?