Skip to content

Commit b941e36

Browse files
authored
Merge pull request rage#208 from MagnusHJensen/patch-2
Correct typos 13.5
2 parents d13cb95 + 5cda305 commit b941e36

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

data/part-13/5-multiple-views.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Thus far our graphical interfaces have always included only one view. Next, we'l
2626

2727
<!-- Yleisesti ottaen näkymät luodaan Scene-olion avulla, joiden välillä siirtyminen tapahtuu sovellukseen kytkettyjen tapahtumien avulla. Alla olevassa esimerkissä on luotu kaksi erillistä Scene-oliota, joista kummallakin on oma sisältö sekä sisältöön liittyvä tapahtuma. Alla Scene-olioihin ei ole erikseen liitetty käyttöliittymän asetteluun käytettyä komponenttia (esim. BorderPane), vaan kummassakin Scene-oliossa on täsmälleen yksi käyttöliittymäkomponentti. -->
2828

29-
Generally the views are created as Scene-objects and the transitioning between them happens with events bound to the application. The example below has to Scene objects which both have their own content and an event related to the content. Instead of having an object for laying out components (such as BorderPane) in the example Scene objects, both objects have just one user interface component.
29+
Generally the views are created as Scene-objects and the transitioning between them happens with events bound to the application. The example below has two Scene objects which both have their own content and an event related to the content. Instead of having an object for laying out components (such as BorderPane) in the example Scene objects, both objects have just one user interface component.
3030

3131

3232
```java

0 commit comments

Comments
 (0)