naelian's Recent Forum Activity

  • Could be nice to display a small area that can give focus to the project view to make it keyboard responsive after changing a parameter in debugger view. It's possible to click on it but many project as mine do specific things (as exiting !) when a mouse click is done so it could be useful.

  • It's very strange to see Scirra still using the 0.6.2 nw release and also still closing program using "window["nwgui"]["App"]["quit"]();" instead of "window.close();" because this last command seems to be more reliable. Actually the last nw release (0.7.1) try to solve some problems using nwgui.app.quit (issue 984) but it's still not fixed in 0.7.1. Using "window.close();" avoid this issue.

    so i edit C2runtime.js like this ...

    Acts.prototype.Close = function ()

         {

              if (this.runtime.isCocoonJs)

                  ?CocoonJS["App"]["forceToFinish"]();

              else if (this.runtime.isNodeWebkit)

                  ?//window["nwgui"]["App"]["quit"]();

                  ?window.close();

              else if (!this.is_arcade && !this.runtime.isDomFree)

                  ?window.close();

         };

    * R142 debugger problem update *

    Fullscreen mode still generating a error message in a node webkit debugger mode but Browser > Close is now working differently, the project itself is close but the debugger window need to be close in a second step ... so there is a real progress and no more issue using Browser.close.

    Thanks Scirra for updating nw to 0.7.0 in R142 release and use now window.close() to exit. App.quit will perhaps be reliable in 0.7.2 and better way in future but window.close seems now the only way to avoid major issues ... sure using "window.close()" will probably create other problems but seems actually the better choice !

    * R143 debugger problem update *

    Debugger now hangs using node webkit as debugger with this example.

  • Yes it's true there is a bug but you can avoid it before this will be fixed

    Create a constant text variable called quote and containing "

    so this will display quote = """

    And then use the run file command using

    quote & NodeWebkit.AppFolder & "/dxwebsetup.exe" & quote

    Doing so even with spaces in exe folder name or path (ex : "new project") the dxwebsetup program will be run, this is exactly the same way use by windows to manage spaces in path.

    Strangely some others node webkit plugin commands are running well if AppFolfer name or path use spaces such as "List Files" or "Copy Files"

  • Check if uncompressing the .7z file (install the "7zip" program to do so because it's not a standard format as .zip) create a folder into folder ... so if you get a /rex_pause_dt/rex_pause_dt/(files) only copy the "last" rex_pause_dt folder containing "files" into the behaviour folder.

    In editor because it's a behavior and not an object ... add the pause behavior to an object and then retrieve pause actions events and conditions using this object.

    This plugin is interesting to specifying some objects/or instances of an object that need to be paused and not. But if you need to put all your game in pause the standard command System.timescale set to 0 (paused) or 1 (running) do the job.

  • Thanks Ramones this is THE answer ! ... can i call you "Master" ? <img src="smileys/smiley1.gif" border="0" align="middle" />

    Doing so 107 is still triggered 26 times but with no more lags ... perhaps merging this "Default" animation + my code will provided even better speed because 107 will be triggered only once ! ... *need to be tested* !

  • It's not no instance is returned but many instances are returned if overlapped, use a "for each button" in a sub event after the "on touched Button" to retrieve each instance of Button touched

    So your code is not working when is no a unique answer.

    Can't be seen and can't be touched is different, blind people see nothing but can touch many things ! ... so all your visible tests do nothing but you can add a condition "Button is on layer" with the "for each button" to retrieve only all touched buttons on a specific layer and in your case and because you have only one button on each layer you will get a unique answer.

  • It's perhaps not really a R141 bug but a new different behaviour in "on animation finished" creating a lag bug in your game (impressive game) ... clean code with checking variables still the best way to avoid unwanted results in time.

    Scirra team will probably explain us asap if there is really a bug or not, but sure my coding avoid it ;p

  • event 108 is good, event 107 is probably not good now because "on animation" finished retrieve pillars one by one and not all instances.

    change 107 like this this :

    (If) On animation "pulse" finished and VisualFeedback not = -1

    (Do) => set VisualFeedback to -1

    (add a new event)

    (If) VisualFeedback = -1

    (Do) => set VisualFeedback to -2 and (all your set animation to "default")

    As all "default" animation will send at the same time the problem will be solved.

  • *I remove all refs to another bug link to force close a node webkit window because now solved*

    Link to .capx file (required!):

    http://db.tt/58lArN5N

    Steps to reproduce:

    1. Create a simple project requesting fullscreen

    2. Debug the project using node webkit as debugger

    Observed result: error msg (because of browser fullscreen resquest in code)

    Expected result: no error

    Browsers affected: node webkit in debug mode

    Operating system & service pack: Windows 7 64b SP1

    Construct 2 version: R141, R142, R143

  • *tips*

    Yes it's possible to edit the package.json to launch nw with fullscreen or kiosk mode set to "true" ... but in this case the project is launch with a fullscreen WHITE window and seems also spend time doing this.

    It's far better to use the C2 specific "loader" system and request a fullscreen at start using a empty "black" layer and then "go to" your layout when the loader system is completed (this should be instant unless in preview mode).

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Should be nice to provide a way to retrieve any parameters following a "nw.exe" using the node webkit plugin.

    Example : Renaming a "nw.exe" into "nw.scr" is working fine to create a Construct 2/Node webkit windows screensaver but i don't find any C2 way to retrieve parameters send by windows to change my project behaviour and make it more compliant with standard screensavers management.

    Note : The new node webkit 0.7.0 release seems provide new ways to retrieve this parameters but this version is also full of bugs so it's perhaps better to wait for 0.7.1 ;p

  • Hi everybody !

    A year later ...

    Sorry about the previous link but the "playtomic" plugin used to manage scores is no more working and make the game hang using it, so i will try to create a new version using the "new" Clay.io plugin, stay tune !

naelian's avatar

naelian

Member since 21 Apr, 2012

None one is following naelian yet!

Trophy Case

  • 12-Year Club
  • Coach One of your tutorials has over 1,000 readers
  • Email Verified

Progress

14/44
How to earn trophies