it is actually a Windows desktop app, and was indeed subclassing Xojo.Net.HTTPSocket, like in one of the examples (adding some methods on the class definition, then dropping the class on the windows to get an instance as a control and adding the Event Handlers there. No luck. I haven’t read the feedback case yet, but will do next.
In the meantime i did rewrite to use the Classic framework again, but with the classic I have the issue that using the Subclass-drop-on-window-to-create-control routine gives me strange behavior: it only works once, the second and all consecutive times i get a 400 error (bad request). must have something to do with secure=true.
To make it work i had to define everything in the class, event handlers and all. it works but it doesn’t feel right (the class doesn’t know anything about the control i have on the window, so now it’s hard coded, which is the opposite of encapsulation)
The alternative is of course to define everything in code, but that is outside of my skill set at the moment.
I was hoping my API tester app would turn into a business app we could use to speed up some of the master data entry we need to do, so i’m still hoping to find a better way to program this.