Ashley's Forum Posts

  • Regardless though, you still need to submit such false positives to the antivirus vendor, so they can improve their detection and make sure they don't incorrectly flag files. I suspect there is a single change they can make to their detection that will avoid all false positive cases with NW.js, so long as they have some examples of false positives submitted by users.

  • That's not the case though - suppose you tween the angle of a child in a hierarchy while the parent also rotates. You'd expect the child to rotate relative to the parent. So it isn't going to end on the tween end value. It's cases like this that mean the Tween behavior can't just say "at the end set the exact finish value" - in fact it used to, but it broke cases like the one I just described, so it can't do that.

  • You need to report false positives like this to the antivirus vendor. Only they can change what is detected as malicious or not.

  • There's loads of things that can cause floating point precision errors. Pretty much any fractional math can end up with results that are close to but not exactly correct. It's just something you have to deal with in any kind of tool with any kind of software that uses floating point data types. A famous example is that 0.1 + 0.2 = 0.30000000000000004.

  • The EXE file always has the same content regardless of the project, but changes between each NW.js version. You only need to submit it once per NW.js version that you export with that is incorrectly detected as malicious.

  • IIRC, the tween behavior cannot be exact, because it has to make changes in small steps, in case anything else changes the thing that is being tweened. However changing things in small steps is subject to floating point precision errors. It's just part of how maths works on computers. I don't think it's possible to reliably work around it - the best approach is to avoid making exact comparisons and allow a small tolerance (e.g. is within 0.001 of a number instead of exactly equal).

  • Browsers block access to certain folders for security reasons. For example if you granted a web page access to your entire Documents folder, the web page can access everything there - and a malicious page could then try to steal it all. To mitigate that you can't select the entire folder for certain sensitive folders like Desktop, Documents etc., but you can select a subfolder within them.

    If you only need to open one file, then just use the open file picker anyway - the user can just choose themselves rather than having your project try to list all available files.

  • As ever the first thing to check is the browser console and see if any errors are logged there. I'm not sure how to check the browser console on Xbox - Microsoft might have some documentation on how to remotely debug it.

  • It seems that anything containing "On collision with: (object with the solid behavior)" is no longer working. This is a huge problem.

    I just tried it and it's working fine. I've also not seen anyone else reporting the same problem.

    As ever it's impossible to help unless you file an issue providing all the necessary information.

  • If you want user-scrollable text the easiest solution is probably to put it in a HTML element object and add the style overflow-y: auto; which will add a vertical scrollbar when it fills up.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Browsers have a security restriction that you can't show custom cursors near the edge of the screen, to prevent custom cursors being a way to show misleading information outside the window. AFAIK NW.js still retains that restriction.

  • Well, I tried adding emoji to a layout and event sheet name, and the project could save and open just fine. So it seems to be working OK.

    If you think there's a bug then we need an issue filed following all the guidelines. Without that information all anyone is doing is guessing and it is common that people mis-attribute the cause of problems.

  • As I said, these are most likely false positives. The only solution is to report them to the antivirus vendors as false positives so they are no longer incorrectly identified as malicious.

  • It's most likely a false positive and you'll need to report it as such to the antivirus vendor.

  • I don't know how to help. It looks like maybe you're creating a native app instead of a web app? The former is not something we officially support for Facebook integration.