Blak window "node-webkit"

Comments

• TheMadExile

  September 2016

  I assume that you're clicking on the external link shown in that screenshot—the first one, "Putain vous êtes qui?".
  
  If it is not supped to be an external link.
  You'll need to fix whatever you've done which is making SugarCube 2 think that it is an external link. Show the link code?
  
  If it actually is an external link.
  Maybe the host is down or you need to wait longer, we couldn't really say without knowing what you're linking to. You could always publish your project and test it in a normal browser.
  
  
  PS: This is unrelated to your current issue, however, you may translate most of the UI text in SugarCube 2—pretty much only fatal errors are hard coded. I'm simply mentioning this because your screenshots show the core menus in English.
  
• Logrent

  September 2016

  It's not suppoed to be an external link,
  

  [[ "Qui êtes vous?"|Acte 1.3: Putain?]]
  

  
  I change the Format of my game after some time, I started it in Harlowe and change for sugarcube. Can it be the reason?
  
  

  PS: This is unrelated to your current issue, however, you may translate most of the UI text in SugarCube 2—pretty much only fatal errors are hard coded. I'm simply mentioning this because your screenshots show the core menus in English.

  
  in fact i have one in Frensh and an other in English ^^
• greyelf

  September 2016

  The install-able release of the Twine 2 application is built using a technology known as NW.js (node-web), basically a custom web-browser.
  
  When you say "click in some of my links" I am guessing you mean the ones that open an external web-page.
  
  I believe your issue is a result of either:
  
  1. The URL associated with the link is incorrect.
  2. The custom web-browser can't display the target web-page.
  
  Try first using the Publish to File option to generate a Story HTML file and opening that file within your web-browser, then test the external link again and assuming that the URL is correct then it should work.
• greyelf

  September 2016

  It is generally not a good idea to use punctuation characters like colon and question marks in a Passage Name, strange things can happen if you do because those characters can have special meanings.
  

  [[ "Qui êtes vous?"|Acte 1.3 - Putain]]
  
• Logrent

  September 2016

  Okay, i try to delete them
  

  Try first using the Publish to File option to generate a Story HTML file and opening that file within your web-browser, then test the external link again and assuming that the URL is correct then it should work.

  
  I don't want an external link to a URl ^^
  
  And when i Publish the file, the link is just broke
• TheMadExile

  September 2016

  Logrent wrote: »

  It's not suppoed to be an external link,

  [[ "Qui êtes vous?"|Acte 1.3: Putain?]]
  

  That is not the link I pointed out from your first screenshot—it's the one with the box which has a NE pointing arrow in it on the right side of the link, specifically "Putain vous êtes qui?".
  
  

  greyelf wrote: »

  It is generally not a good idea to use punctuation characters like colon and question marks in a Passage Name, strange things can happen if you do because those characters can have special meanings.

  Greyelf is correct. That said, that particular bug should be fixed in the next version of Twine 2, which is in beta as we speak.
  
• Logrent

  September 2016

  Acte 1.3: Putain?

  
  Sorry, I failed
  
  I Have other example of the same problem in my games:
  

  [[Accepter -> Acte 1.6: Let's go to work.]]
  

  [[ Vous arrivez dans votre lycée après plusieurs minutes de trajet-> Acte 2.1: La rentrée]]
  

  
  I will try to delete the punctuation
  
  
• TheMadExile

  September 2016

  Logrent wrote: »

  I Have other example of the same problem in my games:

  [[Accepter -> Acte 1.6: Let's go to work.]]
  

  [[ Vous arrivez dans votre lycée après plusieurs minutes de trajet-> Acte 2.1: La rentrée]]
  

  The basic issue is that you have spurious leading/trailing whitespace within your link markup, in both the text and link components.
  
  SugarCube elides leading/trailing whitespace within links, so that a link like foo -> bar works as you'd probably expect it to—text of "foo", linking to the passage "bar".
  
  Twine 2's (as of v2.0.11) automatic passage creation feature, however, does not elide leading/trailing whitespace within links so that a link like foo -> bar creates the passage " bar"—notice the leading space—rather than "bar". Frankly, this is daft behavior, which has caused no shortage of heartache for authors/developers like you.
  
  As to why SugarCube is incorrectly showing some of your links as external links. As noted above, a link like foo -> bar automatically creates the passage " bar" in Twine 2, but will link to the passage "bar" in SugarCube. SugarCube will not be able to find a passage named "bar", so it should mark the link as broken under normal circumstances. However, SugarCube's external link detector is, currently, fairly aggressive and so, due to some of the characters within your passage names, your links are being erroneously flagged as external. This is only an issue because of the disconnect between the name that SugarCube is looking for and the passage's actual name.
  
  
  The solution to your problem is to remove the leading/trailing whitespace from your links and, unfortunately, you'll also need to edit the passage names to remove it from them as well.
  
  For example, they should look like one of the following:

  [[text|link]]
  [[text->link]]
  [[link<-text]]
  
  [[Accepter|Acte 1.6: Let's go to work.]]
  [[Accepter->Acte 1.6: Let's go to work.]]
  [[Acte 1.6: Let's go to work.<-Accepter]]
  
  [[Vous arrivez dans votre lycée après plusieurs minutes de trajet|Acte 2.1: La rentrée]]
  [[Vous arrivez dans votre lycée après plusieurs minutes de trajet->Acte 2.1: La rentrée]]
  [[Acte 2.1: La rentrée<-Vous arrivez dans votre lycée après plusieurs minutes de trajet]]