Ashley's Forum Posts

  • According to the node-webkit issue there is now a fix for this which I've tested and works here (and several other users report it works). I'm going to close this report now, the fix should make its way to a C2 update soon.

  • I can't reproduce on a Samsung Galaxy S3 running cyanogenmod. I think it's to do with audio preloading, and the Android stock browser has poor audio support, so it may be unable to report the preloaded status correctly. Can you confirm by turning off 'Preload audio' in project properties and seeing if it works again on an affected device?

    Either way I've turned off audio preloading for the Android stock browser for the next build, since I can believe it is too crappy to work (that browser is a nightmare... please encourage everyone to get Chrome for Android instead!)

  • Closing, please post a new report with some way for us to reproduce the problem if anyone wants this further investigated.

  • You do not have permission to view this post

  • I'm a little skeptical of voting systems. I do keep a close eye on the forum and the regularity features are mentioned are already a rough sort of voting system. The problems I see with formalising it are:

    1) users vote for things which are technically an extraordinary amount of work, or are a completely different product, e.g. 3D. I'd hate to have to keep defending why we are not doing 3D when it's the most voted feature.

    2) I am actually a little skeptical that people really know what they want, first with the WebGL shader effects feature, and then much more clearly with the multiplayer feature. Multiplayer was extremely highly voted for in previous polls. We developed it over several months - it was hard work, and involved quite a lot of research and prototyping before that. Despite the huge amount of heavy lifting the multiplayer engine does for you internally, networking is just a difficult topic in general, and I think that's why it's seen fairly low uptake. I think people see features in the voting stage as magical solutions that will solve everything with no effort, but realistically nothing ever turns out like that. I think we documented it well, it's just hard to design multiplayer games. Maybe it will see increased uptake over time, but so far it was an awful lot of effort for a feature that has seen niche use in practice.

    3) Users don't see the internal technical complexity. For example a common request is to get the editor tabs to persist the same colors between launches. Seems simple and trivial, but I've looked and it's buried somewhere in the black box of our pre-compiled UI library, so it's really difficult. So then you might have an apparently easy feature really high voted, and everyone's wondering why don't we just do it?!? Accusations follow that we ignore our users, etc.

    4) Lots of suggestions come without compelling use cases, e.g. "why don't you make a feature to return the Nth prime number?" Well... why? Who needs it? What do they need it for? Why is it so important? Lots of one-line suggestions lack a thorough definition that identifies it as something really compelling that deserves attention, or are so broadly defined or vague that it's hard to know how to actually address it with code. Every feature we work on comes with opportunity cost - the possibility we're not working on something else that could be even more important.

    Obviously we wouldn't exist without our customers, and exist to serve them. However there is a careful balancing act to be made and I think user voting is a pretty distorted version of that. Also, I'm pretty sure Tom has no time to work on it

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • iOS 8 introduces WebGL support as well as full JIT compilation for Javascript, making the in-app web view as good as Safari. This means you'll be able to PhoneGap apps for iOS 8 and they'll be fast and with good feature support, no wrappers needed. It's going to be a pretty big change!

  • Deprecating means hidden-by-default but still accessible, not completely removed. We know people still depend on it.

    I'll try get the expressions in for the next beta.

  • iOS has always been problematic because they've imposed severe restrictions on apps implementing browser features, and then provided very slow built-in browser features for apps (UIWebView).

    This all changes with iOS 8: the UIWebView will have the full performance and features of the browser, as well as WebGL support. You should then be able to get great results with PhoneGap. Until then Ejecta is about as good a stepping stone as can be made with Apple's tight restrictions, and it does have its limitations, but it should be workable if you design from the start with those limitations in mind.

    iOS 8 should be out in a couple of months and luckily iOS is pretty good at quickly getting a majority of devices on the latest version. So hopefully by the end of the year the picture will be very different.

  • Do you have any use cases for this other than "manual" letterbox? Only CocoonJS lacks this feature, and we will likely deprecate support for CocoonJS in the near future due to problems like this.

  • The animations system was designed to be case insensitive. If you find part of it which is case sensitive, please file a bug report following all the guidelines.

    Note if you use some features like "compare values" from System, that is by default case sensitive, because it is a general purpose comparison as opposed to part of the animations feature.

  • I don't think there is any conclusive evidence that any of these services were "hacked" in the sense they had security problems that were exploited to gain access to the accounts. I think it is far more likely that it was either phishing or just really dedicated snooping/detective work to find out account names, then brute forcing them with common password lists, or something else relatively non-tech along those lines.

    Many people have very poor password security practices, and share the same passwords over multiple sites, or use weak or commonly chosen passwords. This makes your accounts much easier to hack. I strongly recommend using a password manager like KeePass. It makes it easy to have very strong un-guessable passwords for each account you have, while only needing to remember one password.

  • You can overwrite the version of node-webkit C2 uses by pasting the node-webkit files over the ones at <install path>\exporters\html5\node-webkit.

    rogerwang - my best theory is since it doesn't happen in Chrome that the blocking is happening in node.js. However I can't explain why the threaded compositing option would affect it.

  • It should work in Chrome for Android and Crosswalk, both of which have WebRTC support. There are no specific considerations for multiplayer; it should even work through cell data connections (e.g. 3G) providing the host is reachable, as ever the main concern is just getting it to work with touch input.

  • TwinTails Why? What's wrong with using a text box?

  • You can and should use the C2 IAP object on Windows Phone 8.1+. On Windows Phone 8.0 IAP is not officially supported, although there are third party plugins that support it. Also check you've got test mode set correctly.

    If you think the browser object triggers are not firing correctly then please file a bug report following all the guidelines or it will not be investigated.