If you made a server side script, there's no reason you couldn't also POST new data to the server with the AJAX object.
The manual gave the full definition: it calculates (y - a) / (b - a), which is the opposite of lerp. So unlerp(a, b, lerp(a, b, x)) = x. E.g. lerp(10, 20, 0.5) gives 15, so unlerp(10, 20, 15) gives 0.5.
Writing our own wrapper is just about beyond our resources at the moment, although it's not out of the question. I would only consider it as a last-ditch effort if all other methods have completely failed first.
It seems a much easier solution is to integrate Game Center, IAP and iAds in to CocoonJS and directCanvas. I'll contact them about this and see what can be done. If both supported all three of those iOS features, would that solve the problem?
Develop games in your browser. Powerful, performant & highly capable.
I think PhoneGap 2.0 is out, does that still do it?
PhoneGap itself requires that permission to work, so I don't think you can remove it. It's not at all unusual for an app to request internet access though, and also allows you to make AJAX calls and such.
Moved to Construct 2 general forum since it's highly doubtful this is a Construct 2 bug.
Can you provide some more details about the system you are having this problem on? What's the hardware spec, OS, etc.?
According to Microsoft documentation, error 193 is "ERROR_BAD_EXE_FORMAT - not a valid Win32 application". It sounds like the Scintilla DLL has become corrupt. It may be the USB stick is old and failing, or you need to delete all the files off it and reinstall.
3D physics engines are even more CPU intensive than 2D physics engines, so I think we'd be best sticking with Box2D until we add 3D features, which we have no current plans for.
LintuSotaRauha - I disagree. I think you would be teaching a bad practice right away - copying and pasting code should be avoided in all programming languages, including C2 events and javascript.
Some better ideas:
I'm pretty sure your graphics card or the graphics driver is causing this. The first screenshot looks like either failing hardware or a driver bug.
Downgrading from Win7 to XP sounds like the wrong move. Drivers are usually older and buggier for Windows XP, so that likely exacerbated any driver problems. Try Windows 7 again and double check you have the latest drivers. (What do you mean by "minimal resolution"?)
Mind you 7 years old is pretty old for graphics hardware, you might be stuck with crappy drivers if the manufacturer has ended product support.
entelechystudios - this thread is old and out of date, check for the newer threads and blog posts about Awesomium.
Maybe your computer isn't fast enough to draw in fullscreen but it can handle a smaller window?
It's a tradeoff between having a single large image (which wastes memory) and thousands of tiny tiles (which will be slow due to increasing the object count). 256-512 sized tiles is a good middleground.
There are no hard and fast rules, the best thing to do is test on a low-end machine and see how it performs.
Using one large image should be avoided at all costs - it will waste a huge amount of memory.
Using a series of 256x256 or 512x512 tiles should be fine, but I wouldn't go any smaller than 256, since then you start getting in to higher object counts.