KDE TechBase - User contributions [en]

Edit Markup/fi

2012-12-23T17:08:51Z

Centerlink:

<languages />
== Käytettävissä olevat työkalut ==


* [[Special:MyLanguage/Typographical_Guidelines]] standardisoi kotoistamisessa käytettävät markup-merkinnät, joko virallisia käsikirjoja varten (DocBook) tai muille kielille. Viittaa tähän taajaan, koska markup-merkkejä määritellään uudelleen täsmäämään kotoistajien tarpeita.


== Työnkulku vaihe 1 ==

=== Vanhan markup-merkinnän korjaaminen ===

* Tarkista, että jokaista lohkon tai alilohkon otsaketta seuraa tyhjä rivi.

* Monille sivuille on asetettu useita sisennyksiä. Tämä sisällytettiin aikaisempaan mediawiki-dokumentaatioon, mutta ei ole enää hyväksyttävää, koska se aiheuttaa pulmia muiden muotojen viennissä, joten järjestele uudelleen käyttäen vain yksittäisiä sisennyksiä. Etumerkki-luettelot voivat edelleen olla sisäkkäisiä.

* ASCII-hymiöt aiheuttavat pulmia ja ne on poistettava. Ne voidaan korvata pienikokoisilla (11px?) oxygen-kuvakkeilla. Monia muita on saatavilla Wikimedia Commons -sivustolta - lisätiedot lisätään tänne.

* Muotoa <nowiki>[[Kotoistamistyökulku]]</nowiki> olevat sisäiset linkit olisi muokattava täydelliseen muotoon, jotka näyttävät linkin, sitten näkyvän tekstin, kuten <nowiki>[[Special:myLanguage/Translation_Workflow|Kotoistamistyökulku]]</nowiki>

* Syöttötekstin näyttämiseen on käytetty monia tyylejä, mukaan lukien <nowiki><code>, <pre></nowiki> ja taulukot ja laatikot. Käyttäjän syötteeksi tarkoitetun tekstin tulisi käyttää Input-mallinnetta, <nowiki>{{Input|1=syöteteksti (voi olla useita rivejä tai yksi rivi)}}</nowiki>. Voit yhä käyttää <nowiki><code></nowiki> hyvin lyhyelle syötteelle, jos et halua tekstin esiintyvän usealla rivillä.

* Pääteikkunatulosteet ja virheilmoitusviestit on samalla tavalla merkitty vaihtelevasti. Nämä tulisi korvata Output-mallinteella, <nowiki>{{Output|1=pääteikkunatuloste}}</nowiki>

* Jokaisen sivun tulisi päättyä Category-luokkalauseeseen. Näiden on oltava standardisoituja luokkia. Luokkien nykyinen luettelo löydetään miltä tahansa kotoistajan sivulta linkitettynä [[Translation_Help_Needed|tämä kielisivu]]

* Varmista, että missään kappaleessa ei ole parittomia sulkeita. Jos löydät parittomia sulkeita, lisää puuttuvat sulkeet — mahdollisesti kommenteissa kuten tämä: {{Input|1=<nowiki> a)</nowiki>}}

* Luetteloissa pitäisi olla etumerkkirivien välissä tyhjä rivi. Katso kappeleita luetteloissa [[Special:myLanguage/Toolbox#Bulleted Lists|Etumerkilliset luettelot]].

* Taulukot pitäisi jakaa samalla tavalla niin että jokaisen rivin välissä on tyhjä rivi. Ensimmäisellä ja viimeisellä rivillä on oltava parilliset aaltosulkeet.

== Vaihe 2 - Opas uuteen markup-merkintään ==

=== Merkitään linkit kotoistamiseen ===

* Yksittäisen linkin, sellaisen kuin sovelluksen nimi kohteessa Applications/Internet, pitäisi käyttää muotoa <nowiki>[[Special:myLanguage/Ark|<translate>Ark</translate>]]</nowiki>
* Siellä missä linkki on lauseen sisällä, koko linkki pitäisi pitää kotoistettavan viestin sisällä.

=== Erityistunnisteet ===

* Tunnista kaikki näppäimistön näppäinnimet, ja tagitunnisteet, esim.: <nowiki><keycap>Enter</keycap></nowiki>
* Sisällytä samanaikaisen näppäinten painallukset <nowiki><keycap></nowiki> -tagitunniste, esim.: <keycap>Ctrl + Alt + F1</keycap>. Huomaa, että erotin on (välilyönti)+(välilyönti)
* Kohtele valikkosarjoja samalla tavalla käyttäen <nowiki><menuchoice></nowiki> -tagitunnistetta, esim.: <menuchoice>System Settings -> Account Details -> Social Desktop</menuchoice>. Huomaa, että erotin on (välilyönti)->(välilyönti)

{{Warning|2=Varoitus|1=ÄLÄ KOSKAAN lisää translate-lohkotagitunnisteita (niitä, jotka näyttävät seuraavilta <nowiki>< !--T:18-- ></nowiki>). Ohjelmisto tekee kaikkien vaadittujen tagitunnisteiden käsittelyn, ja manuaaliset muutokset rikkovat järjestelmän.}}

=== Lihavoidut ===

* Tunnista ohjelmanimet ja merkitse ne lihavoituna, esim.: '''Klipper'''
* Tunnista nimiöt ja nimet, joita käyttäjä ei voi muuttaa, ja merkitse ne lihavoiduiksi.
* Poista kaikki aikaisemmat lihavoinnit, jotka on kirjoitettu aiemmin, mutta jotka eivät täsmää tähän ohjeeseen. (Katso alle sanan tai fraasin painottamisesta.)
* Ikkunan otsikkotekstit ja kuvakkeiden nimiöt merkitään myös lihavoiduiksi.

=== Kursiivit ===

* Kursivointia käytetään painottamiseen kuten tehdään ei-teknisessä kirjoittamisessa
* Käytä kursiivia epätavallisen sanan tai fraasin ensimmäisessä esiintymisessä, ja jos mahdollista, linkitä se kohteeseen #Glossary tai sanakirjasanaan.
* Kun viitataan muihin (ulkoisiin) teoksiin, otsikot kursivoidaan.

=== Yhdistetty lihavointi ja kursivointi ===

* Tätä pitäisi käyttää ainoastaan asiayhteydessä, jossa käyttäjä on korvannut tekstiä, esim.: "Uudet osoitekirjatietueesi ovat kohteessa <tt>/home/</tt>'''''user'''''<tt>/share/contacts</tt>"

{{Tip|2=Vihje|Yksinkertaistettuja määrittelyjä - käyttäjät käynnistävät ''Ohjelmia'', ohjelmat käyttävät ''komponentteja''}}

== Kohteet, jotka aiheuttavat kotoistamispulmia ==

Useat kohteet on tunnistettu ja niistä on keskusteltu, ja ehdotetut ratkaisut ovat seuraavassa kappaleessa:

* [[Typographical_Guidelines#Lists|Luetteloiden jakaminen luettavuuden vuoksi]]
* [[Typographical_Guidelines#Keeping_things_together|Muut "luettavuus"katkokset]]
* [[Typographical_Guidelines#Unbalanced_brackets|Sulkeet jakavat lohkoja]]

Nämä havaitaan tavallisesti ensimmäisen markup-merkinnän jälkeen ja saattaa olla välttämätöntä järjestää uudelleen välit ja/tai rakenne pulmien välttämiseksi.

== Lähes valmis ==


* Kirjoita lopussa olevaan yhteenvetokenttään, mitä olet tehnyt markup-muokkauksessa.
* Käytä <menuchoice>Esikatselu</menuchoice> ja lue koko työsi lävitse. Jos olet tyytyväinen, tallenna sivu.
* Käytä sivupalkin linkkiä julkaisun pyytämiseen - se ottaa sivusi, kun lisäät muokkaamasi sivun verkko-osoitteen. Linkkisi liittäminen sinne kertoo meille, että uskot sivun olevan valmis kotoistajien työskentelyä varten. Tutkimme sitä, ja jos olemme tyytyväisiä, otamme sen mukaan kotoistamiseen.


[[Category:Translator_Help]]

Translations:Edit Markup/30/fi

2012-12-23T17:08:51Z

Centerlink:

* [[Typographical_Guidelines#Lists|Luetteloiden jakaminen luettavuuden vuoksi]]
* [[Typographical_Guidelines#Keeping_things_together|Muut "luettavuus"katkokset]]
* [[Typographical_Guidelines#Unbalanced_brackets|Sulkeet jakavat lohkoja]]

Edit Markup/fi

2012-12-23T17:06:30Z

Centerlink:

<languages />
== Käytettävissä olevat työkalut ==


* [[Special:MyLanguage/Typographical_Guidelines]] standardisoi kotoistamisessa käytettävät markup-merkinnät, joko virallisia käsikirjoja varten (DocBook) tai muille kielille. Viittaa tähän taajaan, koska markup-merkkejä määritellään uudelleen täsmäämään kotoistajien tarpeita.


== Työnkulku vaihe 1 ==

=== Vanhan markup-merkinnän korjaaminen ===

* Tarkista, että jokaista lohkon tai alilohkon otsaketta seuraa tyhjä rivi.

* Monille sivuille on asetettu useita sisennyksiä. Tämä sisällytettiin aikaisempaan mediawiki-dokumentaatioon, mutta ei ole enää hyväksyttävää, koska se aiheuttaa pulmia muiden muotojen viennissä, joten järjestele uudelleen käyttäen vain yksittäisiä sisennyksiä. Etumerkki-luettelot voivat edelleen olla sisäkkäisiä.

* ASCII-hymiöt aiheuttavat pulmia ja ne on poistettava. Ne voidaan korvata pienikokoisilla (11px?) oxygen-kuvakkeilla. Monia muita on saatavilla Wikimedia Commons -sivustolta - lisätiedot lisätään tänne.

* Muotoa <nowiki>[[Kotoistamistyökulku]]</nowiki> olevat sisäiset linkit olisi muokattava täydelliseen muotoon, jotka näyttävät linkin, sitten näkyvän tekstin, kuten <nowiki>[[Special:myLanguage/Translation_Workflow|Kotoistamistyökulku]]</nowiki>

* Syöttötekstin näyttämiseen on käytetty monia tyylejä, mukaan lukien <nowiki><code>, <pre></nowiki> ja taulukot ja laatikot. Käyttäjän syötteeksi tarkoitetun tekstin tulisi käyttää Input-mallinnetta, <nowiki>{{Input|1=syöteteksti (voi olla useita rivejä tai yksi rivi)}}</nowiki>. Voit yhä käyttää <nowiki><code></nowiki> hyvin lyhyelle syötteelle, jos et halua tekstin esiintyvän usealla rivillä.

* Pääteikkunatulosteet ja virheilmoitusviestit on samalla tavalla merkitty vaihtelevasti. Nämä tulisi korvata Output-mallinteella, <nowiki>{{Output|1=pääteikkunatuloste}}</nowiki>

* Jokaisen sivun tulisi päättyä Category-luokkalauseeseen. Näiden on oltava standardisoituja luokkia. Luokkien nykyinen luettelo löydetään miltä tahansa kotoistajan sivulta linkitettynä [[Translation_Help_Needed|tämä kielisivu]]

* Varmista, että missään kappaleessa ei ole parittomia sulkeita. Jos löydät parittomia sulkeita, lisää puuttuvat sulkeet — mahdollisesti kommenteissa kuten tämä: {{Input|1=<nowiki> a)</nowiki>}}

* Luetteloissa pitäisi olla etumerkkirivien välissä tyhjä rivi. Katso kappeleita luetteloissa [[Special:myLanguage/Toolbox#Bulleted Lists|Etumerkilliset luettelot]].

* Taulukot pitäisi jakaa samalla tavalla niin että jokaisen rivin välissä on tyhjä rivi. Ensimmäisellä ja viimeisellä rivillä on oltava parilliset aaltosulkeet.

== Vaihe 2 - Opas uuteen markup-merkintään ==

=== Merkitään linkit kotoistamiseen ===

* Yksittäisen linkin, sellaisen kuin sovelluksen nimi kohteessa Applications/Internet, pitäisi käyttää muotoa <nowiki>[[Special:myLanguage/Ark|<translate>Ark</translate>]]</nowiki>
* Siellä missä linkki on lauseen sisällä, koko linkki pitäisi pitää kotoistettavan viestin sisällä.

=== Erityistunnisteet ===

* Tunnista kaikki näppäimistön näppäinnimet, ja tagitunnisteet, esim.: <nowiki><keycap>Enter</keycap></nowiki>
* Sisällytä samanaikaisen näppäinten painallukset <nowiki><keycap></nowiki> -tagitunniste, esim.: <keycap>Ctrl + Alt + F1</keycap>. Huomaa, että erotin on (välilyönti)+(välilyönti)
* Kohtele valikkosarjoja samalla tavalla käyttäen <nowiki><menuchoice></nowiki> -tagitunnistetta, esim.: <menuchoice>System Settings -> Account Details -> Social Desktop</menuchoice>. Huomaa, että erotin on (välilyönti)->(välilyönti)

{{Warning|2=Varoitus|1=ÄLÄ KOSKAAN lisää translate-lohkotagitunnisteita (niitä, jotka näyttävät seuraavilta <nowiki>< !--T:18-- ></nowiki>). Ohjelmisto tekee kaikkien vaadittujen tagitunnisteiden käsittelyn, ja manuaaliset muutokset rikkovat järjestelmän.}}

=== Lihavoidut ===

* Tunnista ohjelmanimet ja merkitse ne lihavoituna, esim.: '''Klipper'''
* Tunnista nimiöt ja nimet, joita käyttäjä ei voi muuttaa, ja merkitse ne lihavoiduiksi.
* Poista kaikki aikaisemmat lihavoinnit, jotka on kirjoitettu aiemmin, mutta jotka eivät täsmää tähän ohjeeseen. (Katso alle sanan tai fraasin painottamisesta.)
* Ikkunan otsikkotekstit ja kuvakkeiden nimiöt merkitään myös lihavoiduiksi.

=== Kursiivit ===

* Kursivointia käytetään painottamiseen kuten tehdään ei-teknisessä kirjoittamisessa
* Käytä kursiivia epätavallisen sanan tai fraasin ensimmäisessä esiintymisessä, ja jos mahdollista, linkitä se kohteeseen #Glossary tai sanakirjasanaan.
* Kun viitataan muihin (ulkoisiin) teoksiin, otsikot kursivoidaan.

=== Yhdistetty lihavointi ja kursivointi ===

* Tätä pitäisi käyttää ainoastaan asiayhteydessä, jossa käyttäjä on korvannut tekstiä, esim.: "Uudet osoitekirjatietueesi ovat kohteessa <tt>/home/</tt>'''''user'''''<tt>/share/contacts</tt>"

{{Tip|2=Vihje|Yksinkertaistettuja määrittelyjä - käyttäjät käynnistävät ''Ohjelmia'', ohjelmat käyttävät ''komponentteja''}}

== Kohteet, jotka aiheuttavat kotoistamispulmia ==

Useat kohteet on tunnistettu ja niistä on keskusteltu, ja ehdotetut ratkaisut ovat seuraavassa kappaleessa:

* [[Typographical_Guidelines#Lists|Luetteloiden jakaminen luettavuuden vuoksi]]
* [[Typographical_Guidelines#Keeping_things_together|Muut "luettavuus" katkokset]]
* [[Typographical_Guidelines#Unbalanced_brackets|Sulkeet jakavat lohkoja]]

Nämä havaitaan tavallisesti ensimmäisen markup-merkinnän jälkeen ja saattaa olla välttämätöntä järjestää uudelleen välit ja/tai rakenne pulmien välttämiseksi.

== Lähes valmis ==


* Kirjoita lopussa olevaan yhteenvetokenttään, mitä olet tehnyt markup-muokkauksessa.
* Käytä <menuchoice>Esikatselu</menuchoice> ja lue koko työsi lävitse. Jos olet tyytyväinen, tallenna sivu.
* Käytä sivupalkin linkkiä julkaisun pyytämiseen - se ottaa sivusi, kun lisäät muokkaamasi sivun verkko-osoitteen. Linkkisi liittäminen sinne kertoo meille, että uskot sivun olevan valmis kotoistajien työskentelyä varten. Tutkimme sitä, ja jos olemme tyytyväisiä, otamme sen mukaan kotoistamiseen.


[[Category:Translator_Help]]

Translations:Edit Markup/20/fi

2012-12-23T17:06:30Z

Centerlink:

{{Warning|2=Varoitus|1=ÄLÄ KOSKAAN lisää translate-lohkotagitunnisteita (niitä, jotka näyttävät seuraavilta <nowiki>< !--T:18-- ></nowiki>). Ohjelmisto tekee kaikkien vaadittujen tagitunnisteiden käsittelyn, ja manuaaliset muutokset rikkovat järjestelmän.}}

Edit Markup/fi

2012-12-23T16:53:51Z

Centerlink:

<languages />
== Käytettävissä olevat työkalut ==


* [[Special:MyLanguage/Typographical_Guidelines]] standardisoi kotoistamisessa käytettävät markup-merkinnät, joko virallisia käsikirjoja varten (DocBook) tai muille kielille. Viittaa tähän taajaan, koska markup-merkkejä määritellään uudelleen täsmäämään kotoistajien tarpeita.


== Työnkulku vaihe 1 ==

=== Vanhan markup-merkinnän korjaaminen ===

* Tarkista, että jokaista lohkon tai alilohkon otsaketta seuraa tyhjä rivi.

* Monille sivuille on asetettu useita sisennyksiä. Tämä sisällytettiin aikaisempaan mediawiki-dokumentaatioon, mutta ei ole enää hyväksyttävää, koska se aiheuttaa pulmia muiden muotojen viennissä, joten järjestele uudelleen käyttäen vain yksittäisiä sisennyksiä. Etumerkki-luettelot voivat edelleen olla sisäkkäisiä.

* ASCII-hymiöt aiheuttavat pulmia ja ne on poistettava. Ne voidaan korvata pienikokoisilla (11px?) oxygen-kuvakkeilla. Monia muita on saatavilla Wikimedia Commons -sivustolta - lisätiedot lisätään tänne.

* Muotoa <nowiki>[[Kotoistamistyökulku]]</nowiki> olevat sisäiset linkit olisi muokattava täydelliseen muotoon, jotka näyttävät linkin, sitten näkyvän tekstin, kuten <nowiki>[[Special:myLanguage/Translation_Workflow|Kotoistamistyökulku]]</nowiki>

* Syöttötekstin näyttämiseen on käytetty monia tyylejä, mukaan lukien <nowiki><code>, <pre></nowiki> ja taulukot ja laatikot. Käyttäjän syötteeksi tarkoitetun tekstin tulisi käyttää Input-mallinnetta, <nowiki>{{Input|1=syöteteksti (voi olla useita rivejä tai yksi rivi)}}</nowiki>. Voit yhä käyttää <nowiki><code></nowiki> hyvin lyhyelle syötteelle, jos et halua tekstin esiintyvän usealla rivillä.

* Pääteikkunatulosteet ja virheilmoitusviestit on samalla tavalla merkitty vaihtelevasti. Nämä tulisi korvata Output-mallinteella, <nowiki>{{Output|1=pääteikkunatuloste}}</nowiki>

* Jokaisen sivun tulisi päättyä Category-luokkalauseeseen. Näiden on oltava standardisoituja luokkia. Luokkien nykyinen luettelo löydetään miltä tahansa kotoistajan sivulta linkitettynä [[Translation_Help_Needed|tämä kielisivu]]

* Varmista, että missään kappaleessa ei ole parittomia sulkeita. Jos löydät parittomia sulkeita, lisää puuttuvat sulkeet — mahdollisesti kommenteissa kuten tämä: {{Input|1=<nowiki> a)</nowiki>}}

* Luetteloissa pitäisi olla etumerkkirivien välissä tyhjä rivi. Katso kappeleita luetteloissa [[Special:myLanguage/Toolbox#Bulleted Lists|Etumerkilliset luettelot]].

* Taulukot pitäisi jakaa samalla tavalla niin että jokaisen rivin välissä on tyhjä rivi. Ensimmäisellä ja viimeisellä rivillä on oltava parilliset aaltosulkeet.

== Vaihe 2 - Opas uuteen markup-merkintään ==

=== Merkitään linkit kotoistamiseen ===

* Yksittäisen linkin, sellaisen kuin sovelluksen nimi kohteessa Applications/Internet, pitäisi käyttää muotoa <nowiki>[[Special:myLanguage/Ark|<translate>Ark</translate>]]</nowiki>
* Siellä missä linkki on lauseen sisällä, koko linkki pitäisi pitää kotoistettavan viestin sisällä.

=== Erityistunnisteet ===

* Tunnista kaikki näppäimistön näppäinnimet, ja tagitunnisteet, esim.: <nowiki><keycap>Enter</keycap></nowiki>
* Sisällytä samanaikaisen näppäinten painallukset <nowiki><keycap></nowiki> -tagitunniste, esim.: <keycap>Ctrl + Alt + F1</keycap>. Huomaa, että erotin on (välilyönti)+(välilyönti)
* Kohtele valikkosarjoja samalla tavalla käyttäen <nowiki><menuchoice></nowiki> -tagitunnistetta, esim.: <menuchoice>System Settings -> Account Details -> Social Desktop</menuchoice>. Huomaa, että erotin on (välilyönti)->(välilyönti)

{{Warning|2=Varoitus|ÄLÄ KOSKAAN lisää translate-lohkotagitunnisteita (niitä, jotka näyttävät seuraavilta <nowiki>< !--T:18-- ></nowiki>). Ohjelmisto tekee kaikkien vaadittujen tagitunnisteiden käsittelyn, ja manuaaliset muutokset rikkovat järjestelmän.}}

=== Lihavoidut ===

* Tunnista ohjelmanimet ja merkitse ne lihavoituna, esim.: '''Klipper'''
* Tunnista nimiöt ja nimet, joita käyttäjä ei voi muuttaa, ja merkitse ne lihavoiduiksi.
* Poista kaikki aikaisemmat lihavoinnit, jotka on kirjoitettu aiemmin, mutta jotka eivät täsmää tähän ohjeeseen. (Katso alle sanan tai fraasin painottamisesta.)
* Ikkunan otsikkotekstit ja kuvakkeiden nimiöt merkitään myös lihavoiduiksi.

=== Kursiivit ===

* Kursivointia käytetään painottamiseen kuten tehdään ei-teknisessä kirjoittamisessa
* Käytä kursiivia epätavallisen sanan tai fraasin ensimmäisessä esiintymisessä, ja jos mahdollista, linkitä se kohteeseen #Glossary tai sanakirjasanaan.
* Kun viitataan muihin (ulkoisiin) teoksiin, otsikot kursivoidaan.

=== Yhdistetty lihavointi ja kursivointi ===

* Tätä pitäisi käyttää ainoastaan asiayhteydessä, jossa käyttäjä on korvannut tekstiä, esim.: "Uudet osoitekirjatietueesi ovat kohteessa <tt>/home/</tt>'''''user'''''<tt>/share/contacts</tt>"

{{Tip|2=Vihje|Yksinkertaistettuja määrittelyjä - käyttäjät käynnistävät ''Ohjelmia'', ohjelmat käyttävät ''komponentteja''}}

== Kohteet, jotka aiheuttavat kotoistamispulmia ==

Useat kohteet on tunnistettu ja niistä on keskusteltu, ja ehdotetut ratkaisut ovat seuraavassa kappaleessa:

* [[Typographical_Guidelines#Lists|Luetteloiden jakaminen luettavuuden vuoksi]]
* [[Typographical_Guidelines#Keeping_things_together|Muut "luettavuus" katkokset]]
* [[Typographical_Guidelines#Unbalanced_brackets|Sulkeet jakavat lohkoja]]

Nämä havaitaan tavallisesti ensimmäisen markup-merkinnän jälkeen ja saattaa olla välttämätöntä järjestää uudelleen välit ja/tai rakenne pulmien välttämiseksi.

== Lähes valmis ==


* Kirjoita lopussa olevaan yhteenvetokenttään, mitä olet tehnyt markup-muokkauksessa.
* Käytä <menuchoice>Esikatselu</menuchoice> ja lue koko työsi lävitse. Jos olet tyytyväinen, tallenna sivu.
* Käytä sivupalkin linkkiä julkaisun pyytämiseen - se ottaa sivusi, kun lisäät muokkaamasi sivun verkko-osoitteen. Linkkisi liittäminen sinne kertoo meille, että uskot sivun olevan valmis kotoistajien työskentelyä varten. Tutkimme sitä, ja jos olemme tyytyväisiä, otamme sen mukaan kotoistamiseen.


[[Category:Translator_Help]]

Translations:Edit Markup/8/fi

2012-12-23T16:53:51Z

Centerlink:

* Muotoa <nowiki>[[Kotoistamistyökulku]]</nowiki> olevat sisäiset linkit olisi muokattava täydelliseen muotoon, jotka näyttävät linkin, sitten näkyvän tekstin, kuten <nowiki>[[Special:myLanguage/Translation_Workflow|Kotoistamistyökulku]]</nowiki>

Translate a Page/fi

2012-12-23T15:58:43Z

Centerlink:

<languages />

== Käytettävissä olevat työkalut ==

* [[Special:myLanguage/Translation Workflow|Kotoistamistyön kulku]] kuvaa työkulun siirryttäessä uuteen kotoistamisjärjestelmään

== Työnkulku ==

* Pyyntö lisäämisestä kotoistamisryhmään:
** Napsauta kohdetta [[Special:myLanguage/Translator Account|Hae kotoistajatili]] sivupalkissa
** Napsauta <menuchoice>Muokkaa</menuchoice>-kuvaketta [[Image:Userbase-edit.png|14px]] ja kirjoita käyttäjänimesi, kieli, jolle haluat kotoistaa ja aiotko kotoistaa tekstiä erillistiedostoissa
** Käytä <menuchoice>Tallenna sivu</menuchoice> tietojen tallentamiseksi

* Kun käyttäjätilisi on lisätty ryhmään (sinun pitäisi saada siitä ilmoitus), napsauta kohdetta [[Special:LanguageStats|Aloita kotoistaminen]] sivupalkissa

* Kirjoita se kieli, jolle haluat kotoistaa <menuchoice>Kielikoodi</menuchoice>-valintaan ja napsauta kohdetta <menuchoice>Siirry</menuchoice>

{{Note|2=Huomaa|Kielikoodin ''en'' (englanti) kirjoittaminen kielikoodivalintaan ei näytä yhtään kotoistusviestiä, koska kaikki alkuperäinen sisältö on kirjoitettu englanniksi.}}

* Napsauta luettelossa sivua, jonka haluat kotoistaa

* Aseta '''Kotoista sivu''' asetuksessa <menuchoice>Katso kaikki kotoistamattomat viestit</menuchoice> ensimmäisessä pudotusvalikkoluettelossa

* Tarkista, että näkyvissä on oikea kielikoodi

* <menuchoice>Navigointi</menuchoice>-osassa napsauta linkkiä sen viestin vasemmalla puolella, jonka haluat kotoistaa

* Kirjoita kotoistamisteksti - Google-ehdotus tarjotaan viitteenä, mutta oma kotoistamisteksti on tavallisesti parempi.

* Napsauta kohdetta <menuchoice>Tallenna ja avaa seuraava</menuchoice>, jos haluat jatkaa seuraavaan viestiin tai <menuchoice>Tallenna sivu</menuchoice> kotoistamistekstin tallentamiseksi, jos haluat lopettaa työskentelyn.

{{Warning|2=Varoitus|Älä luo kotoistettua sivuavarianttia manuaalisesti (kirjoittamalla sivunimen/kielikoodin ja yrittämällä kotoistaa alkuperäistekstin). Tämä sotkee kotoistamisjärjestelmän ja yhtään suomennosta ei näytetä.}}

== Vihjeitä ==

=== Kuvan näyttämisohjeita ===

Tyypillinen esimerkki on <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. Tämä on koko järjestelmäkäsky kuvan näyttämiseksi. Mitään siitä ei kotoisteta.

=== Luokkaohjeet ===

Ajattele tässä asiayhteydessä sanaa "Category" järjestelmäsanana, jota ei siksi pitäisi kotoistaa. Esimerkiksi, <nowiki>[[Category:Administration]]</nowiki> tulisi <nowiki>[[Category:Administrasi/id]]</nowiki>

Johdonmukaisuuden vuoksi UserBase:ssa on hyväksyttyjen kotoistamisien luettelot. Kotoistamisryhmät saattavat havaita samanlaiset luettelot hyödyllisiksi. Sellaisia taulukkoja voidaan nähdä osoitteessa [{{UB}}Translation_Help_Needed Kotoistamisapua tarvitaan]. Pyydä apua, jos tarvitset sitä.

=== Linkit muille sivuille TechBase-sivustolla ===

Nämä ovat muodoltaan <nowiki>[[Special:myLanguage/Other page|linkkiteksti]]</nowiki> Linkki pitäisi jättää kotoistamatta, kun taas linkin teksti on aina kotoistettava. Ellei linkin teksti on läsnä, lisätään sopiva (kotoistettu) linkin teksti.

{{Note|2=Huomaa:|"myLanguage" yrittää ladata linkin kotoistetun version kielellä, jonka olet asettanut omiin asetuksiisi. Jos lataaminen epäonnistuu, se lataa vain englanninkielisen alkuperäistekstin, joten on turvallista käyttää sitä kaikissa sisäisissä linkeissä.}}

=== Linkit ulkopuolisille sivustoille ===

Nämä saavat muodon <nowiki>[http://example.com linkkiteksti]</nowiki>. Kuten sisäisissä linkeissä, säilytä varsinainen linkki ja kotoista linkkiteksti.

=== Linkit sivupalkissa ===

Ohjeita sivupalkkilinkkien kotoistamiseen löytyy osoitteesta [[Modifying_the_Sidebar#Translating_Sidebar_Items]]

=== Tietolaatikot ===

Nämä yleensä koostuvat otsakesanasta "Information" ja muokattavasta tietotekstistä. Jos sana "Information" ei ole tunnistettavissa kielelläsi, saatat tarvita kotoistetun version mallinteesta. Kysy, jos tarvitset apua tämän kanssa.

=== Kotoistetut yksiköt on merkitty sumeana ===

Joskus saattaa tapahtua, että sinun on kotoistettava sivu, mutta kotoistaminen on merkitty vaillinaiseksi. Tietyt virheet alkuperäissivun merkkauskielen merkeissä voivat aiheuttaa tämän. Yleisin virhetyyppi on parittomat sulkumerkit tai lainausmerkit. Kotoistamisjärjestelmä vaatii, että kaikilla avaavilla sulkumerkeillä ('[', '{' tai '(' ) on täsmäävä sulkeva sulkumerkki (']', '}' tai ')' ) samassa kotoistamisyksikössä, muutoin kotoistamista pidetään vaillinaisena.

Sama sääntö ei ole pakollinen wiki-ohjelmistossa, joten kirjoittajat helposti sortuvat noihin virheisiin. Jos sulkumerkki yksinkertaisesti puuttuu, niin lisää se. Joskus sulkumerkkien sisään suljettu sisältö ulottuu useampaan kuin yhteen kotoistamisyksikköön, joten täsmäävä sulkeva lainausmerkki on myöhemmässä yksikössä. Tässä tapauksessa tarvitset parilliset lainausmerkit molemmissa yksiköissä, mutta et voi yksinkertaisesti lisätä sulkumerkkejä muuttamatta muotoilun merkitystä, joten sinun on kommentoitava piiloon lisätyt sulkumerkit, kuten tämä

{{Input|1=<nowiki>{{Info|1=Pitkän tietolaatikon alku... </nowiki>}}

ja myöhemmässä yksikössä

{{Input|1=<nowiki> ...pitkän tietolaatikon loppu}}</nowiki>}}

Jos rikkova sulkumerkki on osa hymiötä, korvaa se emoticon-kuvakkeella. Vakiohymiötä varten :-) voit käyttää mallinetta <nowiki>{{Smiley}}</nowiki>

Korjaa myös alkuperäissivu, jotta muilla kotoistajilla ei ole sama pulma, tai jätä viesti keskustelusivulle.

=== Kielitilastojen epäjohdonmukaisuuksia ===

Saatat havaita lievää epäjohdonmukaisuutta LanguageStats-sivulla osoitetuissa prosenttiluvuissa ja kielipalkin prosenttiluvuissa. Tämä on normaalia. LanguageStats vertaa vain niiden viestien lukumäärää, jotka ovat kotoistamattomia tai vanhentuneita. Kielipalkkitilasto yrittää olla älykkäämpi. Esimerkiksi yhdellä sivulla (100 viestiä) 8:ssa viestissä oli pieni (uudelleen-lajittelun-aiheuttama) muutos. Jokaisessa tapauksessa kyse oli yksittäisestä sanasta. Kahdessa tilastossa on 8% ero, koska se oli viestien oleellinen osa, mutta pieni osa koko kokoistamisesta.

=== Jos käytät Chromium- tai Chrome-selainta... ===

Ole tietoinen, että Chromium-selaimessa on jonkinlainen välimuistipulma. Olen huomannut, että jopa pakotetuilla virkistyksillä jotkut tilastot eivät näy kuten niiden pitäisi näkyä (olen nähnyt vaikutuksia myös muissa asioissa), vaikka sama sivu Firefox-selaimessa avattuna näyttää tilastot oikein.

== Katso myös ==


* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]


[[Category:Translator_Help]]

Translations:Translate a Page/23/fi

2012-12-23T15:58:43Z

Centerlink:

{{Note|2=Huomaa:|"myLanguage" yrittää ladata linkin kotoistetun version kielellä, jonka olet asettanut omiin asetuksiisi. Jos lataaminen epäonnistuu, se lataa vain englanninkielisen alkuperäistekstin, joten on turvallista käyttää sitä kaikissa sisäisissä linkeissä.}}

Translations:Translate a Page/23/fi

2012-12-23T15:57:38Z

Centerlink:

{{2=Huomaa:|"myLanguage" yrittää ladata linkin kotoistetun version kielellä, jonka olet asettanut omiin asetuksiisi. Jos lataaminen epäonnistuu, se lataa vain englanninkielisen alkuperäistekstin, joten on turvallista käyttää sitä kaikissa sisäisissä linkeissä.}}

Translate a Page/fi

2012-12-23T15:57:38Z

Centerlink:

<languages />

== Käytettävissä olevat työkalut ==

* [[Special:myLanguage/Translation Workflow|Kotoistamistyön kulku]] kuvaa työkulun siirryttäessä uuteen kotoistamisjärjestelmään

== Työnkulku ==

* Pyyntö lisäämisestä kotoistamisryhmään:
** Napsauta kohdetta [[Special:myLanguage/Translator Account|Hae kotoistajatili]] sivupalkissa
** Napsauta <menuchoice>Muokkaa</menuchoice>-kuvaketta [[Image:Userbase-edit.png|14px]] ja kirjoita käyttäjänimesi, kieli, jolle haluat kotoistaa ja aiotko kotoistaa tekstiä erillistiedostoissa
** Käytä <menuchoice>Tallenna sivu</menuchoice> tietojen tallentamiseksi

* Kun käyttäjätilisi on lisätty ryhmään (sinun pitäisi saada siitä ilmoitus), napsauta kohdetta [[Special:LanguageStats|Aloita kotoistaminen]] sivupalkissa

* Kirjoita se kieli, jolle haluat kotoistaa <menuchoice>Kielikoodi</menuchoice>-valintaan ja napsauta kohdetta <menuchoice>Siirry</menuchoice>

{{Note|2=Huomaa|Kielikoodin ''en'' (englanti) kirjoittaminen kielikoodivalintaan ei näytä yhtään kotoistusviestiä, koska kaikki alkuperäinen sisältö on kirjoitettu englanniksi.}}

* Napsauta luettelossa sivua, jonka haluat kotoistaa

* Aseta '''Kotoista sivu''' asetuksessa <menuchoice>Katso kaikki kotoistamattomat viestit</menuchoice> ensimmäisessä pudotusvalikkoluettelossa

* Tarkista, että näkyvissä on oikea kielikoodi

* <menuchoice>Navigointi</menuchoice>-osassa napsauta linkkiä sen viestin vasemmalla puolella, jonka haluat kotoistaa

* Kirjoita kotoistamisteksti - Google-ehdotus tarjotaan viitteenä, mutta oma kotoistamisteksti on tavallisesti parempi.

* Napsauta kohdetta <menuchoice>Tallenna ja avaa seuraava</menuchoice>, jos haluat jatkaa seuraavaan viestiin tai <menuchoice>Tallenna sivu</menuchoice> kotoistamistekstin tallentamiseksi, jos haluat lopettaa työskentelyn.

{{Warning|2=Varoitus|Älä luo kotoistettua sivuavarianttia manuaalisesti (kirjoittamalla sivunimen/kielikoodin ja yrittämällä kotoistaa alkuperäistekstin). Tämä sotkee kotoistamisjärjestelmän ja yhtään suomennosta ei näytetä.}}

== Vihjeitä ==

=== Kuvan näyttämisohjeita ===

Tyypillinen esimerkki on <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. Tämä on koko järjestelmäkäsky kuvan näyttämiseksi. Mitään siitä ei kotoisteta.

=== Luokkaohjeet ===

Ajattele tässä asiayhteydessä sanaa "Category" järjestelmäsanana, jota ei siksi pitäisi kotoistaa. Esimerkiksi, <nowiki>[[Category:Administration]]</nowiki> tulisi <nowiki>[[Category:Administrasi/id]]</nowiki>

Johdonmukaisuuden vuoksi UserBase:ssa on hyväksyttyjen kotoistamisien luettelot. Kotoistamisryhmät saattavat havaita samanlaiset luettelot hyödyllisiksi. Sellaisia taulukkoja voidaan nähdä osoitteessa [{{UB}}Translation_Help_Needed Kotoistamisapua tarvitaan]. Pyydä apua, jos tarvitset sitä.

=== Linkit muille sivuille TechBase-sivustolla ===

Nämä ovat muodoltaan <nowiki>[[Special:myLanguage/Other page|linkkiteksti]]</nowiki> Linkki pitäisi jättää kotoistamatta, kun taas linkin teksti on aina kotoistettava. Ellei linkin teksti on läsnä, lisätään sopiva (kotoistettu) linkin teksti.

{{2=Huomaa:|"myLanguage" yrittää ladata linkin kotoistetun version kielellä, jonka olet asettanut omiin asetuksiisi. Jos lataaminen epäonnistuu, se lataa vain englanninkielisen alkuperäistekstin, joten on turvallista käyttää sitä kaikissa sisäisissä linkeissä.}}

=== Linkit ulkopuolisille sivustoille ===

Nämä saavat muodon <nowiki>[http://example.com linkkiteksti]</nowiki>. Kuten sisäisissä linkeissä, säilytä varsinainen linkki ja kotoista linkkiteksti.

=== Linkit sivupalkissa ===

Ohjeita sivupalkkilinkkien kotoistamiseen löytyy osoitteesta [[Modifying_the_Sidebar#Translating_Sidebar_Items]]

=== Tietolaatikot ===

Nämä yleensä koostuvat otsakesanasta "Information" ja muokattavasta tietotekstistä. Jos sana "Information" ei ole tunnistettavissa kielelläsi, saatat tarvita kotoistetun version mallinteesta. Kysy, jos tarvitset apua tämän kanssa.

=== Kotoistetut yksiköt on merkitty sumeana ===

Joskus saattaa tapahtua, että sinun on kotoistettava sivu, mutta kotoistaminen on merkitty vaillinaiseksi. Tietyt virheet alkuperäissivun merkkauskielen merkeissä voivat aiheuttaa tämän. Yleisin virhetyyppi on parittomat sulkumerkit tai lainausmerkit. Kotoistamisjärjestelmä vaatii, että kaikilla avaavilla sulkumerkeillä ('[', '{' tai '(' ) on täsmäävä sulkeva sulkumerkki (']', '}' tai ')' ) samassa kotoistamisyksikössä, muutoin kotoistamista pidetään vaillinaisena.

Sama sääntö ei ole pakollinen wiki-ohjelmistossa, joten kirjoittajat helposti sortuvat noihin virheisiin. Jos sulkumerkki yksinkertaisesti puuttuu, niin lisää se. Joskus sulkumerkkien sisään suljettu sisältö ulottuu useampaan kuin yhteen kotoistamisyksikköön, joten täsmäävä sulkeva lainausmerkki on myöhemmässä yksikössä. Tässä tapauksessa tarvitset parilliset lainausmerkit molemmissa yksiköissä, mutta et voi yksinkertaisesti lisätä sulkumerkkejä muuttamatta muotoilun merkitystä, joten sinun on kommentoitava piiloon lisätyt sulkumerkit, kuten tämä

{{Input|1=<nowiki>{{Info|1=Pitkän tietolaatikon alku... </nowiki>}}

ja myöhemmässä yksikössä

{{Input|1=<nowiki> ...pitkän tietolaatikon loppu}}</nowiki>}}

Jos rikkova sulkumerkki on osa hymiötä, korvaa se emoticon-kuvakkeella. Vakiohymiötä varten :-) voit käyttää mallinetta <nowiki>{{Smiley}}</nowiki>

Korjaa myös alkuperäissivu, jotta muilla kotoistajilla ei ole sama pulma, tai jätä viesti keskustelusivulle.

=== Kielitilastojen epäjohdonmukaisuuksia ===

Saatat havaita lievää epäjohdonmukaisuutta LanguageStats-sivulla osoitetuissa prosenttiluvuissa ja kielipalkin prosenttiluvuissa. Tämä on normaalia. LanguageStats vertaa vain niiden viestien lukumäärää, jotka ovat kotoistamattomia tai vanhentuneita. Kielipalkkitilasto yrittää olla älykkäämpi. Esimerkiksi yhdellä sivulla (100 viestiä) 8:ssa viestissä oli pieni (uudelleen-lajittelun-aiheuttama) muutos. Jokaisessa tapauksessa kyse oli yksittäisestä sanasta. Kahdessa tilastossa on 8% ero, koska se oli viestien oleellinen osa, mutta pieni osa koko kokoistamisesta.

=== Jos käytät Chromium- tai Chrome-selainta... ===

Ole tietoinen, että Chromium-selaimessa on jonkinlainen välimuistipulma. Olen huomannut, että jopa pakotetuilla virkistyksillä jotkut tilastot eivät näy kuten niiden pitäisi näkyä (olen nähnyt vaikutuksia myös muissa asioissa), vaikka sama sivu Firefox-selaimessa avattuna näyttää tilastot oikein.

== Katso myös ==


* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]


[[Category:Translator_Help]]

Translate a Page/fi

2012-12-23T15:55:15Z

Centerlink:

<languages />

== Käytettävissä olevat työkalut ==

* [[Special:myLanguage/Translation Workflow|Kotoistamistyön kulku]] kuvaa työkulun siirryttäessä uuteen kotoistamisjärjestelmään

== Työnkulku ==

* Pyyntö lisäämisestä kotoistamisryhmään:
** Napsauta kohdetta [[Special:myLanguage/Translator Account|Hae kotoistajatili]] sivupalkissa
** Napsauta <menuchoice>Muokkaa</menuchoice>-kuvaketta [[Image:Userbase-edit.png|14px]] ja kirjoita käyttäjänimesi, kieli, jolle haluat kotoistaa ja aiotko kotoistaa tekstiä erillistiedostoissa
** Käytä <menuchoice>Tallenna sivu</menuchoice> tietojen tallentamiseksi

* Kun käyttäjätilisi on lisätty ryhmään (sinun pitäisi saada siitä ilmoitus), napsauta kohdetta [[Special:LanguageStats|Aloita kotoistaminen]] sivupalkissa

* Kirjoita se kieli, jolle haluat kotoistaa <menuchoice>Kielikoodi</menuchoice>-valintaan ja napsauta kohdetta <menuchoice>Siirry</menuchoice>

{{Note|2=Huomaa|Kielikoodin ''en'' (englanti) kirjoittaminen kielikoodivalintaan ei näytä yhtään kotoistusviestiä, koska kaikki alkuperäinen sisältö on kirjoitettu englanniksi.}}

* Napsauta luettelossa sivua, jonka haluat kotoistaa

* Aseta '''Kotoista sivu''' asetuksessa <menuchoice>Katso kaikki kotoistamattomat viestit</menuchoice> ensimmäisessä pudotusvalikkoluettelossa

* Tarkista, että näkyvissä on oikea kielikoodi

* <menuchoice>Navigointi</menuchoice>-osassa napsauta linkkiä sen viestin vasemmalla puolella, jonka haluat kotoistaa

* Kirjoita kotoistamisteksti - Google-ehdotus tarjotaan viitteenä, mutta oma kotoistamisteksti on tavallisesti parempi.

* Napsauta kohdetta <menuchoice>Tallenna ja avaa seuraava</menuchoice>, jos haluat jatkaa seuraavaan viestiin tai <menuchoice>Tallenna sivu</menuchoice> kotoistamistekstin tallentamiseksi, jos haluat lopettaa työskentelyn.

{{Warning|2=Varoitus|Älä luo kotoistettua sivuavarianttia manuaalisesti (kirjoittamalla sivunimen/kielikoodin ja yrittämällä kotoistaa alkuperäistekstin). Tämä sotkee kotoistamisjärjestelmän ja yhtään suomennosta ei näytetä.}}

== Vihjeitä ==

=== Kuvan näyttämisohjeita ===

Tyypillinen esimerkki on <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. Tämä on koko järjestelmäkäsky kuvan näyttämiseksi. Mitään siitä ei kotoisteta.

=== Luokkaohjeet ===

Ajattele tässä asiayhteydessä sanaa "Category" järjestelmäsanana, jota ei siksi pitäisi kotoistaa. Esimerkiksi, <nowiki>[[Category:Administration]]</nowiki> tulisi <nowiki>[[Category:Administrasi/id]]</nowiki>

Johdonmukaisuuden vuoksi UserBase:ssa on hyväksyttyjen kotoistamisien luettelot. Kotoistamisryhmät saattavat havaita samanlaiset luettelot hyödyllisiksi. Sellaisia taulukkoja voidaan nähdä osoitteessa [{{UB}}Translation_Help_Needed Kotoistamisapua tarvitaan]. Pyydä apua, jos tarvitset sitä.

=== Linkit muille sivuille TechBase-sivustolla ===

Nämä ovat muodoltaan <nowiki>[[Special:myLanguage/Other page|linkkiteksti]]</nowiki> Linkki pitäisi jättää kotoistamatta, kun taas linkin teksti on aina kotoistettava. Ellei linkin teksti on läsnä, lisätään sopiva (kotoistettu) linkin teksti.


Huomaa: "myLanguage" yrittää ladata linkin kotoistetun version kielellä, jonka olet asettanut omiin asetuksiisi. Jos lataaminen epäonnistuu, se lataa vain englanninkielisen alkuperäistekstin, joten on turvallista käyttää sitä kaikissa sisäisissä linkeissä.


=== Linkit ulkopuolisille sivustoille ===

Nämä saavat muodon <nowiki>[http://example.com linkkiteksti]</nowiki>. Kuten sisäisissä linkeissä, säilytä varsinainen linkki ja kotoista linkkiteksti.

=== Linkit sivupalkissa ===

Ohjeita sivupalkkilinkkien kotoistamiseen löytyy osoitteesta [[Modifying_the_Sidebar#Translating_Sidebar_Items]]

=== Tietolaatikot ===

Nämä yleensä koostuvat otsakesanasta "Information" ja muokattavasta tietotekstistä. Jos sana "Information" ei ole tunnistettavissa kielelläsi, saatat tarvita kotoistetun version mallinteesta. Kysy, jos tarvitset apua tämän kanssa.

=== Kotoistetut yksiköt on merkitty sumeana ===

Joskus saattaa tapahtua, että sinun on kotoistettava sivu, mutta kotoistaminen on merkitty vaillinaiseksi. Tietyt virheet alkuperäissivun merkkauskielen merkeissä voivat aiheuttaa tämän. Yleisin virhetyyppi on parittomat sulkumerkit tai lainausmerkit. Kotoistamisjärjestelmä vaatii, että kaikilla avaavilla sulkumerkeillä ('[', '{' tai '(' ) on täsmäävä sulkeva sulkumerkki (']', '}' tai ')' ) samassa kotoistamisyksikössä, muutoin kotoistamista pidetään vaillinaisena.

Sama sääntö ei ole pakollinen wiki-ohjelmistossa, joten kirjoittajat helposti sortuvat noihin virheisiin. Jos sulkumerkki yksinkertaisesti puuttuu, niin lisää se. Joskus sulkumerkkien sisään suljettu sisältö ulottuu useampaan kuin yhteen kotoistamisyksikköön, joten täsmäävä sulkeva lainausmerkki on myöhemmässä yksikössä. Tässä tapauksessa tarvitset parilliset lainausmerkit molemmissa yksiköissä, mutta et voi yksinkertaisesti lisätä sulkumerkkejä muuttamatta muotoilun merkitystä, joten sinun on kommentoitava piiloon lisätyt sulkumerkit, kuten tämä

{{Input|1=<nowiki>{{Info|1=Pitkän tietolaatikon alku... </nowiki>}}

ja myöhemmässä yksikössä

{{Input|1=<nowiki> ...pitkän tietolaatikon loppu}}</nowiki>}}

Jos rikkova sulkumerkki on osa hymiötä, korvaa se emoticon-kuvakkeella. Vakiohymiötä varten :-) voit käyttää mallinetta <nowiki>{{Smiley}}</nowiki>

Korjaa myös alkuperäissivu, jotta muilla kotoistajilla ei ole sama pulma, tai jätä viesti keskustelusivulle.

=== Kielitilastojen epäjohdonmukaisuuksia ===

Saatat havaita lievää epäjohdonmukaisuutta LanguageStats-sivulla osoitetuissa prosenttiluvuissa ja kielipalkin prosenttiluvuissa. Tämä on normaalia. LanguageStats vertaa vain niiden viestien lukumäärää, jotka ovat kotoistamattomia tai vanhentuneita. Kielipalkkitilasto yrittää olla älykkäämpi. Esimerkiksi yhdellä sivulla (100 viestiä) 8:ssa viestissä oli pieni (uudelleen-lajittelun-aiheuttama) muutos. Jokaisessa tapauksessa kyse oli yksittäisestä sanasta. Kahdessa tilastossa on 8% ero, koska se oli viestien oleellinen osa, mutta pieni osa koko kokoistamisesta.

=== Jos käytät Chromium- tai Chrome-selainta... ===

Ole tietoinen, että Chromium-selaimessa on jonkinlainen välimuistipulma. Olen huomannut, että jopa pakotetuilla virkistyksillä jotkut tilastot eivät näy kuten niiden pitäisi näkyä (olen nähnyt vaikutuksia myös muissa asioissa), vaikka sama sivu Firefox-selaimessa avattuna näyttää tilastot oikein.

== Katso myös ==


* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]


[[Category:Translator_Help]]

Translate a Page/fi

2012-12-23T15:49:08Z

Centerlink:

<languages />

== Käytettävissä olevat työkalut ==

* [[Special:myLanguage/Translation Workflow|Kotoistamistyön kulku]] kuvaa työkulun siirryttäessä uuteen kotoistamisjärjestelmään

== Työnkulku ==

* Pyyntö lisäämisestä kotoistamisryhmään:
** Napsauta kohdetta [[Special:myLanguage/Translator Account|Hae kotoistajatili]] sivupalkissa
** Napsauta <menuchoice>Muokkaa</menuchoice>-kuvaketta [[Image:Userbase-edit.png|14px]] ja kirjoita käyttäjänimesi, kieli, jolle haluat kotoistaa ja aiotko kotoistaa tekstiä erillistiedostoissa
** Käytä <menuchoice>Tallenna sivu</menuchoice> tietojen tallentamiseksi

* Kun käyttäjätilisi on lisätty ryhmään (sinun pitäisi saada siitä ilmoitus), napsauta kohdetta [[Special:LanguageStats|Aloita kotoistaminen]] sivupalkissa

* Kirjoita se kieli, jolle haluat kotoistaa <menuchoice>Kielikoodi</menuchoice>-valintaan ja napsauta kohdetta <menuchoice>Siirry</menuchoice>

{{Note|2=Huomaa|Kielikoodin ''en'' (englanti) kirjoittaminen kielikoodivalintaan ei näytä yhtään kotoistusviestiä, koska kaikki alkuperäinen sisältö on kirjoitettu englanniksi.}}

* Napsauta luettelossa sivua, jonka haluat kotoistaa

* Aseta '''Kotoista sivu''' asetuksessa <menuchoice>Katso kaikki kotoistamattomat viestit</menuchoice> ensimmäisessä pudotusvalikkoluettelossa

* Tarkista, että näkyvissä on oikea kielikoodi

* <menuchoice>Navigointi</menuchoice>-osassa napsauta linkkiä sen viestin vasemmalla puolella, jonka haluat kotoistaa

* Kirjoita kotoistamisteksti - Google-ehdotus tarjotaan viitteenä, mutta oma kotoistamisteksti on tavallisesti parempi.

* Napsauta kohdetta <menuchoice>Tallenna ja avaa seuraava</menuchoice>, jos haluat jatkaa seuraavaan viestiin tai <menuchoice>Tallenna sivu</menuchoice> kotoistamistekstin tallentamiseksi, jos haluat lopettaa työskentelyn.

{{Warning|2=Varoitus|Älä luo kotoistettua sivuavarianttia manuaalisesti (kirjoittamalla sivunimen/kielikoodin ja yrittämällä kotoistaa alkuperäistekstin). Tämä sotkee kotoistamisjärjestelmän ja yhtään suomennosta ei näytetä.}}

== Vihjeitä ==

=== Kuvan näyttämisohjeita ===

Tyypillinen esimerkki on <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. Tämä on koko järjestelmäkäsky kuvan näyttämiseksi. Mitään siitä ei kotoisteta.

=== Luokkaohjeet ===

Ajattele tässä asiayhteydessä sanaa "Category" järjestelmäsanana, jota ei siksi pitäisi kotoistaa. Esimerkiksi, <nowiki>[[Category:Administration]]</nowiki> tulisi <nowiki>[[Category:Administrasi/id]]</nowiki>


Johdonmukaisuuden vuoksi UserBase:ssa on hyväksyttyjen kotoistamisien luettelot. Kotoistamisryhmät saattavat havaita samanlaiset luettelot hyödyllisiksi. Sellaisia taulukkoja voidaan nähdä osoitteessa [{{UB}}Translation_Help_Needed Kotoistamisapua tarvitaan]. Pyydä apua, jos tarvitset sitä.


=== Linkit muille sivuille TechBase-sivustolla ===

Nämä ovat muodoltaan <nowiki>[[Special:myLanguage/Other page|linkkiteksti]]</nowiki> Linkki pitäisi jättää kotoistamatta, kun taas linkin teksti on aina kotoistettava. Ellei linkin teksti on läsnä, lisätään sopiva (kotoistettu) linkin teksti.


Huomaa: "myLanguage" yrittää ladata linkin kotoistetun version kielellä, jonka olet asettanut omiin asetuksiisi. Jos lataaminen epäonnistuu, se lataa vain englanninkielisen alkuperäistekstin, joten on turvallista käyttää sitä kaikissa sisäisissä linkeissä.


=== Linkit ulkopuolisille sivustoille ===

Nämä saavat muodon <nowiki>[http://example.com linkkiteksti]</nowiki>. Kuten sisäisissä linkeissä, säilytä varsinainen linkki ja kotoista linkkiteksti.

=== Linkit sivupalkissa ===

Ohjeita sivupalkkilinkkien kotoistamiseen löytyy osoitteesta [[Modifying_the_Sidebar#Translating_Sidebar_Items]]

=== Tietolaatikot ===

Nämä yleensä koostuvat otsakesanasta "Information" ja muokattavasta tietotekstistä. Jos sana "Information" ei ole tunnistettavissa kielelläsi, saatat tarvita kotoistetun version mallinteesta. Kysy, jos tarvitset apua tämän kanssa.

=== Kotoistetut yksiköt on merkitty sumeana ===

Joskus saattaa tapahtua, että sinun on kotoistettava sivu, mutta kotoistaminen on merkitty vaillinaiseksi. Tietyt virheet alkuperäissivun merkkauskielen merkeissä voivat aiheuttaa tämän. Yleisin virhetyyppi on parittomat sulkumerkit tai lainausmerkit. Kotoistamisjärjestelmä vaatii, että kaikilla avaavilla sulkumerkeillä ('[', '{' tai '(' ) on täsmäävä sulkeva sulkumerkki (']', '}' tai ')' ) samassa kotoistamisyksikössä, muutoin kotoistamista pidetään vaillinaisena.

Sama sääntö ei ole pakollinen wiki-ohjelmistossa, joten kirjoittajat helposti sortuvat noihin virheisiin. Jos sulkumerkki yksinkertaisesti puuttuu, niin lisää se. Joskus sulkumerkkien sisään suljettu sisältö ulottuu useampaan kuin yhteen kotoistamisyksikköön, joten täsmäävä sulkeva lainausmerkki on myöhemmässä yksikössä. Tässä tapauksessa tarvitset parilliset lainausmerkit molemmissa yksiköissä, mutta et voi yksinkertaisesti lisätä sulkumerkkejä muuttamatta muotoilun merkitystä, joten sinun on kommentoitava piiloon lisätyt sulkumerkit, kuten tämä

{{Input|1=<nowiki>{{Info|1=Pitkän tietolaatikon alku... </nowiki>}}

ja myöhemmässä yksikössä

{{Input|1=<nowiki> ...pitkän tietolaatikon loppu}}</nowiki>}}

Jos rikkova sulkumerkki on osa hymiötä, korvaa se emoticon-kuvakkeella. Vakiohymiötä varten :-) voit käyttää mallinetta <nowiki>{{Smiley}}</nowiki>

Korjaa myös alkuperäissivu, jotta muilla kotoistajilla ei ole sama pulma, tai jätä viesti keskustelusivulle.

=== Kielitilastojen epäjohdonmukaisuuksia ===

Saatat havaita lievää epäjohdonmukaisuutta LanguageStats-sivulla osoitetuissa prosenttiluvuissa ja kielipalkin prosenttiluvuissa. Tämä on normaalia. LanguageStats vertaa vain niiden viestien lukumäärää, jotka ovat kotoistamattomia tai vanhentuneita. Kielipalkkitilasto yrittää olla älykkäämpi. Esimerkiksi yhdellä sivulla (100 viestiä) 8:ssa viestissä oli pieni (uudelleen-lajittelun-aiheuttama) muutos. Jokaisessa tapauksessa kyse oli yksittäisestä sanasta. Kahdessa tilastossa on 8% ero, koska se oli viestien oleellinen osa, mutta pieni osa koko kokoistamisesta.

=== Jos käytät Chromium- tai Chrome-selainta... ===

Ole tietoinen, että Chromium-selaimessa on jonkinlainen välimuistipulma. Olen huomannut, että jopa pakotetuilla virkistyksillä jotkut tilastot eivät näy kuten niiden pitäisi näkyä (olen nähnyt vaikutuksia myös muissa asioissa), vaikka sama sivu Firefox-selaimessa avattuna näyttää tilastot oikein.

== Katso myös ==


* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]


[[Category:Translator_Help]]

Translations:Translate a Page/9/fi

2012-12-23T15:49:07Z

Centerlink:

* Aseta '''Kotoista sivu''' asetuksessa <menuchoice>Katso kaikki kotoistamattomat viestit</menuchoice> ensimmäisessä pudotusvalikkoluettelossa

Translate a Page/fi

2012-12-23T15:48:03Z

Centerlink:

<languages />

== Käytettävissä olevat työkalut ==

* [[Special:myLanguage/Translation Workflow|Kotoistamistyön kulku]] kuvaa työkulun siirryttäessä uuteen kotoistamisjärjestelmään

== Työnkulku ==

* Pyyntö lisäämisestä kotoistamisryhmään:
** Napsauta kohdetta [[Special:myLanguage/Translator Account|Hae kotoistajatili]] sivupalkissa
** Napsauta <menuchoice>Muokkaa</menuchoice>-kuvaketta [[Image:Userbase-edit.png|14px]] ja kirjoita käyttäjänimesi, kieli, jolle haluat kotoistaa ja aiotko kotoistaa tekstiä erillistiedostoissa
** Käytä <menuchoice>Tallenna sivu</menuchoice> tietojen tallentamiseksi

* Kun käyttäjätilisi on lisätty ryhmään (sinun pitäisi saada siitä ilmoitus), napsauta kohdetta [[Special:LanguageStats|Aloita kotoistaminen]] sivupalkissa

* Kirjoita se kieli, jolle haluat kotoistaa <menuchoice>Kielikoodi</menuchoice>-valintaan ja napsauta kohdetta <menuchoice>Siirry</menuchoice>

{{Note|2=Huomaa|Kielikoodin ''en'' (englanti) kirjoittaminen kielikoodivalintaan ei näytä yhtään kotoistusviestiä, koska kaikki alkuperäinen sisältö on kirjoitettu englanniksi.}}

* Napsauta luettelossa sivua, jonka haluat kotoistaa

* Aseta '''Kotoista sivu''' asetuksessa <menuchoice>Katso kaikki kotoistamattomat viestit</menuchoice> ensimmäisessä vetovalikkoluettelossa

* Tarkista, että näkyvissä on oikea kielikoodi

* <menuchoice>Navigointi</menuchoice>-osassa napsauta linkkiä sen viestin vasemmalla puolella, jonka haluat kotoistaa

* Kirjoita kotoistamisteksti - Google-ehdotus tarjotaan viitteenä, mutta oma kotoistamisteksti on tavallisesti parempi.

* Napsauta kohdetta <menuchoice>Tallenna ja avaa seuraava</menuchoice>, jos haluat jatkaa seuraavaan viestiin tai <menuchoice>Tallenna sivu</menuchoice> kotoistamistekstin tallentamiseksi, jos haluat lopettaa työskentelyn.

{{Warning|2=Varoitus|Älä luo kotoistettua sivuavarianttia manuaalisesti (kirjoittamalla sivunimen/kielikoodin ja yrittämällä kotoistaa alkuperäistekstin). Tämä sotkee kotoistamisjärjestelmän ja yhtään suomennosta ei näytetä.}}

== Vihjeitä ==

=== Kuvan näyttämisohjeita ===

Tyypillinen esimerkki on <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. Tämä on koko järjestelmäkäsky kuvan näyttämiseksi. Mitään siitä ei kotoisteta.

=== Luokkaohjeet ===

Ajattele tässä asiayhteydessä sanaa "Category" järjestelmäsanana, jota ei siksi pitäisi kotoistaa. Esimerkiksi, <nowiki>[[Category:Administration]]</nowiki> tulisi <nowiki>[[Category:Administrasi/id]]</nowiki>


Johdonmukaisuuden vuoksi UserBase:ssa on hyväksyttyjen kotoistamisien luettelot. Kotoistamisryhmät saattavat havaita samanlaiset luettelot hyödyllisiksi. Sellaisia taulukkoja voidaan nähdä osoitteessa [{{UB}}Translation_Help_Needed Kotoistamisapua tarvitaan]. Pyydä apua, jos tarvitset sitä.


=== Linkit muille sivuille TechBase-sivustolla ===

Nämä ovat muodoltaan <nowiki>[[Special:myLanguage/Other page|linkkiteksti]]</nowiki> Linkki pitäisi jättää kotoistamatta, kun taas linkin teksti on aina kotoistettava. Ellei linkin teksti on läsnä, lisätään sopiva (kotoistettu) linkin teksti.


Huomaa: "myLanguage" yrittää ladata linkin kotoistetun version kielellä, jonka olet asettanut omiin asetuksiisi. Jos lataaminen epäonnistuu, se lataa vain englanninkielisen alkuperäistekstin, joten on turvallista käyttää sitä kaikissa sisäisissä linkeissä.


=== Linkit ulkopuolisille sivustoille ===

Nämä saavat muodon <nowiki>[http://example.com linkkiteksti]</nowiki>. Kuten sisäisissä linkeissä, säilytä varsinainen linkki ja kotoista linkkiteksti.

=== Linkit sivupalkissa ===

Ohjeita sivupalkkilinkkien kotoistamiseen löytyy osoitteesta [[Modifying_the_Sidebar#Translating_Sidebar_Items]]

=== Tietolaatikot ===

Nämä yleensä koostuvat otsakesanasta "Information" ja muokattavasta tietotekstistä. Jos sana "Information" ei ole tunnistettavissa kielelläsi, saatat tarvita kotoistetun version mallinteesta. Kysy, jos tarvitset apua tämän kanssa.

=== Kotoistetut yksiköt on merkitty sumeana ===

Joskus saattaa tapahtua, että sinun on kotoistettava sivu, mutta kotoistaminen on merkitty vaillinaiseksi. Tietyt virheet alkuperäissivun merkkauskielen merkeissä voivat aiheuttaa tämän. Yleisin virhetyyppi on parittomat sulkumerkit tai lainausmerkit. Kotoistamisjärjestelmä vaatii, että kaikilla avaavilla sulkumerkeillä ('[', '{' tai '(' ) on täsmäävä sulkeva sulkumerkki (']', '}' tai ')' ) samassa kotoistamisyksikössä, muutoin kotoistamista pidetään vaillinaisena.

Sama sääntö ei ole pakollinen wiki-ohjelmistossa, joten kirjoittajat helposti sortuvat noihin virheisiin. Jos sulkumerkki yksinkertaisesti puuttuu, niin lisää se. Joskus sulkumerkkien sisään suljettu sisältö ulottuu useampaan kuin yhteen kotoistamisyksikköön, joten täsmäävä sulkeva lainausmerkki on myöhemmässä yksikössä. Tässä tapauksessa tarvitset parilliset lainausmerkit molemmissa yksiköissä, mutta et voi yksinkertaisesti lisätä sulkumerkkejä muuttamatta muotoilun merkitystä, joten sinun on kommentoitava piiloon lisätyt sulkumerkit, kuten tämä

{{Input|1=<nowiki>{{Info|1=Pitkän tietolaatikon alku... </nowiki>}}

ja myöhemmässä yksikössä

{{Input|1=<nowiki> ...pitkän tietolaatikon loppu}}</nowiki>}}

Jos rikkova sulkumerkki on osa hymiötä, korvaa se emoticon-kuvakkeella. Vakiohymiötä varten :-) voit käyttää mallinetta <nowiki>{{Smiley}}</nowiki>

Korjaa myös alkuperäissivu, jotta muilla kotoistajilla ei ole sama pulma, tai jätä viesti keskustelusivulle.

=== Kielitilastojen epäjohdonmukaisuuksia ===

Saatat havaita lievää epäjohdonmukaisuutta LanguageStats-sivulla osoitetuissa prosenttiluvuissa ja kielipalkin prosenttiluvuissa. Tämä on normaalia. LanguageStats vertaa vain niiden viestien lukumäärää, jotka ovat kotoistamattomia tai vanhentuneita. Kielipalkkitilasto yrittää olla älykkäämpi. Esimerkiksi yhdellä sivulla (100 viestiä) 8:ssa viestissä oli pieni (uudelleen-lajittelun-aiheuttama) muutos. Jokaisessa tapauksessa kyse oli yksittäisestä sanasta. Kahdessa tilastossa on 8% ero, koska se oli viestien oleellinen osa, mutta pieni osa koko kokoistamisesta.

=== Jos käytät Chromium- tai Chrome-selainta... ===

Ole tietoinen, että Chromium-selaimessa on jonkinlainen välimuistipulma. Olen huomannut, että jopa pakotetuilla virkistyksillä jotkut tilastot eivät näy kuten niiden pitäisi näkyä (olen nähnyt vaikutuksia myös muissa asioissa), vaikka sama sivu Firefox-selaimessa avattuna näyttää tilastot oikein.

== Katso myös ==


* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]


[[Category:Translator_Help]]

Translations:Translate a Page/7/fi

2012-12-23T15:48:03Z

Centerlink:

{{Note|2=Huomaa|Kielikoodin ''en'' (englanti) kirjoittaminen kielikoodivalintaan ei näytä yhtään kotoistusviestiä, koska kaikki alkuperäinen sisältö on kirjoitettu englanniksi.}}

Translate a Page/fi

2012-12-23T15:46:42Z

Centerlink:

<languages />

== Käytettävissä olevat työkalut ==

* [[Special:myLanguage/Translation Workflow|Kotoistamistyön kulku]] kuvaa työkulun siirryttäessä uuteen kotoistamisjärjestelmään

== Työnkulku ==

* Pyyntö lisäämisestä kotoistamisryhmään:
** Napsauta kohdetta [[Special:myLanguage/Translator Account|Hae kotoistajatili]] sivupalkissa
** Napsauta <menuchoice>Muokkaa</menuchoice>-kuvaketta [[Image:Userbase-edit.png|14px]] ja kirjoita käyttäjänimesi, kieli, jolle haluat kotoistaa ja aiotko kotoistaa tekstiä erillistiedostoissa
** Käytä <menuchoice>Tallenna sivu</menuchoice> tietojen tallentamiseksi

* Kun käyttäjätilisi on lisätty ryhmään (sinun pitäisi saada siitä ilmoitus), napsauta kohdetta [[Special:LanguageStats|Aloita kotoistaminen]] sivupalkissa

* Kirjoita se kieli, jolle haluat kotoistaa <menuchoice>Kielikoodi</menuchoice>-valintaan ja napsauta kohdetta <menuchoice>Siirry</menuchoice>

{{Note|Huomaa|Kielikoodin ''en'' (englanti) kirjoittaminen kielikoodivalintaan ei näytä yhtään kotoistusviestiä, koska kaikki alkuperäinen sisältö on kirjoitettu englanniksi.}}

* Napsauta luettelossa sivua, jonka haluat kotoistaa

* Aseta '''Kotoista sivu''' asetuksessa <menuchoice>Katso kaikki kotoistamattomat viestit</menuchoice> ensimmäisessä vetovalikkoluettelossa

* Tarkista, että näkyvissä on oikea kielikoodi

* <menuchoice>Navigointi</menuchoice>-osassa napsauta linkkiä sen viestin vasemmalla puolella, jonka haluat kotoistaa

* Kirjoita kotoistamisteksti - Google-ehdotus tarjotaan viitteenä, mutta oma kotoistamisteksti on tavallisesti parempi.

* Napsauta kohdetta <menuchoice>Tallenna ja avaa seuraava</menuchoice>, jos haluat jatkaa seuraavaan viestiin tai <menuchoice>Tallenna sivu</menuchoice> kotoistamistekstin tallentamiseksi, jos haluat lopettaa työskentelyn.

{{Warning|2=Varoitus|Älä luo kotoistettua sivuavarianttia manuaalisesti (kirjoittamalla sivunimen/kielikoodin ja yrittämällä kotoistaa alkuperäistekstin). Tämä sotkee kotoistamisjärjestelmän ja yhtään suomennosta ei näytetä.}}

== Vihjeitä ==

=== Kuvan näyttämisohjeita ===

Tyypillinen esimerkki on <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>. Tämä on koko järjestelmäkäsky kuvan näyttämiseksi. Mitään siitä ei kotoisteta.

=== Luokkaohjeet ===

Ajattele tässä asiayhteydessä sanaa "Category" järjestelmäsanana, jota ei siksi pitäisi kotoistaa. Esimerkiksi, <nowiki>[[Category:Administration]]</nowiki> tulisi <nowiki>[[Category:Administrasi/id]]</nowiki>


Johdonmukaisuuden vuoksi UserBase:ssa on hyväksyttyjen kotoistamisien luettelot. Kotoistamisryhmät saattavat havaita samanlaiset luettelot hyödyllisiksi. Sellaisia taulukkoja voidaan nähdä osoitteessa [{{UB}}Translation_Help_Needed Kotoistamisapua tarvitaan]. Pyydä apua, jos tarvitset sitä.


=== Linkit muille sivuille TechBase-sivustolla ===

Nämä ovat muodoltaan <nowiki>[[Special:myLanguage/Other page|linkkiteksti]]</nowiki> Linkki pitäisi jättää kotoistamatta, kun taas linkin teksti on aina kotoistettava. Ellei linkin teksti on läsnä, lisätään sopiva (kotoistettu) linkin teksti.


Huomaa: "myLanguage" yrittää ladata linkin kotoistetun version kielellä, jonka olet asettanut omiin asetuksiisi. Jos lataaminen epäonnistuu, se lataa vain englanninkielisen alkuperäistekstin, joten on turvallista käyttää sitä kaikissa sisäisissä linkeissä.


=== Linkit ulkopuolisille sivustoille ===

Nämä saavat muodon <nowiki>[http://example.com linkkiteksti]</nowiki>. Kuten sisäisissä linkeissä, säilytä varsinainen linkki ja kotoista linkkiteksti.

=== Linkit sivupalkissa ===

Ohjeita sivupalkkilinkkien kotoistamiseen löytyy osoitteesta [[Modifying_the_Sidebar#Translating_Sidebar_Items]]

=== Tietolaatikot ===

Nämä yleensä koostuvat otsakesanasta "Information" ja muokattavasta tietotekstistä. Jos sana "Information" ei ole tunnistettavissa kielelläsi, saatat tarvita kotoistetun version mallinteesta. Kysy, jos tarvitset apua tämän kanssa.

=== Kotoistetut yksiköt on merkitty sumeana ===

Joskus saattaa tapahtua, että sinun on kotoistettava sivu, mutta kotoistaminen on merkitty vaillinaiseksi. Tietyt virheet alkuperäissivun merkkauskielen merkeissä voivat aiheuttaa tämän. Yleisin virhetyyppi on parittomat sulkumerkit tai lainausmerkit. Kotoistamisjärjestelmä vaatii, että kaikilla avaavilla sulkumerkeillä ('[', '{' tai '(' ) on täsmäävä sulkeva sulkumerkki (']', '}' tai ')' ) samassa kotoistamisyksikössä, muutoin kotoistamista pidetään vaillinaisena.

Sama sääntö ei ole pakollinen wiki-ohjelmistossa, joten kirjoittajat helposti sortuvat noihin virheisiin. Jos sulkumerkki yksinkertaisesti puuttuu, niin lisää se. Joskus sulkumerkkien sisään suljettu sisältö ulottuu useampaan kuin yhteen kotoistamisyksikköön, joten täsmäävä sulkeva lainausmerkki on myöhemmässä yksikössä. Tässä tapauksessa tarvitset parilliset lainausmerkit molemmissa yksiköissä, mutta et voi yksinkertaisesti lisätä sulkumerkkejä muuttamatta muotoilun merkitystä, joten sinun on kommentoitava piiloon lisätyt sulkumerkit, kuten tämä

{{Input|1=<nowiki>{{Info|1=Pitkän tietolaatikon alku... </nowiki>}}

ja myöhemmässä yksikössä

{{Input|1=<nowiki> ...pitkän tietolaatikon loppu}}</nowiki>}}

Jos rikkova sulkumerkki on osa hymiötä, korvaa se emoticon-kuvakkeella. Vakiohymiötä varten :-) voit käyttää mallinetta <nowiki>{{Smiley}}</nowiki>

Korjaa myös alkuperäissivu, jotta muilla kotoistajilla ei ole sama pulma, tai jätä viesti keskustelusivulle.

=== Kielitilastojen epäjohdonmukaisuuksia ===

Saatat havaita lievää epäjohdonmukaisuutta LanguageStats-sivulla osoitetuissa prosenttiluvuissa ja kielipalkin prosenttiluvuissa. Tämä on normaalia. LanguageStats vertaa vain niiden viestien lukumäärää, jotka ovat kotoistamattomia tai vanhentuneita. Kielipalkkitilasto yrittää olla älykkäämpi. Esimerkiksi yhdellä sivulla (100 viestiä) 8:ssa viestissä oli pieni (uudelleen-lajittelun-aiheuttama) muutos. Jokaisessa tapauksessa kyse oli yksittäisestä sanasta. Kahdessa tilastossa on 8% ero, koska se oli viestien oleellinen osa, mutta pieni osa koko kokoistamisesta.

=== Jos käytät Chromium- tai Chrome-selainta... ===

Ole tietoinen, että Chromium-selaimessa on jonkinlainen välimuistipulma. Olen huomannut, että jopa pakotetuilla virkistyksillä jotkut tilastot eivät näy kuten niiden pitäisi näkyä (olen nähnyt vaikutuksia myös muissa asioissa), vaikka sama sivu Firefox-selaimessa avattuna näyttää tilastot oikein.

== Katso myös ==


* [http://translatewiki.net/wiki/Translating:Page_translation_feature#Translators]


[[Category:Translator_Help]]

Translations:Translate a Page/7/fi

2012-12-23T15:46:41Z

Centerlink:

{{Note|Huomaa|Kielikoodin ''en'' (englanti) kirjoittaminen kielikoodivalintaan ei näytä yhtään kotoistusviestiä, koska kaikki alkuperäinen sisältö on kirjoitettu englanniksi.}}

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/44/fi

2011-11-01T17:34:19Z

Centerlink: Created page with "Category:Ruby"

[[Category:Ruby]]

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/fi

2011-11-01T17:34:13Z

Centerlink: Created page with "=== Harjoitukset ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Facing the Wall|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Tutorial 13 - Game Over]]
}}
== Facing the Wall ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_14.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/t14.rb t14.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/cannon.rb cannon.rb]

=== Yleiskuva ===

This is the final example: a complete game.

We add keyboard accelerators and introduce mouse events to '''<tt>CannonField</tt>'''. We put a frame around the '''<tt>CannonField</tt>''' and add a barrier (wall) to make the game more challenging.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' can now receive mouse events to make the user aim the barrel by clicking on it and dragging. '''<tt>CannonField</tt>''' also has a barrier wall.

<syntaxhighlight lang="ruby">
@barrelPressed = false
</syntaxhighlight>

This line has been added to the constructor. Initially, the mouse is not pressed on the barrel.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height() ||
shotR.intersects(barrierRect())
</syntaxhighlight>

Now that we have a barrier, there are three ways to miss. We test for the third, too. (In '''<tt>moveShot()</tt>'''.)

<syntaxhighlight lang="ruby">
def mousePressEvent(event)
unless event.button() == Qt::LeftButton
return
end

if barrelHit(event.pos())
@barrelPressed = true
end
end
</syntaxhighlight>

This is a Qt event handler. It is called when the user presses a mouse button when the mouse cursor is over the widget.

If the event was not generated by the left mouse button, we return immediately. Otherwise, we check if the position of the mouse cursor is within the cannon's barrel. If it is, we set '''<tt>barrelPressed</tt>''' to true.

Notice that the [http://doc.qt.nokia.com/latest/qmouseevent.html#pos Qt::MouseEvent::pos()] function returns a point in the widget's coordinate system.

<syntaxhighlight lang="ruby">
def mouseMoveEvent(event)
unless @barrelPressed
return
end

pos = event.pos();

if pos.x() <= 0
pos.setX(1)
end

if pos.y() >= height()
pos.setY(height() - 1)
end

rad = atan2((rect().bottom() - pos.y()), pos.x())
setAngle((rad * 180 / 3.14159265).round())
end
</syntaxhighlight>

This is another Qt event handler. It is called when the user already has pressed the mouse button inside this widget and then moves/drags the mouse. (You can make Qt send mouse move events even when no buttons are pressed. See [http://doc.qt.nokia.com/latest/qwidget.html#mouseTracking-prop Qt::Widget::setMouseTracking()].)

This handler repositions the cannon's barrel according to the position of the mouse cursor.

First, if the barrel is not pressed, we return. Next, we fetch the mouse cursor's position. If the mouse cursor is to the left or below the widget, we adjust the point to be inside the widget.

Then we calculate the angle between the bottom edge of the widget and the imaginary line between the bottom-left corner of the widget and the cursor position. Finally we set the cannon's angle to the new value converted to degrees.

Remember that '''<tt>setAngle()</tt>''' redraws the cannon.

<syntaxhighlight lang="ruby">
def mouseReleaseEvent(event)
if event.button() == Qt::LeftButton
@barrelPressed = false
end
end
</syntaxhighlight>

This Qt event handler is called whenever the user releases a mouse button and it was pressed inside this widget.

If the left button is released, we can be sure that the barrel is no longer pressed.

The paint event has one extra line:

<syntaxhighlight lang="ruby">
paintBarrier(painter)
</syntaxhighlight>

'''<tt>paintBarrier()</tt>''' does the same sort of thing as '''<tt>paintShot()</tt>''', '''<tt>paintTarget()</tt>''', and '''<tt>paintCannon()</tt>'''.

<syntaxhighlight lang="ruby">
def paintBarrier( painter )
painter.setBrush(Qt::Brush.new(Qt::yellow))
painter.setPen(Qt::Color.new(Qt::black))
painter.drawRect(barrierRect())
end
</syntaxhighlight>

This function paints the barrier as a rectangle filled with yellow and with a black outline.

<syntaxhighlight lang="ruby">
def barrierRect()
return Qt::Rect.new(145, height() - 100, 15, 99)
end
</syntaxhighlight>

This function returns the rectangle of the barrier. We fix the bottom edge of the barrier to the bottom edge of the widget.

<syntaxhighlight lang="ruby">
def barrelHit(pos)
matrix = Qt::Matrix.new()
matrix.translate(0, height())
matrix.rotate(-@currentAngle)
matrix = matrix.inverted()
return @barrelRect.contains(matrix.map(pos))
end
</syntaxhighlight>

This function returns '''<tt>true</tt>''' if the point is in the barrel; otherwise it returns '''<tt>false</tt>'''.

Here we use the class [http://doc.qt.nokia.com/latest/qmatrix.html Qt::Matrix]. [http://doc.qt.nokia.com/latest/qmatrix.html Qt::Matrix] defines a coordinate system mapping. It can perform the same transformations as the [http://doc.qt.nokia.com/latest/qpainter.html Qt::Painter].

Here we perform the same transformation steps as we do when drawing the barrel in the '''<tt>paintCannon()</tt>''' function. First we translate the coordinate system and then we rotate it.

Now we need to check whether the point '''<tt>pos</tt>''' (in widget coordinates) lies inside the barrel. To do this, we invert the transformation matrix. The inverted matrix performs the inverse transformation that we used when drawing the barrel. We map the point '''<tt>pos</tt>''' using the inverted matrix and return '''<tt>true</tt>''' if it is inside the original barrel rectangle.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/gamebrd.rb gamebrd.rb]'''

<syntaxhighlight lang="ruby">
cannonBox = Qt::Frame.new()
cannonBox.setFrameStyle(Qt::Frame::WinPanel | Qt::Frame::Sunken)
</syntaxhighlight>

We create and set up a [http://doc.qt.nokia.com/latest/qframe.html Qt::Frame], and set its frame style. This results in a 3D frame around the '''<tt>CannonField</tt>'''.

<syntaxhighlight lang="ruby">
Qt::Shortcut.new(Qt::KeySequence.new(Qt::Key_Enter.to_i),
self, SLOT('fire()'))
Qt::Shortcut.new(Qt::KeySequence.new(Qt::Key_Return.to_i),
self, SLOT('fire()'))
Qt::Shortcut.new(Qt::KeySequence.new(Qt::CTRL.to_i + Qt::Key_Q.to_i),
self, SLOT('close()'))
</syntaxhighlight>

Here we create and set up three [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] objects. These objects intercept keyboard events to a widget and call slots if certain keys are pressed. Note that a [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] object is a child of a widget and will be destroyed when that widget is destroyed. [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] itself is not a widget and has no visible effect on its parent.

We define three shortcut keys. We want the '''<tt>fire()</tt>''' slot to be called when the user presses Enter or Return. We also want the application to quit when key Ctrl+Q is pressed. Instead of connecting to [http://doc.qt.nokia.com/latest/qcoreapplication.html#quit Qt::CoreApplication::quit()], we connect to [http://doc.qt.nokia.com/latest/qwidget.html#close Qt::Widget::close()] this time. Since the '''<tt>GameBoard</tt>''' is the application's main widget, this has the same effect as [http://doc.qt.nokia.com/latest/qcoreapplication.html#quit QCoreApplication::quit()].

Qt::CTRL, Qt::Key_Enter, Qt::Key_Return, and Qt::Key_Q are all constants declared in the Qt namespace. Unfortunately, in the current version of qtruby, they need to be converted to integers before we can use them in our shortcuts.

<syntaxhighlight lang="ruby">
leftLayout = Qt::VBoxLayout.new()
leftLayout.addWidget(angle)
leftLayout.addWidget(force)

gridLayout = Qt::GridLayout.new()
gridLayout.addWidget(quit, 0, 0)
gridLayout.addLayout(topLayout, 0, 1)
gridLayout.addLayout(leftLayout, 1, 0)
gridLayout.addWidget(@cannonField, 1, 1, 2, 1)
gridLayout.setColumnStretch(1, 10)
setLayout(gridLayout)
</syntaxhighlight>

We give '''<tt>cannonBox</tt>''' its own [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout], and we add '''<tt>CannonField</tt>''' to that layout. This implicitly makes '''<tt>CannonField</tt>''' a child of '''<tt>cannonBox</tt>'''. Because nothing else is in the box, the effect is that the [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] will put a frame around the '''<tt>CannonField</tt>'''. We put '''<tt>cannonBox</tt>''', not '''<tt>CannonField</tt>''', in the grid layout.

=== Sovellusen suorittaminen ===

The cannon now shoots when you press Enter. You can also position the cannon's angle using the mouse. The barrier makes it a little more challenging to play the game. We also have a nice looking frame around the '''<tt>CannonField</tt>'''.

=== Harjoitukset ===

Write a space invaders game.

The new exercise is: Write a Breakout game.

Final exhortation: Go forth now and create masterpieces of the programming art!

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/40/fi

2011-11-01T17:34:12Z

Centerlink: Created page with "=== Harjoitukset ==="

=== Harjoitukset ===

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/fi

2011-11-01T17:34:00Z

Centerlink: Created page with "=== Sovellusen suorittaminen ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Facing the Wall|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Tutorial 13 - Game Over]]
}}
== Facing the Wall ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_14.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/t14.rb t14.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/cannon.rb cannon.rb]

=== Yleiskuva ===

This is the final example: a complete game.

We add keyboard accelerators and introduce mouse events to '''<tt>CannonField</tt>'''. We put a frame around the '''<tt>CannonField</tt>''' and add a barrier (wall) to make the game more challenging.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' can now receive mouse events to make the user aim the barrel by clicking on it and dragging. '''<tt>CannonField</tt>''' also has a barrier wall.

<syntaxhighlight lang="ruby">
@barrelPressed = false
</syntaxhighlight>

This line has been added to the constructor. Initially, the mouse is not pressed on the barrel.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height() ||
shotR.intersects(barrierRect())
</syntaxhighlight>

Now that we have a barrier, there are three ways to miss. We test for the third, too. (In '''<tt>moveShot()</tt>'''.)

<syntaxhighlight lang="ruby">
def mousePressEvent(event)
unless event.button() == Qt::LeftButton
return
end

if barrelHit(event.pos())
@barrelPressed = true
end
end
</syntaxhighlight>

This is a Qt event handler. It is called when the user presses a mouse button when the mouse cursor is over the widget.

If the event was not generated by the left mouse button, we return immediately. Otherwise, we check if the position of the mouse cursor is within the cannon's barrel. If it is, we set '''<tt>barrelPressed</tt>''' to true.

Notice that the [http://doc.qt.nokia.com/latest/qmouseevent.html#pos Qt::MouseEvent::pos()] function returns a point in the widget's coordinate system.

<syntaxhighlight lang="ruby">
def mouseMoveEvent(event)
unless @barrelPressed
return
end

pos = event.pos();

if pos.x() <= 0
pos.setX(1)
end

if pos.y() >= height()
pos.setY(height() - 1)
end

rad = atan2((rect().bottom() - pos.y()), pos.x())
setAngle((rad * 180 / 3.14159265).round())
end
</syntaxhighlight>

This is another Qt event handler. It is called when the user already has pressed the mouse button inside this widget and then moves/drags the mouse. (You can make Qt send mouse move events even when no buttons are pressed. See [http://doc.qt.nokia.com/latest/qwidget.html#mouseTracking-prop Qt::Widget::setMouseTracking()].)

This handler repositions the cannon's barrel according to the position of the mouse cursor.

First, if the barrel is not pressed, we return. Next, we fetch the mouse cursor's position. If the mouse cursor is to the left or below the widget, we adjust the point to be inside the widget.

Then we calculate the angle between the bottom edge of the widget and the imaginary line between the bottom-left corner of the widget and the cursor position. Finally we set the cannon's angle to the new value converted to degrees.

Remember that '''<tt>setAngle()</tt>''' redraws the cannon.

<syntaxhighlight lang="ruby">
def mouseReleaseEvent(event)
if event.button() == Qt::LeftButton
@barrelPressed = false
end
end
</syntaxhighlight>

This Qt event handler is called whenever the user releases a mouse button and it was pressed inside this widget.

If the left button is released, we can be sure that the barrel is no longer pressed.

The paint event has one extra line:

<syntaxhighlight lang="ruby">
paintBarrier(painter)
</syntaxhighlight>

'''<tt>paintBarrier()</tt>''' does the same sort of thing as '''<tt>paintShot()</tt>''', '''<tt>paintTarget()</tt>''', and '''<tt>paintCannon()</tt>'''.

<syntaxhighlight lang="ruby">
def paintBarrier( painter )
painter.setBrush(Qt::Brush.new(Qt::yellow))
painter.setPen(Qt::Color.new(Qt::black))
painter.drawRect(barrierRect())
end
</syntaxhighlight>

This function paints the barrier as a rectangle filled with yellow and with a black outline.

<syntaxhighlight lang="ruby">
def barrierRect()
return Qt::Rect.new(145, height() - 100, 15, 99)
end
</syntaxhighlight>

This function returns the rectangle of the barrier. We fix the bottom edge of the barrier to the bottom edge of the widget.

<syntaxhighlight lang="ruby">
def barrelHit(pos)
matrix = Qt::Matrix.new()
matrix.translate(0, height())
matrix.rotate(-@currentAngle)
matrix = matrix.inverted()
return @barrelRect.contains(matrix.map(pos))
end
</syntaxhighlight>

This function returns '''<tt>true</tt>''' if the point is in the barrel; otherwise it returns '''<tt>false</tt>'''.

Here we use the class [http://doc.qt.nokia.com/latest/qmatrix.html Qt::Matrix]. [http://doc.qt.nokia.com/latest/qmatrix.html Qt::Matrix] defines a coordinate system mapping. It can perform the same transformations as the [http://doc.qt.nokia.com/latest/qpainter.html Qt::Painter].

Here we perform the same transformation steps as we do when drawing the barrel in the '''<tt>paintCannon()</tt>''' function. First we translate the coordinate system and then we rotate it.

Now we need to check whether the point '''<tt>pos</tt>''' (in widget coordinates) lies inside the barrel. To do this, we invert the transformation matrix. The inverted matrix performs the inverse transformation that we used when drawing the barrel. We map the point '''<tt>pos</tt>''' using the inverted matrix and return '''<tt>true</tt>''' if it is inside the original barrel rectangle.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/gamebrd.rb gamebrd.rb]'''

<syntaxhighlight lang="ruby">
cannonBox = Qt::Frame.new()
cannonBox.setFrameStyle(Qt::Frame::WinPanel | Qt::Frame::Sunken)
</syntaxhighlight>

We create and set up a [http://doc.qt.nokia.com/latest/qframe.html Qt::Frame], and set its frame style. This results in a 3D frame around the '''<tt>CannonField</tt>'''.

<syntaxhighlight lang="ruby">
Qt::Shortcut.new(Qt::KeySequence.new(Qt::Key_Enter.to_i),
self, SLOT('fire()'))
Qt::Shortcut.new(Qt::KeySequence.new(Qt::Key_Return.to_i),
self, SLOT('fire()'))
Qt::Shortcut.new(Qt::KeySequence.new(Qt::CTRL.to_i + Qt::Key_Q.to_i),
self, SLOT('close()'))
</syntaxhighlight>

Here we create and set up three [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] objects. These objects intercept keyboard events to a widget and call slots if certain keys are pressed. Note that a [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] object is a child of a widget and will be destroyed when that widget is destroyed. [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] itself is not a widget and has no visible effect on its parent.

We define three shortcut keys. We want the '''<tt>fire()</tt>''' slot to be called when the user presses Enter or Return. We also want the application to quit when key Ctrl+Q is pressed. Instead of connecting to [http://doc.qt.nokia.com/latest/qcoreapplication.html#quit Qt::CoreApplication::quit()], we connect to [http://doc.qt.nokia.com/latest/qwidget.html#close Qt::Widget::close()] this time. Since the '''<tt>GameBoard</tt>''' is the application's main widget, this has the same effect as [http://doc.qt.nokia.com/latest/qcoreapplication.html#quit QCoreApplication::quit()].

Qt::CTRL, Qt::Key_Enter, Qt::Key_Return, and Qt::Key_Q are all constants declared in the Qt namespace. Unfortunately, in the current version of qtruby, they need to be converted to integers before we can use them in our shortcuts.

<syntaxhighlight lang="ruby">
leftLayout = Qt::VBoxLayout.new()
leftLayout.addWidget(angle)
leftLayout.addWidget(force)

gridLayout = Qt::GridLayout.new()
gridLayout.addWidget(quit, 0, 0)
gridLayout.addLayout(topLayout, 0, 1)
gridLayout.addLayout(leftLayout, 1, 0)
gridLayout.addWidget(@cannonField, 1, 1, 2, 1)
gridLayout.setColumnStretch(1, 10)
setLayout(gridLayout)
</syntaxhighlight>

We give '''<tt>cannonBox</tt>''' its own [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout], and we add '''<tt>CannonField</tt>''' to that layout. This implicitly makes '''<tt>CannonField</tt>''' a child of '''<tt>cannonBox</tt>'''. Because nothing else is in the box, the effect is that the [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] will put a frame around the '''<tt>CannonField</tt>'''. We put '''<tt>cannonBox</tt>''', not '''<tt>CannonField</tt>''', in the grid layout.

=== Sovellusen suorittaminen ===

The cannon now shoots when you press Enter. You can also position the cannon's angle using the mouse. The barrier makes it a little more challenging to play the game. We also have a nice looking frame around the '''<tt>CannonField</tt>'''.

=== Exercises ===

Write a space invaders game.

The new exercise is: Write a Breakout game.

Final exhortation: Go forth now and create masterpieces of the programming art!

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/38/fi

2011-11-01T17:34:00Z

Centerlink: Created page with "=== Sovellusen suorittaminen ==="

=== Sovellusen suorittaminen ===

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/fi

2011-11-01T17:33:35Z

Centerlink: Created page with "=== Läpikäynti rivi riviltä ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Facing the Wall|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Tutorial 13 - Game Over]]
}}
== Facing the Wall ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_14.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/t14.rb t14.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/cannon.rb cannon.rb]

=== Yleiskuva ===

This is the final example: a complete game.

We add keyboard accelerators and introduce mouse events to '''<tt>CannonField</tt>'''. We put a frame around the '''<tt>CannonField</tt>''' and add a barrier (wall) to make the game more challenging.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' can now receive mouse events to make the user aim the barrel by clicking on it and dragging. '''<tt>CannonField</tt>''' also has a barrier wall.

<syntaxhighlight lang="ruby">
@barrelPressed = false
</syntaxhighlight>

This line has been added to the constructor. Initially, the mouse is not pressed on the barrel.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height() ||
shotR.intersects(barrierRect())
</syntaxhighlight>

Now that we have a barrier, there are three ways to miss. We test for the third, too. (In '''<tt>moveShot()</tt>'''.)

<syntaxhighlight lang="ruby">
def mousePressEvent(event)
unless event.button() == Qt::LeftButton
return
end

if barrelHit(event.pos())
@barrelPressed = true
end
end
</syntaxhighlight>

This is a Qt event handler. It is called when the user presses a mouse button when the mouse cursor is over the widget.

If the event was not generated by the left mouse button, we return immediately. Otherwise, we check if the position of the mouse cursor is within the cannon's barrel. If it is, we set '''<tt>barrelPressed</tt>''' to true.

Notice that the [http://doc.qt.nokia.com/latest/qmouseevent.html#pos Qt::MouseEvent::pos()] function returns a point in the widget's coordinate system.

<syntaxhighlight lang="ruby">
def mouseMoveEvent(event)
unless @barrelPressed
return
end

pos = event.pos();

if pos.x() <= 0
pos.setX(1)
end

if pos.y() >= height()
pos.setY(height() - 1)
end

rad = atan2((rect().bottom() - pos.y()), pos.x())
setAngle((rad * 180 / 3.14159265).round())
end
</syntaxhighlight>

This is another Qt event handler. It is called when the user already has pressed the mouse button inside this widget and then moves/drags the mouse. (You can make Qt send mouse move events even when no buttons are pressed. See [http://doc.qt.nokia.com/latest/qwidget.html#mouseTracking-prop Qt::Widget::setMouseTracking()].)

This handler repositions the cannon's barrel according to the position of the mouse cursor.

First, if the barrel is not pressed, we return. Next, we fetch the mouse cursor's position. If the mouse cursor is to the left or below the widget, we adjust the point to be inside the widget.

Then we calculate the angle between the bottom edge of the widget and the imaginary line between the bottom-left corner of the widget and the cursor position. Finally we set the cannon's angle to the new value converted to degrees.

Remember that '''<tt>setAngle()</tt>''' redraws the cannon.

<syntaxhighlight lang="ruby">
def mouseReleaseEvent(event)
if event.button() == Qt::LeftButton
@barrelPressed = false
end
end
</syntaxhighlight>

This Qt event handler is called whenever the user releases a mouse button and it was pressed inside this widget.

If the left button is released, we can be sure that the barrel is no longer pressed.

The paint event has one extra line:

<syntaxhighlight lang="ruby">
paintBarrier(painter)
</syntaxhighlight>

'''<tt>paintBarrier()</tt>''' does the same sort of thing as '''<tt>paintShot()</tt>''', '''<tt>paintTarget()</tt>''', and '''<tt>paintCannon()</tt>'''.

<syntaxhighlight lang="ruby">
def paintBarrier( painter )
painter.setBrush(Qt::Brush.new(Qt::yellow))
painter.setPen(Qt::Color.new(Qt::black))
painter.drawRect(barrierRect())
end
</syntaxhighlight>

This function paints the barrier as a rectangle filled with yellow and with a black outline.

<syntaxhighlight lang="ruby">
def barrierRect()
return Qt::Rect.new(145, height() - 100, 15, 99)
end
</syntaxhighlight>

This function returns the rectangle of the barrier. We fix the bottom edge of the barrier to the bottom edge of the widget.

<syntaxhighlight lang="ruby">
def barrelHit(pos)
matrix = Qt::Matrix.new()
matrix.translate(0, height())
matrix.rotate(-@currentAngle)
matrix = matrix.inverted()
return @barrelRect.contains(matrix.map(pos))
end
</syntaxhighlight>

This function returns '''<tt>true</tt>''' if the point is in the barrel; otherwise it returns '''<tt>false</tt>'''.

Here we use the class [http://doc.qt.nokia.com/latest/qmatrix.html Qt::Matrix]. [http://doc.qt.nokia.com/latest/qmatrix.html Qt::Matrix] defines a coordinate system mapping. It can perform the same transformations as the [http://doc.qt.nokia.com/latest/qpainter.html Qt::Painter].

Here we perform the same transformation steps as we do when drawing the barrel in the '''<tt>paintCannon()</tt>''' function. First we translate the coordinate system and then we rotate it.

Now we need to check whether the point '''<tt>pos</tt>''' (in widget coordinates) lies inside the barrel. To do this, we invert the transformation matrix. The inverted matrix performs the inverse transformation that we used when drawing the barrel. We map the point '''<tt>pos</tt>''' using the inverted matrix and return '''<tt>true</tt>''' if it is inside the original barrel rectangle.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/gamebrd.rb gamebrd.rb]'''

<syntaxhighlight lang="ruby">
cannonBox = Qt::Frame.new()
cannonBox.setFrameStyle(Qt::Frame::WinPanel | Qt::Frame::Sunken)
</syntaxhighlight>

We create and set up a [http://doc.qt.nokia.com/latest/qframe.html Qt::Frame], and set its frame style. This results in a 3D frame around the '''<tt>CannonField</tt>'''.

<syntaxhighlight lang="ruby">
Qt::Shortcut.new(Qt::KeySequence.new(Qt::Key_Enter.to_i),
self, SLOT('fire()'))
Qt::Shortcut.new(Qt::KeySequence.new(Qt::Key_Return.to_i),
self, SLOT('fire()'))
Qt::Shortcut.new(Qt::KeySequence.new(Qt::CTRL.to_i + Qt::Key_Q.to_i),
self, SLOT('close()'))
</syntaxhighlight>

Here we create and set up three [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] objects. These objects intercept keyboard events to a widget and call slots if certain keys are pressed. Note that a [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] object is a child of a widget and will be destroyed when that widget is destroyed. [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] itself is not a widget and has no visible effect on its parent.

We define three shortcut keys. We want the '''<tt>fire()</tt>''' slot to be called when the user presses Enter or Return. We also want the application to quit when key Ctrl+Q is pressed. Instead of connecting to [http://doc.qt.nokia.com/latest/qcoreapplication.html#quit Qt::CoreApplication::quit()], we connect to [http://doc.qt.nokia.com/latest/qwidget.html#close Qt::Widget::close()] this time. Since the '''<tt>GameBoard</tt>''' is the application's main widget, this has the same effect as [http://doc.qt.nokia.com/latest/qcoreapplication.html#quit QCoreApplication::quit()].

Qt::CTRL, Qt::Key_Enter, Qt::Key_Return, and Qt::Key_Q are all constants declared in the Qt namespace. Unfortunately, in the current version of qtruby, they need to be converted to integers before we can use them in our shortcuts.

<syntaxhighlight lang="ruby">
leftLayout = Qt::VBoxLayout.new()
leftLayout.addWidget(angle)
leftLayout.addWidget(force)

gridLayout = Qt::GridLayout.new()
gridLayout.addWidget(quit, 0, 0)
gridLayout.addLayout(topLayout, 0, 1)
gridLayout.addLayout(leftLayout, 1, 0)
gridLayout.addWidget(@cannonField, 1, 1, 2, 1)
gridLayout.setColumnStretch(1, 10)
setLayout(gridLayout)
</syntaxhighlight>

We give '''<tt>cannonBox</tt>''' its own [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout], and we add '''<tt>CannonField</tt>''' to that layout. This implicitly makes '''<tt>CannonField</tt>''' a child of '''<tt>cannonBox</tt>'''. Because nothing else is in the box, the effect is that the [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] will put a frame around the '''<tt>CannonField</tt>'''. We put '''<tt>cannonBox</tt>''', not '''<tt>CannonField</tt>''', in the grid layout.

=== Running the Application ===

The cannon now shoots when you press Enter. You can also position the cannon's angle using the mouse. The barrier makes it a little more challenging to play the game. We also have a nice looking frame around the '''<tt>CannonField</tt>'''.

=== Exercises ===

Write a space invaders game.

The new exercise is: Write a Breakout game.

Final exhortation: Go forth now and create masterpieces of the programming art!

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/11/fi

2011-11-01T17:33:34Z

Centerlink: Created page with "=== Läpikäynti rivi riviltä ==="

=== Läpikäynti rivi riviltä ===

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/fi

2011-11-01T17:33:20Z

Centerlink: Created page with "=== Yleiskuva ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Facing the Wall|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Tutorial 13 - Game Over]]
}}
== Facing the Wall ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_14.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/t14.rb t14.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/cannon.rb cannon.rb]

=== Yleiskuva ===

This is the final example: a complete game.

We add keyboard accelerators and introduce mouse events to '''<tt>CannonField</tt>'''. We put a frame around the '''<tt>CannonField</tt>''' and add a barrier (wall) to make the game more challenging.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' can now receive mouse events to make the user aim the barrel by clicking on it and dragging. '''<tt>CannonField</tt>''' also has a barrier wall.

<syntaxhighlight lang="ruby">
@barrelPressed = false
</syntaxhighlight>

This line has been added to the constructor. Initially, the mouse is not pressed on the barrel.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height() ||
shotR.intersects(barrierRect())
</syntaxhighlight>

Now that we have a barrier, there are three ways to miss. We test for the third, too. (In '''<tt>moveShot()</tt>'''.)

<syntaxhighlight lang="ruby">
def mousePressEvent(event)
unless event.button() == Qt::LeftButton
return
end

if barrelHit(event.pos())
@barrelPressed = true
end
end
</syntaxhighlight>

This is a Qt event handler. It is called when the user presses a mouse button when the mouse cursor is over the widget.

If the event was not generated by the left mouse button, we return immediately. Otherwise, we check if the position of the mouse cursor is within the cannon's barrel. If it is, we set '''<tt>barrelPressed</tt>''' to true.

Notice that the [http://doc.qt.nokia.com/latest/qmouseevent.html#pos Qt::MouseEvent::pos()] function returns a point in the widget's coordinate system.

<syntaxhighlight lang="ruby">
def mouseMoveEvent(event)
unless @barrelPressed
return
end

pos = event.pos();

if pos.x() <= 0
pos.setX(1)
end

if pos.y() >= height()
pos.setY(height() - 1)
end

rad = atan2((rect().bottom() - pos.y()), pos.x())
setAngle((rad * 180 / 3.14159265).round())
end
</syntaxhighlight>

This is another Qt event handler. It is called when the user already has pressed the mouse button inside this widget and then moves/drags the mouse. (You can make Qt send mouse move events even when no buttons are pressed. See [http://doc.qt.nokia.com/latest/qwidget.html#mouseTracking-prop Qt::Widget::setMouseTracking()].)

This handler repositions the cannon's barrel according to the position of the mouse cursor.

First, if the barrel is not pressed, we return. Next, we fetch the mouse cursor's position. If the mouse cursor is to the left or below the widget, we adjust the point to be inside the widget.

Then we calculate the angle between the bottom edge of the widget and the imaginary line between the bottom-left corner of the widget and the cursor position. Finally we set the cannon's angle to the new value converted to degrees.

Remember that '''<tt>setAngle()</tt>''' redraws the cannon.

<syntaxhighlight lang="ruby">
def mouseReleaseEvent(event)
if event.button() == Qt::LeftButton
@barrelPressed = false
end
end
</syntaxhighlight>

This Qt event handler is called whenever the user releases a mouse button and it was pressed inside this widget.

If the left button is released, we can be sure that the barrel is no longer pressed.

The paint event has one extra line:

<syntaxhighlight lang="ruby">
paintBarrier(painter)
</syntaxhighlight>

'''<tt>paintBarrier()</tt>''' does the same sort of thing as '''<tt>paintShot()</tt>''', '''<tt>paintTarget()</tt>''', and '''<tt>paintCannon()</tt>'''.

<syntaxhighlight lang="ruby">
def paintBarrier( painter )
painter.setBrush(Qt::Brush.new(Qt::yellow))
painter.setPen(Qt::Color.new(Qt::black))
painter.drawRect(barrierRect())
end
</syntaxhighlight>

This function paints the barrier as a rectangle filled with yellow and with a black outline.

<syntaxhighlight lang="ruby">
def barrierRect()
return Qt::Rect.new(145, height() - 100, 15, 99)
end
</syntaxhighlight>

This function returns the rectangle of the barrier. We fix the bottom edge of the barrier to the bottom edge of the widget.

<syntaxhighlight lang="ruby">
def barrelHit(pos)
matrix = Qt::Matrix.new()
matrix.translate(0, height())
matrix.rotate(-@currentAngle)
matrix = matrix.inverted()
return @barrelRect.contains(matrix.map(pos))
end
</syntaxhighlight>

This function returns '''<tt>true</tt>''' if the point is in the barrel; otherwise it returns '''<tt>false</tt>'''.

Here we use the class [http://doc.qt.nokia.com/latest/qmatrix.html Qt::Matrix]. [http://doc.qt.nokia.com/latest/qmatrix.html Qt::Matrix] defines a coordinate system mapping. It can perform the same transformations as the [http://doc.qt.nokia.com/latest/qpainter.html Qt::Painter].

Here we perform the same transformation steps as we do when drawing the barrel in the '''<tt>paintCannon()</tt>''' function. First we translate the coordinate system and then we rotate it.

Now we need to check whether the point '''<tt>pos</tt>''' (in widget coordinates) lies inside the barrel. To do this, we invert the transformation matrix. The inverted matrix performs the inverse transformation that we used when drawing the barrel. We map the point '''<tt>pos</tt>''' using the inverted matrix and return '''<tt>true</tt>''' if it is inside the original barrel rectangle.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/gamebrd.rb gamebrd.rb]'''

<syntaxhighlight lang="ruby">
cannonBox = Qt::Frame.new()
cannonBox.setFrameStyle(Qt::Frame::WinPanel | Qt::Frame::Sunken)
</syntaxhighlight>

We create and set up a [http://doc.qt.nokia.com/latest/qframe.html Qt::Frame], and set its frame style. This results in a 3D frame around the '''<tt>CannonField</tt>'''.

<syntaxhighlight lang="ruby">
Qt::Shortcut.new(Qt::KeySequence.new(Qt::Key_Enter.to_i),
self, SLOT('fire()'))
Qt::Shortcut.new(Qt::KeySequence.new(Qt::Key_Return.to_i),
self, SLOT('fire()'))
Qt::Shortcut.new(Qt::KeySequence.new(Qt::CTRL.to_i + Qt::Key_Q.to_i),
self, SLOT('close()'))
</syntaxhighlight>

Here we create and set up three [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] objects. These objects intercept keyboard events to a widget and call slots if certain keys are pressed. Note that a [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] object is a child of a widget and will be destroyed when that widget is destroyed. [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] itself is not a widget and has no visible effect on its parent.

We define three shortcut keys. We want the '''<tt>fire()</tt>''' slot to be called when the user presses Enter or Return. We also want the application to quit when key Ctrl+Q is pressed. Instead of connecting to [http://doc.qt.nokia.com/latest/qcoreapplication.html#quit Qt::CoreApplication::quit()], we connect to [http://doc.qt.nokia.com/latest/qwidget.html#close Qt::Widget::close()] this time. Since the '''<tt>GameBoard</tt>''' is the application's main widget, this has the same effect as [http://doc.qt.nokia.com/latest/qcoreapplication.html#quit QCoreApplication::quit()].

Qt::CTRL, Qt::Key_Enter, Qt::Key_Return, and Qt::Key_Q are all constants declared in the Qt namespace. Unfortunately, in the current version of qtruby, they need to be converted to integers before we can use them in our shortcuts.

<syntaxhighlight lang="ruby">
leftLayout = Qt::VBoxLayout.new()
leftLayout.addWidget(angle)
leftLayout.addWidget(force)

gridLayout = Qt::GridLayout.new()
gridLayout.addWidget(quit, 0, 0)
gridLayout.addLayout(topLayout, 0, 1)
gridLayout.addLayout(leftLayout, 1, 0)
gridLayout.addWidget(@cannonField, 1, 1, 2, 1)
gridLayout.setColumnStretch(1, 10)
setLayout(gridLayout)
</syntaxhighlight>

We give '''<tt>cannonBox</tt>''' its own [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout], and we add '''<tt>CannonField</tt>''' to that layout. This implicitly makes '''<tt>CannonField</tt>''' a child of '''<tt>cannonBox</tt>'''. Because nothing else is in the box, the effect is that the [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] will put a frame around the '''<tt>CannonField</tt>'''. We put '''<tt>cannonBox</tt>''', not '''<tt>CannonField</tt>''', in the grid layout.

=== Running the Application ===

The cannon now shoots when you press Enter. You can also position the cannon's angle using the mouse. The barrier makes it a little more challenging to play the game. We also have a nice looking frame around the '''<tt>CannonField</tt>'''.

=== Exercises ===

Write a space invaders game.

The new exercise is: Write a Breakout game.

Final exhortation: Go forth now and create masterpieces of the programming art!

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/8/fi

2011-11-01T17:33:20Z

Centerlink: Created page with "=== Yleiskuva ==="

=== Yleiskuva ===

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/6/fi

2011-11-01T17:33:09Z

Centerlink: Created page with "center"

[[Image:Qt4_Ruby_Tutorial_Screenshot_14.png|center]]

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/fi

2011-11-01T17:33:01Z

Centerlink: Created page with "Qt4 Ruby -oppikurssi"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Facing the Wall|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Tutorial 13 - Game Over]]
}}
== Facing the Wall ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_14.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/t14.rb t14.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/cannon.rb cannon.rb]

=== Overview ===

This is the final example: a complete game.

We add keyboard accelerators and introduce mouse events to '''<tt>CannonField</tt>'''. We put a frame around the '''<tt>CannonField</tt>''' and add a barrier (wall) to make the game more challenging.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' can now receive mouse events to make the user aim the barrel by clicking on it and dragging. '''<tt>CannonField</tt>''' also has a barrier wall.

<syntaxhighlight lang="ruby">
@barrelPressed = false
</syntaxhighlight>

This line has been added to the constructor. Initially, the mouse is not pressed on the barrel.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height() ||
shotR.intersects(barrierRect())
</syntaxhighlight>

Now that we have a barrier, there are three ways to miss. We test for the third, too. (In '''<tt>moveShot()</tt>'''.)

<syntaxhighlight lang="ruby">
def mousePressEvent(event)
unless event.button() == Qt::LeftButton
return
end

if barrelHit(event.pos())
@barrelPressed = true
end
end
</syntaxhighlight>

This is a Qt event handler. It is called when the user presses a mouse button when the mouse cursor is over the widget.

If the event was not generated by the left mouse button, we return immediately. Otherwise, we check if the position of the mouse cursor is within the cannon's barrel. If it is, we set '''<tt>barrelPressed</tt>''' to true.

Notice that the [http://doc.qt.nokia.com/latest/qmouseevent.html#pos Qt::MouseEvent::pos()] function returns a point in the widget's coordinate system.

<syntaxhighlight lang="ruby">
def mouseMoveEvent(event)
unless @barrelPressed
return
end

pos = event.pos();

if pos.x() <= 0
pos.setX(1)
end

if pos.y() >= height()
pos.setY(height() - 1)
end

rad = atan2((rect().bottom() - pos.y()), pos.x())
setAngle((rad * 180 / 3.14159265).round())
end
</syntaxhighlight>

This is another Qt event handler. It is called when the user already has pressed the mouse button inside this widget and then moves/drags the mouse. (You can make Qt send mouse move events even when no buttons are pressed. See [http://doc.qt.nokia.com/latest/qwidget.html#mouseTracking-prop Qt::Widget::setMouseTracking()].)

This handler repositions the cannon's barrel according to the position of the mouse cursor.

First, if the barrel is not pressed, we return. Next, we fetch the mouse cursor's position. If the mouse cursor is to the left or below the widget, we adjust the point to be inside the widget.

Then we calculate the angle between the bottom edge of the widget and the imaginary line between the bottom-left corner of the widget and the cursor position. Finally we set the cannon's angle to the new value converted to degrees.

Remember that '''<tt>setAngle()</tt>''' redraws the cannon.

<syntaxhighlight lang="ruby">
def mouseReleaseEvent(event)
if event.button() == Qt::LeftButton
@barrelPressed = false
end
end
</syntaxhighlight>

This Qt event handler is called whenever the user releases a mouse button and it was pressed inside this widget.

If the left button is released, we can be sure that the barrel is no longer pressed.

The paint event has one extra line:

<syntaxhighlight lang="ruby">
paintBarrier(painter)
</syntaxhighlight>

'''<tt>paintBarrier()</tt>''' does the same sort of thing as '''<tt>paintShot()</tt>''', '''<tt>paintTarget()</tt>''', and '''<tt>paintCannon()</tt>'''.

<syntaxhighlight lang="ruby">
def paintBarrier( painter )
painter.setBrush(Qt::Brush.new(Qt::yellow))
painter.setPen(Qt::Color.new(Qt::black))
painter.drawRect(barrierRect())
end
</syntaxhighlight>

This function paints the barrier as a rectangle filled with yellow and with a black outline.

<syntaxhighlight lang="ruby">
def barrierRect()
return Qt::Rect.new(145, height() - 100, 15, 99)
end
</syntaxhighlight>

This function returns the rectangle of the barrier. We fix the bottom edge of the barrier to the bottom edge of the widget.

<syntaxhighlight lang="ruby">
def barrelHit(pos)
matrix = Qt::Matrix.new()
matrix.translate(0, height())
matrix.rotate(-@currentAngle)
matrix = matrix.inverted()
return @barrelRect.contains(matrix.map(pos))
end
</syntaxhighlight>

This function returns '''<tt>true</tt>''' if the point is in the barrel; otherwise it returns '''<tt>false</tt>'''.

Here we use the class [http://doc.qt.nokia.com/latest/qmatrix.html Qt::Matrix]. [http://doc.qt.nokia.com/latest/qmatrix.html Qt::Matrix] defines a coordinate system mapping. It can perform the same transformations as the [http://doc.qt.nokia.com/latest/qpainter.html Qt::Painter].

Here we perform the same transformation steps as we do when drawing the barrel in the '''<tt>paintCannon()</tt>''' function. First we translate the coordinate system and then we rotate it.

Now we need to check whether the point '''<tt>pos</tt>''' (in widget coordinates) lies inside the barrel. To do this, we invert the transformation matrix. The inverted matrix performs the inverse transformation that we used when drawing the barrel. We map the point '''<tt>pos</tt>''' using the inverted matrix and return '''<tt>true</tt>''' if it is inside the original barrel rectangle.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/gamebrd.rb gamebrd.rb]'''

<syntaxhighlight lang="ruby">
cannonBox = Qt::Frame.new()
cannonBox.setFrameStyle(Qt::Frame::WinPanel | Qt::Frame::Sunken)
</syntaxhighlight>

We create and set up a [http://doc.qt.nokia.com/latest/qframe.html Qt::Frame], and set its frame style. This results in a 3D frame around the '''<tt>CannonField</tt>'''.

<syntaxhighlight lang="ruby">
Qt::Shortcut.new(Qt::KeySequence.new(Qt::Key_Enter.to_i),
self, SLOT('fire()'))
Qt::Shortcut.new(Qt::KeySequence.new(Qt::Key_Return.to_i),
self, SLOT('fire()'))
Qt::Shortcut.new(Qt::KeySequence.new(Qt::CTRL.to_i + Qt::Key_Q.to_i),
self, SLOT('close()'))
</syntaxhighlight>

Here we create and set up three [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] objects. These objects intercept keyboard events to a widget and call slots if certain keys are pressed. Note that a [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] object is a child of a widget and will be destroyed when that widget is destroyed. [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] itself is not a widget and has no visible effect on its parent.

We define three shortcut keys. We want the '''<tt>fire()</tt>''' slot to be called when the user presses Enter or Return. We also want the application to quit when key Ctrl+Q is pressed. Instead of connecting to [http://doc.qt.nokia.com/latest/qcoreapplication.html#quit Qt::CoreApplication::quit()], we connect to [http://doc.qt.nokia.com/latest/qwidget.html#close Qt::Widget::close()] this time. Since the '''<tt>GameBoard</tt>''' is the application's main widget, this has the same effect as [http://doc.qt.nokia.com/latest/qcoreapplication.html#quit QCoreApplication::quit()].

Qt::CTRL, Qt::Key_Enter, Qt::Key_Return, and Qt::Key_Q are all constants declared in the Qt namespace. Unfortunately, in the current version of qtruby, they need to be converted to integers before we can use them in our shortcuts.

<syntaxhighlight lang="ruby">
leftLayout = Qt::VBoxLayout.new()
leftLayout.addWidget(angle)
leftLayout.addWidget(force)

gridLayout = Qt::GridLayout.new()
gridLayout.addWidget(quit, 0, 0)
gridLayout.addLayout(topLayout, 0, 1)
gridLayout.addLayout(leftLayout, 1, 0)
gridLayout.addWidget(@cannonField, 1, 1, 2, 1)
gridLayout.setColumnStretch(1, 10)
setLayout(gridLayout)
</syntaxhighlight>

We give '''<tt>cannonBox</tt>''' its own [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout], and we add '''<tt>CannonField</tt>''' to that layout. This implicitly makes '''<tt>CannonField</tt>''' a child of '''<tt>cannonBox</tt>'''. Because nothing else is in the box, the effect is that the [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] will put a frame around the '''<tt>CannonField</tt>'''. We put '''<tt>cannonBox</tt>''', not '''<tt>CannonField</tt>''', in the grid layout.

=== Running the Application ===

The cannon now shoots when you press Enter. You can also position the cannon's angle using the mouse. The barrier makes it a little more challenging to play the game. We also have a nice looking frame around the '''<tt>CannonField</tt>'''.

=== Exercises ===

Write a space invaders game.

The new exercise is: Write a Breakout game.

Final exhortation: Go forth now and create masterpieces of the programming art!

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/2/fi

2011-11-01T17:33:00Z

Centerlink: Created page with "Qt4 Ruby -oppikurssi"

Qt4 Ruby -oppikurssi

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/1/fi

2011-11-01T17:32:45Z

Centerlink: Created page with "TutorialBrowser"

TutorialBrowser

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14/fi

2011-11-01T17:32:45Z

Centerlink: Created page with "TutorialBrowser"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 14}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby Tutorial]]|
name=Facing the Wall|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Tutorial 13 - Game Over]]
}}
== Facing the Wall ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_14.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/t14.rb t14.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/cannon.rb cannon.rb]

=== Overview ===

This is the final example: a complete game.

We add keyboard accelerators and introduce mouse events to '''<tt>CannonField</tt>'''. We put a frame around the '''<tt>CannonField</tt>''' and add a barrier (wall) to make the game more challenging.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' can now receive mouse events to make the user aim the barrel by clicking on it and dragging. '''<tt>CannonField</tt>''' also has a barrier wall.

<syntaxhighlight lang="ruby">
@barrelPressed = false
</syntaxhighlight>

This line has been added to the constructor. Initially, the mouse is not pressed on the barrel.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height() ||
shotR.intersects(barrierRect())
</syntaxhighlight>

Now that we have a barrier, there are three ways to miss. We test for the third, too. (In '''<tt>moveShot()</tt>'''.)

<syntaxhighlight lang="ruby">
def mousePressEvent(event)
unless event.button() == Qt::LeftButton
return
end

if barrelHit(event.pos())
@barrelPressed = true
end
end
</syntaxhighlight>

This is a Qt event handler. It is called when the user presses a mouse button when the mouse cursor is over the widget.

If the event was not generated by the left mouse button, we return immediately. Otherwise, we check if the position of the mouse cursor is within the cannon's barrel. If it is, we set '''<tt>barrelPressed</tt>''' to true.

Notice that the [http://doc.qt.nokia.com/latest/qmouseevent.html#pos Qt::MouseEvent::pos()] function returns a point in the widget's coordinate system.

<syntaxhighlight lang="ruby">
def mouseMoveEvent(event)
unless @barrelPressed
return
end

pos = event.pos();

if pos.x() <= 0
pos.setX(1)
end

if pos.y() >= height()
pos.setY(height() - 1)
end

rad = atan2((rect().bottom() - pos.y()), pos.x())
setAngle((rad * 180 / 3.14159265).round())
end
</syntaxhighlight>

This is another Qt event handler. It is called when the user already has pressed the mouse button inside this widget and then moves/drags the mouse. (You can make Qt send mouse move events even when no buttons are pressed. See [http://doc.qt.nokia.com/latest/qwidget.html#mouseTracking-prop Qt::Widget::setMouseTracking()].)

This handler repositions the cannon's barrel according to the position of the mouse cursor.

First, if the barrel is not pressed, we return. Next, we fetch the mouse cursor's position. If the mouse cursor is to the left or below the widget, we adjust the point to be inside the widget.

Then we calculate the angle between the bottom edge of the widget and the imaginary line between the bottom-left corner of the widget and the cursor position. Finally we set the cannon's angle to the new value converted to degrees.

Remember that '''<tt>setAngle()</tt>''' redraws the cannon.

<syntaxhighlight lang="ruby">
def mouseReleaseEvent(event)
if event.button() == Qt::LeftButton
@barrelPressed = false
end
end
</syntaxhighlight>

This Qt event handler is called whenever the user releases a mouse button and it was pressed inside this widget.

If the left button is released, we can be sure that the barrel is no longer pressed.

The paint event has one extra line:

<syntaxhighlight lang="ruby">
paintBarrier(painter)
</syntaxhighlight>

'''<tt>paintBarrier()</tt>''' does the same sort of thing as '''<tt>paintShot()</tt>''', '''<tt>paintTarget()</tt>''', and '''<tt>paintCannon()</tt>'''.

<syntaxhighlight lang="ruby">
def paintBarrier( painter )
painter.setBrush(Qt::Brush.new(Qt::yellow))
painter.setPen(Qt::Color.new(Qt::black))
painter.drawRect(barrierRect())
end
</syntaxhighlight>

This function paints the barrier as a rectangle filled with yellow and with a black outline.

<syntaxhighlight lang="ruby">
def barrierRect()
return Qt::Rect.new(145, height() - 100, 15, 99)
end
</syntaxhighlight>

This function returns the rectangle of the barrier. We fix the bottom edge of the barrier to the bottom edge of the widget.

<syntaxhighlight lang="ruby">
def barrelHit(pos)
matrix = Qt::Matrix.new()
matrix.translate(0, height())
matrix.rotate(-@currentAngle)
matrix = matrix.inverted()
return @barrelRect.contains(matrix.map(pos))
end
</syntaxhighlight>

This function returns '''<tt>true</tt>''' if the point is in the barrel; otherwise it returns '''<tt>false</tt>'''.

Here we use the class [http://doc.qt.nokia.com/latest/qmatrix.html Qt::Matrix]. [http://doc.qt.nokia.com/latest/qmatrix.html Qt::Matrix] defines a coordinate system mapping. It can perform the same transformations as the [http://doc.qt.nokia.com/latest/qpainter.html Qt::Painter].

Here we perform the same transformation steps as we do when drawing the barrel in the '''<tt>paintCannon()</tt>''' function. First we translate the coordinate system and then we rotate it.

Now we need to check whether the point '''<tt>pos</tt>''' (in widget coordinates) lies inside the barrel. To do this, we invert the transformation matrix. The inverted matrix performs the inverse transformation that we used when drawing the barrel. We map the point '''<tt>pos</tt>''' using the inverted matrix and return '''<tt>true</tt>''' if it is inside the original barrel rectangle.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t14/gamebrd.rb gamebrd.rb]'''

<syntaxhighlight lang="ruby">
cannonBox = Qt::Frame.new()
cannonBox.setFrameStyle(Qt::Frame::WinPanel | Qt::Frame::Sunken)
</syntaxhighlight>

We create and set up a [http://doc.qt.nokia.com/latest/qframe.html Qt::Frame], and set its frame style. This results in a 3D frame around the '''<tt>CannonField</tt>'''.

<syntaxhighlight lang="ruby">
Qt::Shortcut.new(Qt::KeySequence.new(Qt::Key_Enter.to_i),
self, SLOT('fire()'))
Qt::Shortcut.new(Qt::KeySequence.new(Qt::Key_Return.to_i),
self, SLOT('fire()'))
Qt::Shortcut.new(Qt::KeySequence.new(Qt::CTRL.to_i + Qt::Key_Q.to_i),
self, SLOT('close()'))
</syntaxhighlight>

Here we create and set up three [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] objects. These objects intercept keyboard events to a widget and call slots if certain keys are pressed. Note that a [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] object is a child of a widget and will be destroyed when that widget is destroyed. [http://doc.qt.nokia.com/latest/qshortcut.html Qt::Shortcut] itself is not a widget and has no visible effect on its parent.

We define three shortcut keys. We want the '''<tt>fire()</tt>''' slot to be called when the user presses Enter or Return. We also want the application to quit when key Ctrl+Q is pressed. Instead of connecting to [http://doc.qt.nokia.com/latest/qcoreapplication.html#quit Qt::CoreApplication::quit()], we connect to [http://doc.qt.nokia.com/latest/qwidget.html#close Qt::Widget::close()] this time. Since the '''<tt>GameBoard</tt>''' is the application's main widget, this has the same effect as [http://doc.qt.nokia.com/latest/qcoreapplication.html#quit QCoreApplication::quit()].

Qt::CTRL, Qt::Key_Enter, Qt::Key_Return, and Qt::Key_Q are all constants declared in the Qt namespace. Unfortunately, in the current version of qtruby, they need to be converted to integers before we can use them in our shortcuts.

<syntaxhighlight lang="ruby">
leftLayout = Qt::VBoxLayout.new()
leftLayout.addWidget(angle)
leftLayout.addWidget(force)

gridLayout = Qt::GridLayout.new()
gridLayout.addWidget(quit, 0, 0)
gridLayout.addLayout(topLayout, 0, 1)
gridLayout.addLayout(leftLayout, 1, 0)
gridLayout.addWidget(@cannonField, 1, 1, 2, 1)
gridLayout.setColumnStretch(1, 10)
setLayout(gridLayout)
</syntaxhighlight>

We give '''<tt>cannonBox</tt>''' its own [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout], and we add '''<tt>CannonField</tt>''' to that layout. This implicitly makes '''<tt>CannonField</tt>''' a child of '''<tt>cannonBox</tt>'''. Because nothing else is in the box, the effect is that the [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] will put a frame around the '''<tt>CannonField</tt>'''. We put '''<tt>cannonBox</tt>''', not '''<tt>CannonField</tt>''', in the grid layout.

=== Running the Application ===

The cannon now shoots when you press Enter. You can also position the cannon's angle using the mouse. The barrier makes it a little more challenging to play the game. We also have a nice looking frame around the '''<tt>CannonField</tt>'''.

=== Exercises ===

Write a space invaders game.

The new exercise is: Write a Breakout game.

Final exhortation: Go forth now and create masterpieces of the programming art!

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/52/fi

2011-11-01T17:32:19Z

Centerlink: Created page with "Category:Ruby"

[[Category:Ruby]]

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/fi

2011-11-01T17:32:11Z

Centerlink: Created page with "=== Harjoitukset ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Peli loppui|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_14|Tutorial 14 - Facing the Wall]]
}}
== Peli loppui ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_13.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]

=== Yleiskuva ===

In this example we start to approach a real playable game with a score.

We give '''<tt>MyWidget</tt>''' a new name ('''<tt>GameBoard</tt>'''), add some slots, and move it to '''<tt>gamebrd.rb</tt>'''

The '''<tt>CannonField</tt>''' now has a game over state.

The layout problems in '''<tt>LCDRange</tt>''' are fixed.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
@label.setSizePolicy(Qt::SizePolicy::Preferred, Qt::SizePolicy::Fixed)
</syntaxhighlight>

We set the size policy of the [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] to ([http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Preferred], [http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Fixed]). The vertical component ensures that the label won't stretch or shrink vertically; it will stay at its optimal size (its [http://doc.qt.nokia.com/latest/qwidget.html#sizeHint-prop QWidget::sizeHint()]). This solves the layout problems observed in Chapter 12.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has a game over state and a few new functions.

<syntaxhighlight lang="ruby">
signals 'canShoot(bool)'
</syntaxhighlight>

This new signal indicates that the '''<tt>CannonField</tt>''' is in a state where the '''<tt>shoot()</tt>''' slot makes sense. We'll use it below to enable or disable the Shoot button.

<syntaxhighlight lang="ruby">
@gameEnded = false
</syntaxhighlight>

This variable contains the game state; '''<tt>true</tt>''' means that the game is over, and '''<tt>false</tt>''' means that a game is going on. Initially, the game is not over (luckily for the player :-).

<syntaxhighlight lang="ruby">
def shoot()
if isShooting()
return
end

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
emit canShoot(false)
end
</syntaxhighlight>

We added a new '''<tt>isShooting()</tt>''' function, so '''<tt>shoot()</tt>''' uses it instead of testing directly. Also, shoot tells the world that the '''<tt>CannonField</tt>''' cannot shoot now.

<syntaxhighlight lang="ruby">
def setGameOver()
if @gameEnded
return
end

if isShooting()
@autoShootTimer.stop()
end

@gameEnded = true
update()
end
</syntaxhighlight>

This slot ends the game. It must be called from outside '''<tt>CannonField</tt>''', because this widget does not know when to end the game. This is an important design principle in component programming. We choose to make the component as flexible as possible to make it usable with different rules (for example, a multi-player version of this in which the first player to hit ten times wins could use the '''<tt>CannonField</tt>''' unchanged).

If the game has already been ended we return immediately. If a game is going on we stop the shot, set the game over flag, and repaint the entire widget.

<syntaxhighlight lang="ruby">
def restartGame()
if isShooting()
@autoShootTimer.stop()
end

@gameEnded = false

update()
emit canShoot(true)
end
</syntaxhighlight>

This slot starts a new game. If a shot is in the air, we stop shooting. We then reset the '''<tt>gameEnded</tt>''' variable and repaint the widget.

'''<tt>moveShot()</tt>''' too emits the new '''<tt>canShoot(true)</tt>''' signal at the same time as either '''<tt>hit()</tt>''' or '''<tt>miss()</tt>'''.

Modifications in CannonField::paintEvent():

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

if @gameEnded
painter.setPen(Qt::black)
painter.setFont(Qt::Font.new( "Courier", 48, Qt::Font::Bold))
painter.drawText(rect(), Qt::AlignCenter, tr("Game Over"))
end
</syntaxhighlight>

The paint event has been enhanced to display the text "Game Over" if the game is over, i.e., '''<tt>gameEnded</tt>''' is '''<tt>true</tt>'''. We don't bother to check the update rectangle here because speed is not critical when the game is over.

To draw the text we first set a black pen; the pen color is used when drawing text. Next we choose a 48 point bold font from the Courier family. Finally we draw the text centered in the widget's rectangle. Unfortunately, on some systems (especially X servers with Unicode fonts) it can take a while to load such a large font. Because Qt caches fonts, you will notice this only the first time the font is used.

<syntaxhighlight lang="ruby">
paintCannon(painter)

if isShooting()
paintShot(painter)
end

unless @gameEnded
paintTarget(painter)
end

painter.end()
end
</syntaxhighlight>

We draw the shot only when shooting and the target only when playing (that is, when the game is not ended).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]'''

This file is new. It contains the '''<tt>GameBoard</tt>''' class, which was last seen as '''<tt>MyWidget</tt>'''.

<syntaxhighlight lang="ruby">
slots 'fire()', 'hit()', 'missed()', 'newGame()'
</syntaxhighlight>

We have now added four slots.

We have also made some changes in the '''<tt>GameBoard</tt>''' constructor.

<syntaxhighlight lang="ruby">
@cannonField = CannonField.new()
</syntaxhighlight>

'''<tt>@cannonField</tt>''' is now a member variable, so we carefully change the constructor to use it.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('hit()'),
self, SLOT('hit()'))
connect(@cannonField, SIGNAL('missed()'),
self, SLOT('missed()'))
</syntaxhighlight>

This time we want to do something when the shot has hit or missed the target. Thus we connect the '''<tt>hit()</tt>''' and '''<tt>missed()</tt>''' signals of the '''<tt>CannonField</tt>''' to two protected slots with the same names in this class.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), self, SLOT('fire()') )
</syntaxhighlight>

Previously we connected the Shoot button's '''<tt>clicked()</tt>''' signal directly to the '''<tt>CannonField</tt>''''s '''<tt>shoot()</tt>''' slot. This time we want to keep track of the number of shots fired, so we connect it to a slot in this class instead.

Notice how easy it is to change the behavior of a program when you are working with self-contained components.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('canShoot(bool)'),
shoot, SLOT('setEnabled(bool)'))
</syntaxhighlight>

We also use the '''<tt>CannonField</tt>''''s '''<tt>canShoot()</tt>''' signal to enable or disable the Shoot button appropriately.

<syntaxhighlight lang="ruby">
restart = Qt::PushButton.new(tr('&New Game'))
restart.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))

connect(restart, SIGNAL('clicked()'), self, SLOT('newGame()'))
</syntaxhighlight>

We create, set up, and connect the New Game button as we have done with the other buttons. Clicking this button will activate the '''<tt>newGame()</tt>''' slot in this widget.

<syntaxhighlight lang="ruby">
@hits = Qt::LCDNumber.new(2)
@shotsLeft = Qt::LCDNumber.new(2)
hitsLabel = Qt::Label.new(tr('HITS'))
shotsLeftLabel = Qt::Label.new(tr('SHOTS LEFT'))
</syntaxhighlight>

We create four new widgets, to display the number of hits and shots left.

<syntaxhighlight lang="ruby">
topLayout = Qt::HBoxLayout.new()
topLayout.addWidget(shoot)
topLayout.addWidget(@hits)
topLayout.addWidget(hitsLabel)
topLayout.addWidget(@shotsLeft)
topLayout.addWidget(shotsLeftLabel)
topLayout.addStretch(1)
topLayout.addWidget(restart)
</syntaxhighlight>

The top-right cell of the [http://doc.qt.nokia.com/latest/qgridlayout.html Qt::GridLayout] is starting to get crowded. We put a stretch just to the left of the New Game button to ensure that this button will always appear on the right side of the window.

<syntaxhighlight lang="ruby">
newGame()
</syntaxhighlight>

We're all done constructing the '''<tt>GameBoard</tt>''', so we start it all using '''<tt>newGame()</tt>'''. Although '''<tt>newGame()</tt>''' is a slot, it can also be used as an ordinary function.

<syntaxhighlight lang="ruby">
def fire()
if @cannonField.gameOver() || @cannonField.isShooting()
return
end

@shotsLeft.display(@shotsLeft.intValue() - 1)
@cannonField.shoot()
end
</syntaxhighlight>

This function fires a shot. If the game is over or if there is a shot in the air, we return immediately. We decrement the number of shots left and tell the cannon to shoot.

<syntaxhighlight lang="ruby">
def hit()
@hits.display(@hits.intValue() + 1)

if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
else
@cannonField.newTarget()
end
end
</syntaxhighlight>

This slot is activated when a shot has hit the target. We increment the number of hits. If there are no shots left, the game is over. Otherwise, we make the '''<tt>CannonField</tt>''' generate a new target.

<syntaxhighlight lang="ruby">
def missed()
if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
end
end
</syntaxhighlight>

This slot is activated when a shot has missed the target. If there are no shots left, the game is over.

<syntaxhighlight lang="ruby">
def newGame()
@shotsLeft.display(15)
@hits.display(0)
@cannonField.restartGame()
@cannonField.newTarget()
end
</syntaxhighlight>

This slot is activated when the user clicks the New Game button. It is also called from the constructor. First it sets the number of shots to 15. Note that this is the only place in the program where we set the number of shots. Change it to whatever you like to change the game rules. Next we reset the number of hits, restart the game, and generate a new target.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]'''

This file has just been on a diet. '''<tt>MyWidget</tt>''' is gone, and the only thing left is the '''<tt>main()</tt>''' function, unchanged except for the name change.

=== Sovelluksen suorittaminen ===

The cannon can shoot at a target; a new target is automatically created when one has been hit.

Hits and shots left are displayed and the program keeps track of them. The game can end, and there's a button to start a new game.

=== Harjoitukset ===

Add a random wind factor and show it to the user.

Make some splatter effects when the shot hits the target.

Implement multiple targets.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/48/fi

2011-11-01T17:32:11Z

Centerlink: Created page with "=== Harjoitukset ==="

=== Harjoitukset ===

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/fi

2011-11-01T17:32:00Z

Centerlink: Created page with "=== Sovelluksen suorittaminen ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Peli loppui|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_14|Tutorial 14 - Facing the Wall]]
}}
== Peli loppui ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_13.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]

=== Yleiskuva ===

In this example we start to approach a real playable game with a score.

We give '''<tt>MyWidget</tt>''' a new name ('''<tt>GameBoard</tt>'''), add some slots, and move it to '''<tt>gamebrd.rb</tt>'''

The '''<tt>CannonField</tt>''' now has a game over state.

The layout problems in '''<tt>LCDRange</tt>''' are fixed.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
@label.setSizePolicy(Qt::SizePolicy::Preferred, Qt::SizePolicy::Fixed)
</syntaxhighlight>

We set the size policy of the [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] to ([http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Preferred], [http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Fixed]). The vertical component ensures that the label won't stretch or shrink vertically; it will stay at its optimal size (its [http://doc.qt.nokia.com/latest/qwidget.html#sizeHint-prop QWidget::sizeHint()]). This solves the layout problems observed in Chapter 12.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has a game over state and a few new functions.

<syntaxhighlight lang="ruby">
signals 'canShoot(bool)'
</syntaxhighlight>

This new signal indicates that the '''<tt>CannonField</tt>''' is in a state where the '''<tt>shoot()</tt>''' slot makes sense. We'll use it below to enable or disable the Shoot button.

<syntaxhighlight lang="ruby">
@gameEnded = false
</syntaxhighlight>

This variable contains the game state; '''<tt>true</tt>''' means that the game is over, and '''<tt>false</tt>''' means that a game is going on. Initially, the game is not over (luckily for the player :-).

<syntaxhighlight lang="ruby">
def shoot()
if isShooting()
return
end

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
emit canShoot(false)
end
</syntaxhighlight>

We added a new '''<tt>isShooting()</tt>''' function, so '''<tt>shoot()</tt>''' uses it instead of testing directly. Also, shoot tells the world that the '''<tt>CannonField</tt>''' cannot shoot now.

<syntaxhighlight lang="ruby">
def setGameOver()
if @gameEnded
return
end

if isShooting()
@autoShootTimer.stop()
end

@gameEnded = true
update()
end
</syntaxhighlight>

This slot ends the game. It must be called from outside '''<tt>CannonField</tt>''', because this widget does not know when to end the game. This is an important design principle in component programming. We choose to make the component as flexible as possible to make it usable with different rules (for example, a multi-player version of this in which the first player to hit ten times wins could use the '''<tt>CannonField</tt>''' unchanged).

If the game has already been ended we return immediately. If a game is going on we stop the shot, set the game over flag, and repaint the entire widget.

<syntaxhighlight lang="ruby">
def restartGame()
if isShooting()
@autoShootTimer.stop()
end

@gameEnded = false

update()
emit canShoot(true)
end
</syntaxhighlight>

This slot starts a new game. If a shot is in the air, we stop shooting. We then reset the '''<tt>gameEnded</tt>''' variable and repaint the widget.

'''<tt>moveShot()</tt>''' too emits the new '''<tt>canShoot(true)</tt>''' signal at the same time as either '''<tt>hit()</tt>''' or '''<tt>miss()</tt>'''.

Modifications in CannonField::paintEvent():

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

if @gameEnded
painter.setPen(Qt::black)
painter.setFont(Qt::Font.new( "Courier", 48, Qt::Font::Bold))
painter.drawText(rect(), Qt::AlignCenter, tr("Game Over"))
end
</syntaxhighlight>

The paint event has been enhanced to display the text "Game Over" if the game is over, i.e., '''<tt>gameEnded</tt>''' is '''<tt>true</tt>'''. We don't bother to check the update rectangle here because speed is not critical when the game is over.

To draw the text we first set a black pen; the pen color is used when drawing text. Next we choose a 48 point bold font from the Courier family. Finally we draw the text centered in the widget's rectangle. Unfortunately, on some systems (especially X servers with Unicode fonts) it can take a while to load such a large font. Because Qt caches fonts, you will notice this only the first time the font is used.

<syntaxhighlight lang="ruby">
paintCannon(painter)

if isShooting()
paintShot(painter)
end

unless @gameEnded
paintTarget(painter)
end

painter.end()
end
</syntaxhighlight>

We draw the shot only when shooting and the target only when playing (that is, when the game is not ended).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]'''

This file is new. It contains the '''<tt>GameBoard</tt>''' class, which was last seen as '''<tt>MyWidget</tt>'''.

<syntaxhighlight lang="ruby">
slots 'fire()', 'hit()', 'missed()', 'newGame()'
</syntaxhighlight>

We have now added four slots.

We have also made some changes in the '''<tt>GameBoard</tt>''' constructor.

<syntaxhighlight lang="ruby">
@cannonField = CannonField.new()
</syntaxhighlight>

'''<tt>@cannonField</tt>''' is now a member variable, so we carefully change the constructor to use it.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('hit()'),
self, SLOT('hit()'))
connect(@cannonField, SIGNAL('missed()'),
self, SLOT('missed()'))
</syntaxhighlight>

This time we want to do something when the shot has hit or missed the target. Thus we connect the '''<tt>hit()</tt>''' and '''<tt>missed()</tt>''' signals of the '''<tt>CannonField</tt>''' to two protected slots with the same names in this class.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), self, SLOT('fire()') )
</syntaxhighlight>

Previously we connected the Shoot button's '''<tt>clicked()</tt>''' signal directly to the '''<tt>CannonField</tt>''''s '''<tt>shoot()</tt>''' slot. This time we want to keep track of the number of shots fired, so we connect it to a slot in this class instead.

Notice how easy it is to change the behavior of a program when you are working with self-contained components.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('canShoot(bool)'),
shoot, SLOT('setEnabled(bool)'))
</syntaxhighlight>

We also use the '''<tt>CannonField</tt>''''s '''<tt>canShoot()</tt>''' signal to enable or disable the Shoot button appropriately.

<syntaxhighlight lang="ruby">
restart = Qt::PushButton.new(tr('&New Game'))
restart.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))

connect(restart, SIGNAL('clicked()'), self, SLOT('newGame()'))
</syntaxhighlight>

We create, set up, and connect the New Game button as we have done with the other buttons. Clicking this button will activate the '''<tt>newGame()</tt>''' slot in this widget.

<syntaxhighlight lang="ruby">
@hits = Qt::LCDNumber.new(2)
@shotsLeft = Qt::LCDNumber.new(2)
hitsLabel = Qt::Label.new(tr('HITS'))
shotsLeftLabel = Qt::Label.new(tr('SHOTS LEFT'))
</syntaxhighlight>

We create four new widgets, to display the number of hits and shots left.

<syntaxhighlight lang="ruby">
topLayout = Qt::HBoxLayout.new()
topLayout.addWidget(shoot)
topLayout.addWidget(@hits)
topLayout.addWidget(hitsLabel)
topLayout.addWidget(@shotsLeft)
topLayout.addWidget(shotsLeftLabel)
topLayout.addStretch(1)
topLayout.addWidget(restart)
</syntaxhighlight>

The top-right cell of the [http://doc.qt.nokia.com/latest/qgridlayout.html Qt::GridLayout] is starting to get crowded. We put a stretch just to the left of the New Game button to ensure that this button will always appear on the right side of the window.

<syntaxhighlight lang="ruby">
newGame()
</syntaxhighlight>

We're all done constructing the '''<tt>GameBoard</tt>''', so we start it all using '''<tt>newGame()</tt>'''. Although '''<tt>newGame()</tt>''' is a slot, it can also be used as an ordinary function.

<syntaxhighlight lang="ruby">
def fire()
if @cannonField.gameOver() || @cannonField.isShooting()
return
end

@shotsLeft.display(@shotsLeft.intValue() - 1)
@cannonField.shoot()
end
</syntaxhighlight>

This function fires a shot. If the game is over or if there is a shot in the air, we return immediately. We decrement the number of shots left and tell the cannon to shoot.

<syntaxhighlight lang="ruby">
def hit()
@hits.display(@hits.intValue() + 1)

if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
else
@cannonField.newTarget()
end
end
</syntaxhighlight>

This slot is activated when a shot has hit the target. We increment the number of hits. If there are no shots left, the game is over. Otherwise, we make the '''<tt>CannonField</tt>''' generate a new target.

<syntaxhighlight lang="ruby">
def missed()
if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
end
end
</syntaxhighlight>

This slot is activated when a shot has missed the target. If there are no shots left, the game is over.

<syntaxhighlight lang="ruby">
def newGame()
@shotsLeft.display(15)
@hits.display(0)
@cannonField.restartGame()
@cannonField.newTarget()
end
</syntaxhighlight>

This slot is activated when the user clicks the New Game button. It is also called from the constructor. First it sets the number of shots to 15. Note that this is the only place in the program where we set the number of shots. Change it to whatever you like to change the game rules. Next we reset the number of hits, restart the game, and generate a new target.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]'''

This file has just been on a diet. '''<tt>MyWidget</tt>''' is gone, and the only thing left is the '''<tt>main()</tt>''' function, unchanged except for the name change.

=== Sovelluksen suorittaminen ===

The cannon can shoot at a target; a new target is automatically created when one has been hit.

Hits and shots left are displayed and the program keeps track of them. The game can end, and there's a button to start a new game.

=== Exercises ===

Add a random wind factor and show it to the user.

Make some splatter effects when the shot hits the target.

Implement multiple targets.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/45/fi

2011-11-01T17:31:59Z

Centerlink: Created page with "=== Sovelluksen suorittaminen ==="

=== Sovelluksen suorittaminen ===

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/fi

2011-11-01T17:31:37Z

Centerlink: Created page with "=== Läpikäynti rivi riviltä ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Peli loppui|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_14|Tutorial 14 - Facing the Wall]]
}}
== Peli loppui ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_13.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]

=== Yleiskuva ===

In this example we start to approach a real playable game with a score.

We give '''<tt>MyWidget</tt>''' a new name ('''<tt>GameBoard</tt>'''), add some slots, and move it to '''<tt>gamebrd.rb</tt>'''

The '''<tt>CannonField</tt>''' now has a game over state.

The layout problems in '''<tt>LCDRange</tt>''' are fixed.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
@label.setSizePolicy(Qt::SizePolicy::Preferred, Qt::SizePolicy::Fixed)
</syntaxhighlight>

We set the size policy of the [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] to ([http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Preferred], [http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Fixed]). The vertical component ensures that the label won't stretch or shrink vertically; it will stay at its optimal size (its [http://doc.qt.nokia.com/latest/qwidget.html#sizeHint-prop QWidget::sizeHint()]). This solves the layout problems observed in Chapter 12.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has a game over state and a few new functions.

<syntaxhighlight lang="ruby">
signals 'canShoot(bool)'
</syntaxhighlight>

This new signal indicates that the '''<tt>CannonField</tt>''' is in a state where the '''<tt>shoot()</tt>''' slot makes sense. We'll use it below to enable or disable the Shoot button.

<syntaxhighlight lang="ruby">
@gameEnded = false
</syntaxhighlight>

This variable contains the game state; '''<tt>true</tt>''' means that the game is over, and '''<tt>false</tt>''' means that a game is going on. Initially, the game is not over (luckily for the player :-).

<syntaxhighlight lang="ruby">
def shoot()
if isShooting()
return
end

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
emit canShoot(false)
end
</syntaxhighlight>

We added a new '''<tt>isShooting()</tt>''' function, so '''<tt>shoot()</tt>''' uses it instead of testing directly. Also, shoot tells the world that the '''<tt>CannonField</tt>''' cannot shoot now.

<syntaxhighlight lang="ruby">
def setGameOver()
if @gameEnded
return
end

if isShooting()
@autoShootTimer.stop()
end

@gameEnded = true
update()
end
</syntaxhighlight>

This slot ends the game. It must be called from outside '''<tt>CannonField</tt>''', because this widget does not know when to end the game. This is an important design principle in component programming. We choose to make the component as flexible as possible to make it usable with different rules (for example, a multi-player version of this in which the first player to hit ten times wins could use the '''<tt>CannonField</tt>''' unchanged).

If the game has already been ended we return immediately. If a game is going on we stop the shot, set the game over flag, and repaint the entire widget.

<syntaxhighlight lang="ruby">
def restartGame()
if isShooting()
@autoShootTimer.stop()
end

@gameEnded = false

update()
emit canShoot(true)
end
</syntaxhighlight>

This slot starts a new game. If a shot is in the air, we stop shooting. We then reset the '''<tt>gameEnded</tt>''' variable and repaint the widget.

'''<tt>moveShot()</tt>''' too emits the new '''<tt>canShoot(true)</tt>''' signal at the same time as either '''<tt>hit()</tt>''' or '''<tt>miss()</tt>'''.

Modifications in CannonField::paintEvent():

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

if @gameEnded
painter.setPen(Qt::black)
painter.setFont(Qt::Font.new( "Courier", 48, Qt::Font::Bold))
painter.drawText(rect(), Qt::AlignCenter, tr("Game Over"))
end
</syntaxhighlight>

The paint event has been enhanced to display the text "Game Over" if the game is over, i.e., '''<tt>gameEnded</tt>''' is '''<tt>true</tt>'''. We don't bother to check the update rectangle here because speed is not critical when the game is over.

To draw the text we first set a black pen; the pen color is used when drawing text. Next we choose a 48 point bold font from the Courier family. Finally we draw the text centered in the widget's rectangle. Unfortunately, on some systems (especially X servers with Unicode fonts) it can take a while to load such a large font. Because Qt caches fonts, you will notice this only the first time the font is used.

<syntaxhighlight lang="ruby">
paintCannon(painter)

if isShooting()
paintShot(painter)
end

unless @gameEnded
paintTarget(painter)
end

painter.end()
end
</syntaxhighlight>

We draw the shot only when shooting and the target only when playing (that is, when the game is not ended).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]'''

This file is new. It contains the '''<tt>GameBoard</tt>''' class, which was last seen as '''<tt>MyWidget</tt>'''.

<syntaxhighlight lang="ruby">
slots 'fire()', 'hit()', 'missed()', 'newGame()'
</syntaxhighlight>

We have now added four slots.

We have also made some changes in the '''<tt>GameBoard</tt>''' constructor.

<syntaxhighlight lang="ruby">
@cannonField = CannonField.new()
</syntaxhighlight>

'''<tt>@cannonField</tt>''' is now a member variable, so we carefully change the constructor to use it.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('hit()'),
self, SLOT('hit()'))
connect(@cannonField, SIGNAL('missed()'),
self, SLOT('missed()'))
</syntaxhighlight>

This time we want to do something when the shot has hit or missed the target. Thus we connect the '''<tt>hit()</tt>''' and '''<tt>missed()</tt>''' signals of the '''<tt>CannonField</tt>''' to two protected slots with the same names in this class.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), self, SLOT('fire()') )
</syntaxhighlight>

Previously we connected the Shoot button's '''<tt>clicked()</tt>''' signal directly to the '''<tt>CannonField</tt>''''s '''<tt>shoot()</tt>''' slot. This time we want to keep track of the number of shots fired, so we connect it to a slot in this class instead.

Notice how easy it is to change the behavior of a program when you are working with self-contained components.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('canShoot(bool)'),
shoot, SLOT('setEnabled(bool)'))
</syntaxhighlight>

We also use the '''<tt>CannonField</tt>''''s '''<tt>canShoot()</tt>''' signal to enable or disable the Shoot button appropriately.

<syntaxhighlight lang="ruby">
restart = Qt::PushButton.new(tr('&New Game'))
restart.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))

connect(restart, SIGNAL('clicked()'), self, SLOT('newGame()'))
</syntaxhighlight>

We create, set up, and connect the New Game button as we have done with the other buttons. Clicking this button will activate the '''<tt>newGame()</tt>''' slot in this widget.

<syntaxhighlight lang="ruby">
@hits = Qt::LCDNumber.new(2)
@shotsLeft = Qt::LCDNumber.new(2)
hitsLabel = Qt::Label.new(tr('HITS'))
shotsLeftLabel = Qt::Label.new(tr('SHOTS LEFT'))
</syntaxhighlight>

We create four new widgets, to display the number of hits and shots left.

<syntaxhighlight lang="ruby">
topLayout = Qt::HBoxLayout.new()
topLayout.addWidget(shoot)
topLayout.addWidget(@hits)
topLayout.addWidget(hitsLabel)
topLayout.addWidget(@shotsLeft)
topLayout.addWidget(shotsLeftLabel)
topLayout.addStretch(1)
topLayout.addWidget(restart)
</syntaxhighlight>

The top-right cell of the [http://doc.qt.nokia.com/latest/qgridlayout.html Qt::GridLayout] is starting to get crowded. We put a stretch just to the left of the New Game button to ensure that this button will always appear on the right side of the window.

<syntaxhighlight lang="ruby">
newGame()
</syntaxhighlight>

We're all done constructing the '''<tt>GameBoard</tt>''', so we start it all using '''<tt>newGame()</tt>'''. Although '''<tt>newGame()</tt>''' is a slot, it can also be used as an ordinary function.

<syntaxhighlight lang="ruby">
def fire()
if @cannonField.gameOver() || @cannonField.isShooting()
return
end

@shotsLeft.display(@shotsLeft.intValue() - 1)
@cannonField.shoot()
end
</syntaxhighlight>

This function fires a shot. If the game is over or if there is a shot in the air, we return immediately. We decrement the number of shots left and tell the cannon to shoot.

<syntaxhighlight lang="ruby">
def hit()
@hits.display(@hits.intValue() + 1)

if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
else
@cannonField.newTarget()
end
end
</syntaxhighlight>

This slot is activated when a shot has hit the target. We increment the number of hits. If there are no shots left, the game is over. Otherwise, we make the '''<tt>CannonField</tt>''' generate a new target.

<syntaxhighlight lang="ruby">
def missed()
if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
end
end
</syntaxhighlight>

This slot is activated when a shot has missed the target. If there are no shots left, the game is over.

<syntaxhighlight lang="ruby">
def newGame()
@shotsLeft.display(15)
@hits.display(0)
@cannonField.restartGame()
@cannonField.newTarget()
end
</syntaxhighlight>

This slot is activated when the user clicks the New Game button. It is also called from the constructor. First it sets the number of shots to 15. Note that this is the only place in the program where we set the number of shots. Change it to whatever you like to change the game rules. Next we reset the number of hits, restart the game, and generate a new target.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]'''

This file has just been on a diet. '''<tt>MyWidget</tt>''' is gone, and the only thing left is the '''<tt>main()</tt>''' function, unchanged except for the name change.

=== Running the Application ===

The cannon can shoot at a target; a new target is automatically created when one has been hit.

Hits and shots left are displayed and the program keeps track of them. The game can end, and there's a button to start a new game.

=== Exercises ===

Add a random wind factor and show it to the user.

Make some splatter effects when the shot hits the target.

Implement multiple targets.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/14/fi

2011-11-01T17:31:37Z

Centerlink: Created page with "=== Läpikäynti rivi riviltä ==="

=== Läpikäynti rivi riviltä ===

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/fi

2011-11-01T17:31:13Z

Centerlink: Created page with "=== Yleiskuva ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Peli loppui|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_14|Tutorial 14 - Facing the Wall]]
}}
== Peli loppui ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_13.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]

=== Yleiskuva ===

In this example we start to approach a real playable game with a score.

We give '''<tt>MyWidget</tt>''' a new name ('''<tt>GameBoard</tt>'''), add some slots, and move it to '''<tt>gamebrd.rb</tt>'''

The '''<tt>CannonField</tt>''' now has a game over state.

The layout problems in '''<tt>LCDRange</tt>''' are fixed.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
@label.setSizePolicy(Qt::SizePolicy::Preferred, Qt::SizePolicy::Fixed)
</syntaxhighlight>

We set the size policy of the [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] to ([http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Preferred], [http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Fixed]). The vertical component ensures that the label won't stretch or shrink vertically; it will stay at its optimal size (its [http://doc.qt.nokia.com/latest/qwidget.html#sizeHint-prop QWidget::sizeHint()]). This solves the layout problems observed in Chapter 12.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has a game over state and a few new functions.

<syntaxhighlight lang="ruby">
signals 'canShoot(bool)'
</syntaxhighlight>

This new signal indicates that the '''<tt>CannonField</tt>''' is in a state where the '''<tt>shoot()</tt>''' slot makes sense. We'll use it below to enable or disable the Shoot button.

<syntaxhighlight lang="ruby">
@gameEnded = false
</syntaxhighlight>

This variable contains the game state; '''<tt>true</tt>''' means that the game is over, and '''<tt>false</tt>''' means that a game is going on. Initially, the game is not over (luckily for the player :-).

<syntaxhighlight lang="ruby">
def shoot()
if isShooting()
return
end

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
emit canShoot(false)
end
</syntaxhighlight>

We added a new '''<tt>isShooting()</tt>''' function, so '''<tt>shoot()</tt>''' uses it instead of testing directly. Also, shoot tells the world that the '''<tt>CannonField</tt>''' cannot shoot now.

<syntaxhighlight lang="ruby">
def setGameOver()
if @gameEnded
return
end

if isShooting()
@autoShootTimer.stop()
end

@gameEnded = true
update()
end
</syntaxhighlight>

This slot ends the game. It must be called from outside '''<tt>CannonField</tt>''', because this widget does not know when to end the game. This is an important design principle in component programming. We choose to make the component as flexible as possible to make it usable with different rules (for example, a multi-player version of this in which the first player to hit ten times wins could use the '''<tt>CannonField</tt>''' unchanged).

If the game has already been ended we return immediately. If a game is going on we stop the shot, set the game over flag, and repaint the entire widget.

<syntaxhighlight lang="ruby">
def restartGame()
if isShooting()
@autoShootTimer.stop()
end

@gameEnded = false

update()
emit canShoot(true)
end
</syntaxhighlight>

This slot starts a new game. If a shot is in the air, we stop shooting. We then reset the '''<tt>gameEnded</tt>''' variable and repaint the widget.

'''<tt>moveShot()</tt>''' too emits the new '''<tt>canShoot(true)</tt>''' signal at the same time as either '''<tt>hit()</tt>''' or '''<tt>miss()</tt>'''.

Modifications in CannonField::paintEvent():

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

if @gameEnded
painter.setPen(Qt::black)
painter.setFont(Qt::Font.new( "Courier", 48, Qt::Font::Bold))
painter.drawText(rect(), Qt::AlignCenter, tr("Game Over"))
end
</syntaxhighlight>

The paint event has been enhanced to display the text "Game Over" if the game is over, i.e., '''<tt>gameEnded</tt>''' is '''<tt>true</tt>'''. We don't bother to check the update rectangle here because speed is not critical when the game is over.

To draw the text we first set a black pen; the pen color is used when drawing text. Next we choose a 48 point bold font from the Courier family. Finally we draw the text centered in the widget's rectangle. Unfortunately, on some systems (especially X servers with Unicode fonts) it can take a while to load such a large font. Because Qt caches fonts, you will notice this only the first time the font is used.

<syntaxhighlight lang="ruby">
paintCannon(painter)

if isShooting()
paintShot(painter)
end

unless @gameEnded
paintTarget(painter)
end

painter.end()
end
</syntaxhighlight>

We draw the shot only when shooting and the target only when playing (that is, when the game is not ended).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]'''

This file is new. It contains the '''<tt>GameBoard</tt>''' class, which was last seen as '''<tt>MyWidget</tt>'''.

<syntaxhighlight lang="ruby">
slots 'fire()', 'hit()', 'missed()', 'newGame()'
</syntaxhighlight>

We have now added four slots.

We have also made some changes in the '''<tt>GameBoard</tt>''' constructor.

<syntaxhighlight lang="ruby">
@cannonField = CannonField.new()
</syntaxhighlight>

'''<tt>@cannonField</tt>''' is now a member variable, so we carefully change the constructor to use it.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('hit()'),
self, SLOT('hit()'))
connect(@cannonField, SIGNAL('missed()'),
self, SLOT('missed()'))
</syntaxhighlight>

This time we want to do something when the shot has hit or missed the target. Thus we connect the '''<tt>hit()</tt>''' and '''<tt>missed()</tt>''' signals of the '''<tt>CannonField</tt>''' to two protected slots with the same names in this class.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), self, SLOT('fire()') )
</syntaxhighlight>

Previously we connected the Shoot button's '''<tt>clicked()</tt>''' signal directly to the '''<tt>CannonField</tt>''''s '''<tt>shoot()</tt>''' slot. This time we want to keep track of the number of shots fired, so we connect it to a slot in this class instead.

Notice how easy it is to change the behavior of a program when you are working with self-contained components.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('canShoot(bool)'),
shoot, SLOT('setEnabled(bool)'))
</syntaxhighlight>

We also use the '''<tt>CannonField</tt>''''s '''<tt>canShoot()</tt>''' signal to enable or disable the Shoot button appropriately.

<syntaxhighlight lang="ruby">
restart = Qt::PushButton.new(tr('&New Game'))
restart.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))

connect(restart, SIGNAL('clicked()'), self, SLOT('newGame()'))
</syntaxhighlight>

We create, set up, and connect the New Game button as we have done with the other buttons. Clicking this button will activate the '''<tt>newGame()</tt>''' slot in this widget.

<syntaxhighlight lang="ruby">
@hits = Qt::LCDNumber.new(2)
@shotsLeft = Qt::LCDNumber.new(2)
hitsLabel = Qt::Label.new(tr('HITS'))
shotsLeftLabel = Qt::Label.new(tr('SHOTS LEFT'))
</syntaxhighlight>

We create four new widgets, to display the number of hits and shots left.

<syntaxhighlight lang="ruby">
topLayout = Qt::HBoxLayout.new()
topLayout.addWidget(shoot)
topLayout.addWidget(@hits)
topLayout.addWidget(hitsLabel)
topLayout.addWidget(@shotsLeft)
topLayout.addWidget(shotsLeftLabel)
topLayout.addStretch(1)
topLayout.addWidget(restart)
</syntaxhighlight>

The top-right cell of the [http://doc.qt.nokia.com/latest/qgridlayout.html Qt::GridLayout] is starting to get crowded. We put a stretch just to the left of the New Game button to ensure that this button will always appear on the right side of the window.

<syntaxhighlight lang="ruby">
newGame()
</syntaxhighlight>

We're all done constructing the '''<tt>GameBoard</tt>''', so we start it all using '''<tt>newGame()</tt>'''. Although '''<tt>newGame()</tt>''' is a slot, it can also be used as an ordinary function.

<syntaxhighlight lang="ruby">
def fire()
if @cannonField.gameOver() || @cannonField.isShooting()
return
end

@shotsLeft.display(@shotsLeft.intValue() - 1)
@cannonField.shoot()
end
</syntaxhighlight>

This function fires a shot. If the game is over or if there is a shot in the air, we return immediately. We decrement the number of shots left and tell the cannon to shoot.

<syntaxhighlight lang="ruby">
def hit()
@hits.display(@hits.intValue() + 1)

if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
else
@cannonField.newTarget()
end
end
</syntaxhighlight>

This slot is activated when a shot has hit the target. We increment the number of hits. If there are no shots left, the game is over. Otherwise, we make the '''<tt>CannonField</tt>''' generate a new target.

<syntaxhighlight lang="ruby">
def missed()
if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
end
end
</syntaxhighlight>

This slot is activated when a shot has missed the target. If there are no shots left, the game is over.

<syntaxhighlight lang="ruby">
def newGame()
@shotsLeft.display(15)
@hits.display(0)
@cannonField.restartGame()
@cannonField.newTarget()
end
</syntaxhighlight>

This slot is activated when the user clicks the New Game button. It is also called from the constructor. First it sets the number of shots to 15. Note that this is the only place in the program where we set the number of shots. Change it to whatever you like to change the game rules. Next we reset the number of hits, restart the game, and generate a new target.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]'''

This file has just been on a diet. '''<tt>MyWidget</tt>''' is gone, and the only thing left is the '''<tt>main()</tt>''' function, unchanged except for the name change.

=== Running the Application ===

The cannon can shoot at a target; a new target is automatically created when one has been hit.

Hits and shots left are displayed and the program keeps track of them. The game can end, and there's a button to start a new game.

=== Exercises ===

Add a random wind factor and show it to the user.

Make some splatter effects when the shot hits the target.

Implement multiple targets.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/9/fi

2011-11-01T17:31:13Z

Centerlink: Created page with "=== Yleiskuva ==="

=== Yleiskuva ===

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/7/fi

2011-11-01T17:31:02Z

Centerlink: Created page with "center"

[[Image:Qt4_Ruby_Tutorial_Screenshot_13.png|center]]

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/fi

2011-11-01T17:30:53Z

Centerlink: Created page with "== Peli loppui =="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Peli loppui|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_14|Tutorial 14 - Facing the Wall]]
}}
== Peli loppui ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_13.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]

=== Overview ===

In this example we start to approach a real playable game with a score.

We give '''<tt>MyWidget</tt>''' a new name ('''<tt>GameBoard</tt>'''), add some slots, and move it to '''<tt>gamebrd.rb</tt>'''

The '''<tt>CannonField</tt>''' now has a game over state.

The layout problems in '''<tt>LCDRange</tt>''' are fixed.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
@label.setSizePolicy(Qt::SizePolicy::Preferred, Qt::SizePolicy::Fixed)
</syntaxhighlight>

We set the size policy of the [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] to ([http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Preferred], [http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Fixed]). The vertical component ensures that the label won't stretch or shrink vertically; it will stay at its optimal size (its [http://doc.qt.nokia.com/latest/qwidget.html#sizeHint-prop QWidget::sizeHint()]). This solves the layout problems observed in Chapter 12.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has a game over state and a few new functions.

<syntaxhighlight lang="ruby">
signals 'canShoot(bool)'
</syntaxhighlight>

This new signal indicates that the '''<tt>CannonField</tt>''' is in a state where the '''<tt>shoot()</tt>''' slot makes sense. We'll use it below to enable or disable the Shoot button.

<syntaxhighlight lang="ruby">
@gameEnded = false
</syntaxhighlight>

This variable contains the game state; '''<tt>true</tt>''' means that the game is over, and '''<tt>false</tt>''' means that a game is going on. Initially, the game is not over (luckily for the player :-).

<syntaxhighlight lang="ruby">
def shoot()
if isShooting()
return
end

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
emit canShoot(false)
end
</syntaxhighlight>

We added a new '''<tt>isShooting()</tt>''' function, so '''<tt>shoot()</tt>''' uses it instead of testing directly. Also, shoot tells the world that the '''<tt>CannonField</tt>''' cannot shoot now.

<syntaxhighlight lang="ruby">
def setGameOver()
if @gameEnded
return
end

if isShooting()
@autoShootTimer.stop()
end

@gameEnded = true
update()
end
</syntaxhighlight>

This slot ends the game. It must be called from outside '''<tt>CannonField</tt>''', because this widget does not know when to end the game. This is an important design principle in component programming. We choose to make the component as flexible as possible to make it usable with different rules (for example, a multi-player version of this in which the first player to hit ten times wins could use the '''<tt>CannonField</tt>''' unchanged).

If the game has already been ended we return immediately. If a game is going on we stop the shot, set the game over flag, and repaint the entire widget.

<syntaxhighlight lang="ruby">
def restartGame()
if isShooting()
@autoShootTimer.stop()
end

@gameEnded = false

update()
emit canShoot(true)
end
</syntaxhighlight>

This slot starts a new game. If a shot is in the air, we stop shooting. We then reset the '''<tt>gameEnded</tt>''' variable and repaint the widget.

'''<tt>moveShot()</tt>''' too emits the new '''<tt>canShoot(true)</tt>''' signal at the same time as either '''<tt>hit()</tt>''' or '''<tt>miss()</tt>'''.

Modifications in CannonField::paintEvent():

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

if @gameEnded
painter.setPen(Qt::black)
painter.setFont(Qt::Font.new( "Courier", 48, Qt::Font::Bold))
painter.drawText(rect(), Qt::AlignCenter, tr("Game Over"))
end
</syntaxhighlight>

The paint event has been enhanced to display the text "Game Over" if the game is over, i.e., '''<tt>gameEnded</tt>''' is '''<tt>true</tt>'''. We don't bother to check the update rectangle here because speed is not critical when the game is over.

To draw the text we first set a black pen; the pen color is used when drawing text. Next we choose a 48 point bold font from the Courier family. Finally we draw the text centered in the widget's rectangle. Unfortunately, on some systems (especially X servers with Unicode fonts) it can take a while to load such a large font. Because Qt caches fonts, you will notice this only the first time the font is used.

<syntaxhighlight lang="ruby">
paintCannon(painter)

if isShooting()
paintShot(painter)
end

unless @gameEnded
paintTarget(painter)
end

painter.end()
end
</syntaxhighlight>

We draw the shot only when shooting and the target only when playing (that is, when the game is not ended).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]'''

This file is new. It contains the '''<tt>GameBoard</tt>''' class, which was last seen as '''<tt>MyWidget</tt>'''.

<syntaxhighlight lang="ruby">
slots 'fire()', 'hit()', 'missed()', 'newGame()'
</syntaxhighlight>

We have now added four slots.

We have also made some changes in the '''<tt>GameBoard</tt>''' constructor.

<syntaxhighlight lang="ruby">
@cannonField = CannonField.new()
</syntaxhighlight>

'''<tt>@cannonField</tt>''' is now a member variable, so we carefully change the constructor to use it.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('hit()'),
self, SLOT('hit()'))
connect(@cannonField, SIGNAL('missed()'),
self, SLOT('missed()'))
</syntaxhighlight>

This time we want to do something when the shot has hit or missed the target. Thus we connect the '''<tt>hit()</tt>''' and '''<tt>missed()</tt>''' signals of the '''<tt>CannonField</tt>''' to two protected slots with the same names in this class.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), self, SLOT('fire()') )
</syntaxhighlight>

Previously we connected the Shoot button's '''<tt>clicked()</tt>''' signal directly to the '''<tt>CannonField</tt>''''s '''<tt>shoot()</tt>''' slot. This time we want to keep track of the number of shots fired, so we connect it to a slot in this class instead.

Notice how easy it is to change the behavior of a program when you are working with self-contained components.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('canShoot(bool)'),
shoot, SLOT('setEnabled(bool)'))
</syntaxhighlight>

We also use the '''<tt>CannonField</tt>''''s '''<tt>canShoot()</tt>''' signal to enable or disable the Shoot button appropriately.

<syntaxhighlight lang="ruby">
restart = Qt::PushButton.new(tr('&New Game'))
restart.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))

connect(restart, SIGNAL('clicked()'), self, SLOT('newGame()'))
</syntaxhighlight>

We create, set up, and connect the New Game button as we have done with the other buttons. Clicking this button will activate the '''<tt>newGame()</tt>''' slot in this widget.

<syntaxhighlight lang="ruby">
@hits = Qt::LCDNumber.new(2)
@shotsLeft = Qt::LCDNumber.new(2)
hitsLabel = Qt::Label.new(tr('HITS'))
shotsLeftLabel = Qt::Label.new(tr('SHOTS LEFT'))
</syntaxhighlight>

We create four new widgets, to display the number of hits and shots left.

<syntaxhighlight lang="ruby">
topLayout = Qt::HBoxLayout.new()
topLayout.addWidget(shoot)
topLayout.addWidget(@hits)
topLayout.addWidget(hitsLabel)
topLayout.addWidget(@shotsLeft)
topLayout.addWidget(shotsLeftLabel)
topLayout.addStretch(1)
topLayout.addWidget(restart)
</syntaxhighlight>

The top-right cell of the [http://doc.qt.nokia.com/latest/qgridlayout.html Qt::GridLayout] is starting to get crowded. We put a stretch just to the left of the New Game button to ensure that this button will always appear on the right side of the window.

<syntaxhighlight lang="ruby">
newGame()
</syntaxhighlight>

We're all done constructing the '''<tt>GameBoard</tt>''', so we start it all using '''<tt>newGame()</tt>'''. Although '''<tt>newGame()</tt>''' is a slot, it can also be used as an ordinary function.

<syntaxhighlight lang="ruby">
def fire()
if @cannonField.gameOver() || @cannonField.isShooting()
return
end

@shotsLeft.display(@shotsLeft.intValue() - 1)
@cannonField.shoot()
end
</syntaxhighlight>

This function fires a shot. If the game is over or if there is a shot in the air, we return immediately. We decrement the number of shots left and tell the cannon to shoot.

<syntaxhighlight lang="ruby">
def hit()
@hits.display(@hits.intValue() + 1)

if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
else
@cannonField.newTarget()
end
end
</syntaxhighlight>

This slot is activated when a shot has hit the target. We increment the number of hits. If there are no shots left, the game is over. Otherwise, we make the '''<tt>CannonField</tt>''' generate a new target.

<syntaxhighlight lang="ruby">
def missed()
if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
end
end
</syntaxhighlight>

This slot is activated when a shot has missed the target. If there are no shots left, the game is over.

<syntaxhighlight lang="ruby">
def newGame()
@shotsLeft.display(15)
@hits.display(0)
@cannonField.restartGame()
@cannonField.newTarget()
end
</syntaxhighlight>

This slot is activated when the user clicks the New Game button. It is also called from the constructor. First it sets the number of shots to 15. Note that this is the only place in the program where we set the number of shots. Change it to whatever you like to change the game rules. Next we reset the number of hits, restart the game, and generate a new target.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]'''

This file has just been on a diet. '''<tt>MyWidget</tt>''' is gone, and the only thing left is the '''<tt>main()</tt>''' function, unchanged except for the name change.

=== Running the Application ===

The cannon can shoot at a target; a new target is automatically created when one has been hit.

Hits and shots left are displayed and the program keeps track of them. The game can end, and there's a button to start a new game.

=== Exercises ===

Add a random wind factor and show it to the user.

Make some splatter effects when the shot hits the target.

Implement multiple targets.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/6/fi

2011-11-01T17:30:53Z

Centerlink: Created page with "== Peli loppui =="

== Peli loppui ==

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/fi

2011-11-01T17:30:34Z

Centerlink: Created page with "Peli loppui"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Peli loppui|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_14|Tutorial 14 - Facing the Wall]]
}}
== Game Over ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_13.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]

=== Overview ===

In this example we start to approach a real playable game with a score.

We give '''<tt>MyWidget</tt>''' a new name ('''<tt>GameBoard</tt>'''), add some slots, and move it to '''<tt>gamebrd.rb</tt>'''

The '''<tt>CannonField</tt>''' now has a game over state.

The layout problems in '''<tt>LCDRange</tt>''' are fixed.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
@label.setSizePolicy(Qt::SizePolicy::Preferred, Qt::SizePolicy::Fixed)
</syntaxhighlight>

We set the size policy of the [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] to ([http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Preferred], [http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Fixed]). The vertical component ensures that the label won't stretch or shrink vertically; it will stay at its optimal size (its [http://doc.qt.nokia.com/latest/qwidget.html#sizeHint-prop QWidget::sizeHint()]). This solves the layout problems observed in Chapter 12.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has a game over state and a few new functions.

<syntaxhighlight lang="ruby">
signals 'canShoot(bool)'
</syntaxhighlight>

This new signal indicates that the '''<tt>CannonField</tt>''' is in a state where the '''<tt>shoot()</tt>''' slot makes sense. We'll use it below to enable or disable the Shoot button.

<syntaxhighlight lang="ruby">
@gameEnded = false
</syntaxhighlight>

This variable contains the game state; '''<tt>true</tt>''' means that the game is over, and '''<tt>false</tt>''' means that a game is going on. Initially, the game is not over (luckily for the player :-).

<syntaxhighlight lang="ruby">
def shoot()
if isShooting()
return
end

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
emit canShoot(false)
end
</syntaxhighlight>

We added a new '''<tt>isShooting()</tt>''' function, so '''<tt>shoot()</tt>''' uses it instead of testing directly. Also, shoot tells the world that the '''<tt>CannonField</tt>''' cannot shoot now.

<syntaxhighlight lang="ruby">
def setGameOver()
if @gameEnded
return
end

if isShooting()
@autoShootTimer.stop()
end

@gameEnded = true
update()
end
</syntaxhighlight>

This slot ends the game. It must be called from outside '''<tt>CannonField</tt>''', because this widget does not know when to end the game. This is an important design principle in component programming. We choose to make the component as flexible as possible to make it usable with different rules (for example, a multi-player version of this in which the first player to hit ten times wins could use the '''<tt>CannonField</tt>''' unchanged).

If the game has already been ended we return immediately. If a game is going on we stop the shot, set the game over flag, and repaint the entire widget.

<syntaxhighlight lang="ruby">
def restartGame()
if isShooting()
@autoShootTimer.stop()
end

@gameEnded = false

update()
emit canShoot(true)
end
</syntaxhighlight>

This slot starts a new game. If a shot is in the air, we stop shooting. We then reset the '''<tt>gameEnded</tt>''' variable and repaint the widget.

'''<tt>moveShot()</tt>''' too emits the new '''<tt>canShoot(true)</tt>''' signal at the same time as either '''<tt>hit()</tt>''' or '''<tt>miss()</tt>'''.

Modifications in CannonField::paintEvent():

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

if @gameEnded
painter.setPen(Qt::black)
painter.setFont(Qt::Font.new( "Courier", 48, Qt::Font::Bold))
painter.drawText(rect(), Qt::AlignCenter, tr("Game Over"))
end
</syntaxhighlight>

The paint event has been enhanced to display the text "Game Over" if the game is over, i.e., '''<tt>gameEnded</tt>''' is '''<tt>true</tt>'''. We don't bother to check the update rectangle here because speed is not critical when the game is over.

To draw the text we first set a black pen; the pen color is used when drawing text. Next we choose a 48 point bold font from the Courier family. Finally we draw the text centered in the widget's rectangle. Unfortunately, on some systems (especially X servers with Unicode fonts) it can take a while to load such a large font. Because Qt caches fonts, you will notice this only the first time the font is used.

<syntaxhighlight lang="ruby">
paintCannon(painter)

if isShooting()
paintShot(painter)
end

unless @gameEnded
paintTarget(painter)
end

painter.end()
end
</syntaxhighlight>

We draw the shot only when shooting and the target only when playing (that is, when the game is not ended).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]'''

This file is new. It contains the '''<tt>GameBoard</tt>''' class, which was last seen as '''<tt>MyWidget</tt>'''.

<syntaxhighlight lang="ruby">
slots 'fire()', 'hit()', 'missed()', 'newGame()'
</syntaxhighlight>

We have now added four slots.

We have also made some changes in the '''<tt>GameBoard</tt>''' constructor.

<syntaxhighlight lang="ruby">
@cannonField = CannonField.new()
</syntaxhighlight>

'''<tt>@cannonField</tt>''' is now a member variable, so we carefully change the constructor to use it.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('hit()'),
self, SLOT('hit()'))
connect(@cannonField, SIGNAL('missed()'),
self, SLOT('missed()'))
</syntaxhighlight>

This time we want to do something when the shot has hit or missed the target. Thus we connect the '''<tt>hit()</tt>''' and '''<tt>missed()</tt>''' signals of the '''<tt>CannonField</tt>''' to two protected slots with the same names in this class.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), self, SLOT('fire()') )
</syntaxhighlight>

Previously we connected the Shoot button's '''<tt>clicked()</tt>''' signal directly to the '''<tt>CannonField</tt>''''s '''<tt>shoot()</tt>''' slot. This time we want to keep track of the number of shots fired, so we connect it to a slot in this class instead.

Notice how easy it is to change the behavior of a program when you are working with self-contained components.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('canShoot(bool)'),
shoot, SLOT('setEnabled(bool)'))
</syntaxhighlight>

We also use the '''<tt>CannonField</tt>''''s '''<tt>canShoot()</tt>''' signal to enable or disable the Shoot button appropriately.

<syntaxhighlight lang="ruby">
restart = Qt::PushButton.new(tr('&New Game'))
restart.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))

connect(restart, SIGNAL('clicked()'), self, SLOT('newGame()'))
</syntaxhighlight>

We create, set up, and connect the New Game button as we have done with the other buttons. Clicking this button will activate the '''<tt>newGame()</tt>''' slot in this widget.

<syntaxhighlight lang="ruby">
@hits = Qt::LCDNumber.new(2)
@shotsLeft = Qt::LCDNumber.new(2)
hitsLabel = Qt::Label.new(tr('HITS'))
shotsLeftLabel = Qt::Label.new(tr('SHOTS LEFT'))
</syntaxhighlight>

We create four new widgets, to display the number of hits and shots left.

<syntaxhighlight lang="ruby">
topLayout = Qt::HBoxLayout.new()
topLayout.addWidget(shoot)
topLayout.addWidget(@hits)
topLayout.addWidget(hitsLabel)
topLayout.addWidget(@shotsLeft)
topLayout.addWidget(shotsLeftLabel)
topLayout.addStretch(1)
topLayout.addWidget(restart)
</syntaxhighlight>

The top-right cell of the [http://doc.qt.nokia.com/latest/qgridlayout.html Qt::GridLayout] is starting to get crowded. We put a stretch just to the left of the New Game button to ensure that this button will always appear on the right side of the window.

<syntaxhighlight lang="ruby">
newGame()
</syntaxhighlight>

We're all done constructing the '''<tt>GameBoard</tt>''', so we start it all using '''<tt>newGame()</tt>'''. Although '''<tt>newGame()</tt>''' is a slot, it can also be used as an ordinary function.

<syntaxhighlight lang="ruby">
def fire()
if @cannonField.gameOver() || @cannonField.isShooting()
return
end

@shotsLeft.display(@shotsLeft.intValue() - 1)
@cannonField.shoot()
end
</syntaxhighlight>

This function fires a shot. If the game is over or if there is a shot in the air, we return immediately. We decrement the number of shots left and tell the cannon to shoot.

<syntaxhighlight lang="ruby">
def hit()
@hits.display(@hits.intValue() + 1)

if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
else
@cannonField.newTarget()
end
end
</syntaxhighlight>

This slot is activated when a shot has hit the target. We increment the number of hits. If there are no shots left, the game is over. Otherwise, we make the '''<tt>CannonField</tt>''' generate a new target.

<syntaxhighlight lang="ruby">
def missed()
if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
end
end
</syntaxhighlight>

This slot is activated when a shot has missed the target. If there are no shots left, the game is over.

<syntaxhighlight lang="ruby">
def newGame()
@shotsLeft.display(15)
@hits.display(0)
@cannonField.restartGame()
@cannonField.newTarget()
end
</syntaxhighlight>

This slot is activated when the user clicks the New Game button. It is also called from the constructor. First it sets the number of shots to 15. Note that this is the only place in the program where we set the number of shots. Change it to whatever you like to change the game rules. Next we reset the number of hits, restart the game, and generate a new target.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]'''

This file has just been on a diet. '''<tt>MyWidget</tt>''' is gone, and the only thing left is the '''<tt>main()</tt>''' function, unchanged except for the name change.

=== Running the Application ===

The cannon can shoot at a target; a new target is automatically created when one has been hit.

Hits and shots left are displayed and the program keeps track of them. The game can end, and there's a button to start a new game.

=== Exercises ===

Add a random wind factor and show it to the user.

Make some splatter effects when the shot hits the target.

Implement multiple targets.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/3/fi

2011-11-01T17:30:34Z

Centerlink: Created page with "Peli loppui"

Peli loppui

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/fi

2011-11-01T17:30:23Z

Centerlink: Created page with "Qt4 Ruby -oppikurssi"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Game Over|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_14|Tutorial 14 - Facing the Wall]]
}}
== Game Over ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_13.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]

=== Overview ===

In this example we start to approach a real playable game with a score.

We give '''<tt>MyWidget</tt>''' a new name ('''<tt>GameBoard</tt>'''), add some slots, and move it to '''<tt>gamebrd.rb</tt>'''

The '''<tt>CannonField</tt>''' now has a game over state.

The layout problems in '''<tt>LCDRange</tt>''' are fixed.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
@label.setSizePolicy(Qt::SizePolicy::Preferred, Qt::SizePolicy::Fixed)
</syntaxhighlight>

We set the size policy of the [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] to ([http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Preferred], [http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Fixed]). The vertical component ensures that the label won't stretch or shrink vertically; it will stay at its optimal size (its [http://doc.qt.nokia.com/latest/qwidget.html#sizeHint-prop QWidget::sizeHint()]). This solves the layout problems observed in Chapter 12.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has a game over state and a few new functions.

<syntaxhighlight lang="ruby">
signals 'canShoot(bool)'
</syntaxhighlight>

This new signal indicates that the '''<tt>CannonField</tt>''' is in a state where the '''<tt>shoot()</tt>''' slot makes sense. We'll use it below to enable or disable the Shoot button.

<syntaxhighlight lang="ruby">
@gameEnded = false
</syntaxhighlight>

This variable contains the game state; '''<tt>true</tt>''' means that the game is over, and '''<tt>false</tt>''' means that a game is going on. Initially, the game is not over (luckily for the player :-).

<syntaxhighlight lang="ruby">
def shoot()
if isShooting()
return
end

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
emit canShoot(false)
end
</syntaxhighlight>

We added a new '''<tt>isShooting()</tt>''' function, so '''<tt>shoot()</tt>''' uses it instead of testing directly. Also, shoot tells the world that the '''<tt>CannonField</tt>''' cannot shoot now.

<syntaxhighlight lang="ruby">
def setGameOver()
if @gameEnded
return
end

if isShooting()
@autoShootTimer.stop()
end

@gameEnded = true
update()
end
</syntaxhighlight>

This slot ends the game. It must be called from outside '''<tt>CannonField</tt>''', because this widget does not know when to end the game. This is an important design principle in component programming. We choose to make the component as flexible as possible to make it usable with different rules (for example, a multi-player version of this in which the first player to hit ten times wins could use the '''<tt>CannonField</tt>''' unchanged).

If the game has already been ended we return immediately. If a game is going on we stop the shot, set the game over flag, and repaint the entire widget.

<syntaxhighlight lang="ruby">
def restartGame()
if isShooting()
@autoShootTimer.stop()
end

@gameEnded = false

update()
emit canShoot(true)
end
</syntaxhighlight>

This slot starts a new game. If a shot is in the air, we stop shooting. We then reset the '''<tt>gameEnded</tt>''' variable and repaint the widget.

'''<tt>moveShot()</tt>''' too emits the new '''<tt>canShoot(true)</tt>''' signal at the same time as either '''<tt>hit()</tt>''' or '''<tt>miss()</tt>'''.

Modifications in CannonField::paintEvent():

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

if @gameEnded
painter.setPen(Qt::black)
painter.setFont(Qt::Font.new( "Courier", 48, Qt::Font::Bold))
painter.drawText(rect(), Qt::AlignCenter, tr("Game Over"))
end
</syntaxhighlight>

The paint event has been enhanced to display the text "Game Over" if the game is over, i.e., '''<tt>gameEnded</tt>''' is '''<tt>true</tt>'''. We don't bother to check the update rectangle here because speed is not critical when the game is over.

To draw the text we first set a black pen; the pen color is used when drawing text. Next we choose a 48 point bold font from the Courier family. Finally we draw the text centered in the widget's rectangle. Unfortunately, on some systems (especially X servers with Unicode fonts) it can take a while to load such a large font. Because Qt caches fonts, you will notice this only the first time the font is used.

<syntaxhighlight lang="ruby">
paintCannon(painter)

if isShooting()
paintShot(painter)
end

unless @gameEnded
paintTarget(painter)
end

painter.end()
end
</syntaxhighlight>

We draw the shot only when shooting and the target only when playing (that is, when the game is not ended).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]'''

This file is new. It contains the '''<tt>GameBoard</tt>''' class, which was last seen as '''<tt>MyWidget</tt>'''.

<syntaxhighlight lang="ruby">
slots 'fire()', 'hit()', 'missed()', 'newGame()'
</syntaxhighlight>

We have now added four slots.

We have also made some changes in the '''<tt>GameBoard</tt>''' constructor.

<syntaxhighlight lang="ruby">
@cannonField = CannonField.new()
</syntaxhighlight>

'''<tt>@cannonField</tt>''' is now a member variable, so we carefully change the constructor to use it.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('hit()'),
self, SLOT('hit()'))
connect(@cannonField, SIGNAL('missed()'),
self, SLOT('missed()'))
</syntaxhighlight>

This time we want to do something when the shot has hit or missed the target. Thus we connect the '''<tt>hit()</tt>''' and '''<tt>missed()</tt>''' signals of the '''<tt>CannonField</tt>''' to two protected slots with the same names in this class.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), self, SLOT('fire()') )
</syntaxhighlight>

Previously we connected the Shoot button's '''<tt>clicked()</tt>''' signal directly to the '''<tt>CannonField</tt>''''s '''<tt>shoot()</tt>''' slot. This time we want to keep track of the number of shots fired, so we connect it to a slot in this class instead.

Notice how easy it is to change the behavior of a program when you are working with self-contained components.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('canShoot(bool)'),
shoot, SLOT('setEnabled(bool)'))
</syntaxhighlight>

We also use the '''<tt>CannonField</tt>''''s '''<tt>canShoot()</tt>''' signal to enable or disable the Shoot button appropriately.

<syntaxhighlight lang="ruby">
restart = Qt::PushButton.new(tr('&New Game'))
restart.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))

connect(restart, SIGNAL('clicked()'), self, SLOT('newGame()'))
</syntaxhighlight>

We create, set up, and connect the New Game button as we have done with the other buttons. Clicking this button will activate the '''<tt>newGame()</tt>''' slot in this widget.

<syntaxhighlight lang="ruby">
@hits = Qt::LCDNumber.new(2)
@shotsLeft = Qt::LCDNumber.new(2)
hitsLabel = Qt::Label.new(tr('HITS'))
shotsLeftLabel = Qt::Label.new(tr('SHOTS LEFT'))
</syntaxhighlight>

We create four new widgets, to display the number of hits and shots left.

<syntaxhighlight lang="ruby">
topLayout = Qt::HBoxLayout.new()
topLayout.addWidget(shoot)
topLayout.addWidget(@hits)
topLayout.addWidget(hitsLabel)
topLayout.addWidget(@shotsLeft)
topLayout.addWidget(shotsLeftLabel)
topLayout.addStretch(1)
topLayout.addWidget(restart)
</syntaxhighlight>

The top-right cell of the [http://doc.qt.nokia.com/latest/qgridlayout.html Qt::GridLayout] is starting to get crowded. We put a stretch just to the left of the New Game button to ensure that this button will always appear on the right side of the window.

<syntaxhighlight lang="ruby">
newGame()
</syntaxhighlight>

We're all done constructing the '''<tt>GameBoard</tt>''', so we start it all using '''<tt>newGame()</tt>'''. Although '''<tt>newGame()</tt>''' is a slot, it can also be used as an ordinary function.

<syntaxhighlight lang="ruby">
def fire()
if @cannonField.gameOver() || @cannonField.isShooting()
return
end

@shotsLeft.display(@shotsLeft.intValue() - 1)
@cannonField.shoot()
end
</syntaxhighlight>

This function fires a shot. If the game is over or if there is a shot in the air, we return immediately. We decrement the number of shots left and tell the cannon to shoot.

<syntaxhighlight lang="ruby">
def hit()
@hits.display(@hits.intValue() + 1)

if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
else
@cannonField.newTarget()
end
end
</syntaxhighlight>

This slot is activated when a shot has hit the target. We increment the number of hits. If there are no shots left, the game is over. Otherwise, we make the '''<tt>CannonField</tt>''' generate a new target.

<syntaxhighlight lang="ruby">
def missed()
if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
end
end
</syntaxhighlight>

This slot is activated when a shot has missed the target. If there are no shots left, the game is over.

<syntaxhighlight lang="ruby">
def newGame()
@shotsLeft.display(15)
@hits.display(0)
@cannonField.restartGame()
@cannonField.newTarget()
end
</syntaxhighlight>

This slot is activated when the user clicks the New Game button. It is also called from the constructor. First it sets the number of shots to 15. Note that this is the only place in the program where we set the number of shots. Change it to whatever you like to change the game rules. Next we reset the number of hits, restart the game, and generate a new target.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]'''

This file has just been on a diet. '''<tt>MyWidget</tt>''' is gone, and the only thing left is the '''<tt>main()</tt>''' function, unchanged except for the name change.

=== Running the Application ===

The cannon can shoot at a target; a new target is automatically created when one has been hit.

Hits and shots left are displayed and the program keeps track of them. The game can end, and there's a button to start a new game.

=== Exercises ===

Add a random wind factor and show it to the user.

Make some splatter effects when the shot hits the target.

Implement multiple targets.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/2/fi

2011-11-01T17:30:23Z

Centerlink: Created page with "Qt4 Ruby -oppikurssi"

Qt4 Ruby -oppikurssi

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/1/fi

2011-11-01T17:30:10Z

Centerlink: Created page with "TutorialBrowser"

TutorialBrowser

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13/fi

2011-11-01T17:30:10Z

Centerlink: Created page with "TutorialBrowser"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 13}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby Tutorial]]|
name=Game Over|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_14|Tutorial 14 - Facing the Wall]]
}}
== Game Over ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_13.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]

=== Overview ===

In this example we start to approach a real playable game with a score.

We give '''<tt>MyWidget</tt>''' a new name ('''<tt>GameBoard</tt>'''), add some slots, and move it to '''<tt>gamebrd.rb</tt>'''

The '''<tt>CannonField</tt>''' now has a game over state.

The layout problems in '''<tt>LCDRange</tt>''' are fixed.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
@label.setSizePolicy(Qt::SizePolicy::Preferred, Qt::SizePolicy::Fixed)
</syntaxhighlight>

We set the size policy of the [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] to ([http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Preferred], [http://doc.qt.nokia.com/latest/qsizepolicy.html#Policy-enum Qt::SizePolicy::Fixed]). The vertical component ensures that the label won't stretch or shrink vertically; it will stay at its optimal size (its [http://doc.qt.nokia.com/latest/qwidget.html#sizeHint-prop QWidget::sizeHint()]). This solves the layout problems observed in Chapter 12.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has a game over state and a few new functions.

<syntaxhighlight lang="ruby">
signals 'canShoot(bool)'
</syntaxhighlight>

This new signal indicates that the '''<tt>CannonField</tt>''' is in a state where the '''<tt>shoot()</tt>''' slot makes sense. We'll use it below to enable or disable the Shoot button.

<syntaxhighlight lang="ruby">
@gameEnded = false
</syntaxhighlight>

This variable contains the game state; '''<tt>true</tt>''' means that the game is over, and '''<tt>false</tt>''' means that a game is going on. Initially, the game is not over (luckily for the player :-).

<syntaxhighlight lang="ruby">
def shoot()
if isShooting()
return
end

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
emit canShoot(false)
end
</syntaxhighlight>

We added a new '''<tt>isShooting()</tt>''' function, so '''<tt>shoot()</tt>''' uses it instead of testing directly. Also, shoot tells the world that the '''<tt>CannonField</tt>''' cannot shoot now.

<syntaxhighlight lang="ruby">
def setGameOver()
if @gameEnded
return
end

if isShooting()
@autoShootTimer.stop()
end

@gameEnded = true
update()
end
</syntaxhighlight>

This slot ends the game. It must be called from outside '''<tt>CannonField</tt>''', because this widget does not know when to end the game. This is an important design principle in component programming. We choose to make the component as flexible as possible to make it usable with different rules (for example, a multi-player version of this in which the first player to hit ten times wins could use the '''<tt>CannonField</tt>''' unchanged).

If the game has already been ended we return immediately. If a game is going on we stop the shot, set the game over flag, and repaint the entire widget.

<syntaxhighlight lang="ruby">
def restartGame()
if isShooting()
@autoShootTimer.stop()
end

@gameEnded = false

update()
emit canShoot(true)
end
</syntaxhighlight>

This slot starts a new game. If a shot is in the air, we stop shooting. We then reset the '''<tt>gameEnded</tt>''' variable and repaint the widget.

'''<tt>moveShot()</tt>''' too emits the new '''<tt>canShoot(true)</tt>''' signal at the same time as either '''<tt>hit()</tt>''' or '''<tt>miss()</tt>'''.

Modifications in CannonField::paintEvent():

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

if @gameEnded
painter.setPen(Qt::black)
painter.setFont(Qt::Font.new( "Courier", 48, Qt::Font::Bold))
painter.drawText(rect(), Qt::AlignCenter, tr("Game Over"))
end
</syntaxhighlight>

The paint event has been enhanced to display the text "Game Over" if the game is over, i.e., '''<tt>gameEnded</tt>''' is '''<tt>true</tt>'''. We don't bother to check the update rectangle here because speed is not critical when the game is over.

To draw the text we first set a black pen; the pen color is used when drawing text. Next we choose a 48 point bold font from the Courier family. Finally we draw the text centered in the widget's rectangle. Unfortunately, on some systems (especially X servers with Unicode fonts) it can take a while to load such a large font. Because Qt caches fonts, you will notice this only the first time the font is used.

<syntaxhighlight lang="ruby">
paintCannon(painter)

if isShooting()
paintShot(painter)
end

unless @gameEnded
paintTarget(painter)
end

painter.end()
end
</syntaxhighlight>

We draw the shot only when shooting and the target only when playing (that is, when the game is not ended).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/gamebrd.rb gamebrd.rb]'''

This file is new. It contains the '''<tt>GameBoard</tt>''' class, which was last seen as '''<tt>MyWidget</tt>'''.

<syntaxhighlight lang="ruby">
slots 'fire()', 'hit()', 'missed()', 'newGame()'
</syntaxhighlight>

We have now added four slots.

We have also made some changes in the '''<tt>GameBoard</tt>''' constructor.

<syntaxhighlight lang="ruby">
@cannonField = CannonField.new()
</syntaxhighlight>

'''<tt>@cannonField</tt>''' is now a member variable, so we carefully change the constructor to use it.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('hit()'),
self, SLOT('hit()'))
connect(@cannonField, SIGNAL('missed()'),
self, SLOT('missed()'))
</syntaxhighlight>

This time we want to do something when the shot has hit or missed the target. Thus we connect the '''<tt>hit()</tt>''' and '''<tt>missed()</tt>''' signals of the '''<tt>CannonField</tt>''' to two protected slots with the same names in this class.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), self, SLOT('fire()') )
</syntaxhighlight>

Previously we connected the Shoot button's '''<tt>clicked()</tt>''' signal directly to the '''<tt>CannonField</tt>''''s '''<tt>shoot()</tt>''' slot. This time we want to keep track of the number of shots fired, so we connect it to a slot in this class instead.

Notice how easy it is to change the behavior of a program when you are working with self-contained components.

<syntaxhighlight lang="ruby">
connect(@cannonField, SIGNAL('canShoot(bool)'),
shoot, SLOT('setEnabled(bool)'))
</syntaxhighlight>

We also use the '''<tt>CannonField</tt>''''s '''<tt>canShoot()</tt>''' signal to enable or disable the Shoot button appropriately.

<syntaxhighlight lang="ruby">
restart = Qt::PushButton.new(tr('&New Game'))
restart.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))

connect(restart, SIGNAL('clicked()'), self, SLOT('newGame()'))
</syntaxhighlight>

We create, set up, and connect the New Game button as we have done with the other buttons. Clicking this button will activate the '''<tt>newGame()</tt>''' slot in this widget.

<syntaxhighlight lang="ruby">
@hits = Qt::LCDNumber.new(2)
@shotsLeft = Qt::LCDNumber.new(2)
hitsLabel = Qt::Label.new(tr('HITS'))
shotsLeftLabel = Qt::Label.new(tr('SHOTS LEFT'))
</syntaxhighlight>

We create four new widgets, to display the number of hits and shots left.

<syntaxhighlight lang="ruby">
topLayout = Qt::HBoxLayout.new()
topLayout.addWidget(shoot)
topLayout.addWidget(@hits)
topLayout.addWidget(hitsLabel)
topLayout.addWidget(@shotsLeft)
topLayout.addWidget(shotsLeftLabel)
topLayout.addStretch(1)
topLayout.addWidget(restart)
</syntaxhighlight>

The top-right cell of the [http://doc.qt.nokia.com/latest/qgridlayout.html Qt::GridLayout] is starting to get crowded. We put a stretch just to the left of the New Game button to ensure that this button will always appear on the right side of the window.

<syntaxhighlight lang="ruby">
newGame()
</syntaxhighlight>

We're all done constructing the '''<tt>GameBoard</tt>''', so we start it all using '''<tt>newGame()</tt>'''. Although '''<tt>newGame()</tt>''' is a slot, it can also be used as an ordinary function.

<syntaxhighlight lang="ruby">
def fire()
if @cannonField.gameOver() || @cannonField.isShooting()
return
end

@shotsLeft.display(@shotsLeft.intValue() - 1)
@cannonField.shoot()
end
</syntaxhighlight>

This function fires a shot. If the game is over or if there is a shot in the air, we return immediately. We decrement the number of shots left and tell the cannon to shoot.

<syntaxhighlight lang="ruby">
def hit()
@hits.display(@hits.intValue() + 1)

if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
else
@cannonField.newTarget()
end
end
</syntaxhighlight>

This slot is activated when a shot has hit the target. We increment the number of hits. If there are no shots left, the game is over. Otherwise, we make the '''<tt>CannonField</tt>''' generate a new target.

<syntaxhighlight lang="ruby">
def missed()
if @shotsLeft.intValue() == 0
@cannonField.setGameOver()
end
end
</syntaxhighlight>

This slot is activated when a shot has missed the target. If there are no shots left, the game is over.

<syntaxhighlight lang="ruby">
def newGame()
@shotsLeft.display(15)
@hits.display(0)
@cannonField.restartGame()
@cannonField.newTarget()
end
</syntaxhighlight>

This slot is activated when the user clicks the New Game button. It is also called from the constructor. First it sets the number of shots to 15. Note that this is the only place in the program where we set the number of shots. Change it to whatever you like to change the game rules. Next we reset the number of hits, restart the game, and generate a new target.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t13/t13.rb t13.rb]'''

This file has just been on a diet. '''<tt>MyWidget</tt>''' is gone, and the only thing left is the '''<tt>main()</tt>''' function, unchanged except for the name change.

=== Running the Application ===

The cannon can shoot at a target; a new target is automatically created when one has been hit.

Hits and shots left are displayed and the program keeps track of them. The game can end, and there's a button to start a new game.

=== Exercises ===

Add a random wind factor and show it to the user.

Make some splatter effects when the shot hits the target.

Implement multiple targets.

[[Category:Ruby]]

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/fi

2011-11-01T17:29:37Z

Centerlink: Created page with "=== Yleiskuva ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Hanging in the Air the Way Bricks Don't|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_11|Oppikurssi 11 - Ammutaan tykillä]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Oppikurssi 13 - Peli loppui]]
}}
== Hanging in the Air the Way Bricks Don't ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_12.png|center]]
Tiedostot:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]

=== Yleiskuva ===

In this example, we extend our '''<tt>LCDRange</tt>''' class to include a text label. We also provide something to shoot at.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
def initialize(s, parent = nil)
super(parent)
init()
setText(s)
end
</syntaxhighlight>

This constructor first calls '''<tt>init()</tt>''' and then sets the label text. '''<tt>init()</tt>''' is a separate function performing initialization mosty because of function overloading matters in the original C++ version.

<syntaxhighlight lang="ruby">
def init()
lcd = Qt::LCDNumber.new(2)
lcd.setSegmentStyle(Qt::LCDNumber::Filled)

@slider = Qt::Slider.new(Qt::Horizontal)
@slider.setRange(0, 99)
@slider.setValue(0)

@label = Qt::Label.new()
@label.setAlignment(Qt::AlignHCenter.to_i | Qt::AlignTop.to_i)

connect(@slider, SIGNAL('valueChanged(int)'),
lcd, SLOT('display(int)'))
connect(@slider, SIGNAL('valueChanged(int)'),
self, SIGNAL('valueChanged(int)'))

layout = Qt::VBoxLayout.new()
layout.addWidget(lcd)
layout.addWidget(@slider)
layout.addWidget(@label)
setLayout(layout)

setFocusProxy(@slider)
end
</syntaxhighlight>

The setup of '''<tt>lcd</tt>''' and '''<tt>slider</tt>''' is the same as in the previous chapter. Next we create a [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] and tell it to align the contents centered horizontally and to the top vertically. The [http://doc.qt.nokia.com/latest/qobject.html#connect Qt::Object::connect()] calls have also been taken from the previous chapter.

<syntaxhighlight lang="ruby">
def setText(s)
@label.setText(s)
end
</syntaxhighlight>

This function sets the label text.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has two new signals: '''<tt>hit()</tt>''' and '''<tt>missed()</tt>'''. In addition, it contains a target.

<syntaxhighlight lang="ruby">
signals 'hit()', 'missed()' #...
</syntaxhighlight>

The '''<tt>hit()</tt>''' signal is emitted when a shot hits the target. The '''<tt>missed()</tt>''' signal is emitted when the shot moves beyond the right or bottom edge of the widget (i.e., it is certain that it has not and will not hit the target).

<syntaxhighlight lang="ruby">
newTarget()
</syntaxhighlight>

This line has been added to the constructor. It creates a "random" position for the target. In fact, the '''<tt>newTarget()</tt>''' function will try to paint the target. Because we are in a constructor, the '''<tt>CannonField</tt>''' widget is invisible. Qt guarantees that no harm is done when calling [http://doc.qt.nokia.com/latest/qwidget.html#update Qt::Widget::update()] on a hidden widget.

<syntaxhighlight lang="ruby">
@@first_time = true

def newTarget()
if @@first_time
@@first_time = false
midnight = Qt::Time.new(0, 0, 0)
srand(midnight.secsTo(Qt::Time.currentTime()))
end

@target = Qt::Point.new(200 + rand(190), 10 + rand(255))
update()
end
</syntaxhighlight>

This function creates a target center point at a new random position.

We create the [http://doc.qt.nokia.com/latest/qtime.html Qt::Time] object '''<tt>midnight</tt>''', which represents the time 00:00:00. Next we fetch the number of seconds from midnight until now and use it as a random seed. See the documentation for [http://doc.qt.nokia.com/latest/qdate.html Qt::Date], [http://doc.qt.nokia.com/latest/qtime.html Qt::Time], and [http://doc.qt.nokia.com/latest/qdatetime.html Qt::DateTime] for more information.

Finally we calculate the target's center point. We keep it within the rectangle (x = 200, y = 35, width = 190, height = 255), i.e., the possible x and y values are 200 to 389 and 35 to 289, respectively) in a coordinate system where we put y position 0 at the bottom edge of the widget and let y values increase upwards x is as normal, with 0 at the left edge and with x values increasing to the right.

By experimentation we have found this to always be in reach of the shot.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()
</syntaxhighlight>

This part of the timer event has not changed from the previous chapter.

<syntaxhighlight lang="ruby">
if shotR.intersects(targetRect())
@autoShootTimer.stop()
emit hit()
</syntaxhighlight>

This '''<tt>if</tt>''' statement checks whether the shot rectangle intersects the target rectangle. If it does, the shot has hit the target (ouch!). We stop the shoot timer and emit the '''<tt>hit()</tt>''' signal to tell the outside world that a target was destroyed, and return. Note that we could have created a new target on the spot, but because the '''<tt>CannonField</tt>''' is a component we leave such decisions to the user of the component.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
emit missed()
</syntaxhighlight>

This is the same as in the previous chapter, except that it now emits the '''<tt>missed()</tt>''' signal to tell the outside world about the failure.

<syntaxhighlight lang="ruby">
else
region = region.unite(Qt::Region.new(shotR))
end

update(region)
end
</syntaxhighlight>

And the rest of the function is as before.

'''<tt>CannonField::paintEvent()</tt>''' is as before, except that this has been added:

<syntaxhighlight lang="ruby">
paintTarget(painter)
</syntaxhighlight>

This line makes sure that the target is also painted when necessary.

<syntaxhighlight lang="ruby">
def paintTarget(painter)
painter.setBrush(Qt::Brush.new(Qt::red))
painter.setPen(Qt::Pen.new(Qt::Color.new(Qt::black)))
painter.drawRect(targetRect())
end
</syntaxhighlight>

This function paints the target; a rectangle filled with red and with a black outline.

<syntaxhighlight lang="ruby">
def targetRect()
result = Qt::Rect.new(0, 0, 20, 10)
result.moveCenter(Qt::Point.new(@target.x(), height() - 1 - @target.y()))
return result
end
</syntaxhighlight>

This private function returns the enclosing rectangle of the target. Remember from '''<tt>newTarget()</tt>''' that the '''<tt>target</tt>''' point uses y coordinate 0 at the bottom of the widget. We calculate the point in widget coordinates before we call [http://doc.qt.nokia.com/latest/qrect.html#moveCenter Qt::Rect::moveCenter()].

The reason we have chosen this coordinate mapping is to fix the distance between the target and the bottom of the widget. Remember that the widget can be resized by the user or the program at any time.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]'''

There are no new members in the '''<tt>MyWidget</tt>''' class, but we have slightly changed the constructor to set the new '''<tt>LCDRange</tt>''' text labels.

<syntaxhighlight lang="ruby">
angle = LCDRange.new(tr('ANGLE'))
</syntaxhighlight>

We set the angle text label to "ANGLE".

<syntaxhighlight lang="ruby">
force = LCDRange.new(tr('FORCE'))
</syntaxhighlight>

We set the force text label to "FORCE".

=== Sovelluksen suorittaminen ===

The '''<tt>LCDRange</tt>''' widgets look a bit strange: When resizing '''<tt>MyWidget</tt>''', the built-in layout management in [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] gives the labels too much space and the rest not enough; making the space between the two '''<tt>LCDRange</tt>''' widgets change size. We'll fix that in the next chapter

=== Harjoitukset ===

Make a cheat button that, when pressed, makes the '''<tt>CannonField</tt>''' display the shot trajectory for five seconds.

If you did the "round shot" exercise from the previous chapter, try changing the '''<tt>shotRect()</tt>''' to a '''<tt>shotRegion()</tt>''' that returns a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] so you can have really accurate collision detection.

Make a moving target.

Make sure that the target is always created entirely on-screen.

Make sure that the widget cannot be resized so that the target isn't visible. [Hint: [http://doc.qt.nokia.com/latest/qwidget.html#minimumSize-prop Qt::Widget::setMinimumSize()] is your friend.]

Not easy; make it possible to have several shots in the air at the same time. [Hint: Make a '''<tt>Shot</tt>''' class.]

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/9/fi

2011-11-01T17:29:36Z

Centerlink: Created page with "=== Yleiskuva ==="

=== Yleiskuva ===

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/fi

2011-11-01T17:29:25Z

Centerlink: Created page with "Tiedostot:"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Hanging in the Air the Way Bricks Don't|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_11|Oppikurssi 11 - Ammutaan tykillä]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Oppikurssi 13 - Peli loppui]]
}}
== Hanging in the Air the Way Bricks Don't ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_12.png|center]]
Tiedostot:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]

=== Overview ===

In this example, we extend our '''<tt>LCDRange</tt>''' class to include a text label. We also provide something to shoot at.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
def initialize(s, parent = nil)
super(parent)
init()
setText(s)
end
</syntaxhighlight>

This constructor first calls '''<tt>init()</tt>''' and then sets the label text. '''<tt>init()</tt>''' is a separate function performing initialization mosty because of function overloading matters in the original C++ version.

<syntaxhighlight lang="ruby">
def init()
lcd = Qt::LCDNumber.new(2)
lcd.setSegmentStyle(Qt::LCDNumber::Filled)

@slider = Qt::Slider.new(Qt::Horizontal)
@slider.setRange(0, 99)
@slider.setValue(0)

@label = Qt::Label.new()
@label.setAlignment(Qt::AlignHCenter.to_i | Qt::AlignTop.to_i)

connect(@slider, SIGNAL('valueChanged(int)'),
lcd, SLOT('display(int)'))
connect(@slider, SIGNAL('valueChanged(int)'),
self, SIGNAL('valueChanged(int)'))

layout = Qt::VBoxLayout.new()
layout.addWidget(lcd)
layout.addWidget(@slider)
layout.addWidget(@label)
setLayout(layout)

setFocusProxy(@slider)
end
</syntaxhighlight>

The setup of '''<tt>lcd</tt>''' and '''<tt>slider</tt>''' is the same as in the previous chapter. Next we create a [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] and tell it to align the contents centered horizontally and to the top vertically. The [http://doc.qt.nokia.com/latest/qobject.html#connect Qt::Object::connect()] calls have also been taken from the previous chapter.

<syntaxhighlight lang="ruby">
def setText(s)
@label.setText(s)
end
</syntaxhighlight>

This function sets the label text.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has two new signals: '''<tt>hit()</tt>''' and '''<tt>missed()</tt>'''. In addition, it contains a target.

<syntaxhighlight lang="ruby">
signals 'hit()', 'missed()' #...
</syntaxhighlight>

The '''<tt>hit()</tt>''' signal is emitted when a shot hits the target. The '''<tt>missed()</tt>''' signal is emitted when the shot moves beyond the right or bottom edge of the widget (i.e., it is certain that it has not and will not hit the target).

<syntaxhighlight lang="ruby">
newTarget()
</syntaxhighlight>

This line has been added to the constructor. It creates a "random" position for the target. In fact, the '''<tt>newTarget()</tt>''' function will try to paint the target. Because we are in a constructor, the '''<tt>CannonField</tt>''' widget is invisible. Qt guarantees that no harm is done when calling [http://doc.qt.nokia.com/latest/qwidget.html#update Qt::Widget::update()] on a hidden widget.

<syntaxhighlight lang="ruby">
@@first_time = true

def newTarget()
if @@first_time
@@first_time = false
midnight = Qt::Time.new(0, 0, 0)
srand(midnight.secsTo(Qt::Time.currentTime()))
end

@target = Qt::Point.new(200 + rand(190), 10 + rand(255))
update()
end
</syntaxhighlight>

This function creates a target center point at a new random position.

We create the [http://doc.qt.nokia.com/latest/qtime.html Qt::Time] object '''<tt>midnight</tt>''', which represents the time 00:00:00. Next we fetch the number of seconds from midnight until now and use it as a random seed. See the documentation for [http://doc.qt.nokia.com/latest/qdate.html Qt::Date], [http://doc.qt.nokia.com/latest/qtime.html Qt::Time], and [http://doc.qt.nokia.com/latest/qdatetime.html Qt::DateTime] for more information.

Finally we calculate the target's center point. We keep it within the rectangle (x = 200, y = 35, width = 190, height = 255), i.e., the possible x and y values are 200 to 389 and 35 to 289, respectively) in a coordinate system where we put y position 0 at the bottom edge of the widget and let y values increase upwards x is as normal, with 0 at the left edge and with x values increasing to the right.

By experimentation we have found this to always be in reach of the shot.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()
</syntaxhighlight>

This part of the timer event has not changed from the previous chapter.

<syntaxhighlight lang="ruby">
if shotR.intersects(targetRect())
@autoShootTimer.stop()
emit hit()
</syntaxhighlight>

This '''<tt>if</tt>''' statement checks whether the shot rectangle intersects the target rectangle. If it does, the shot has hit the target (ouch!). We stop the shoot timer and emit the '''<tt>hit()</tt>''' signal to tell the outside world that a target was destroyed, and return. Note that we could have created a new target on the spot, but because the '''<tt>CannonField</tt>''' is a component we leave such decisions to the user of the component.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
emit missed()
</syntaxhighlight>

This is the same as in the previous chapter, except that it now emits the '''<tt>missed()</tt>''' signal to tell the outside world about the failure.

<syntaxhighlight lang="ruby">
else
region = region.unite(Qt::Region.new(shotR))
end

update(region)
end
</syntaxhighlight>

And the rest of the function is as before.

'''<tt>CannonField::paintEvent()</tt>''' is as before, except that this has been added:

<syntaxhighlight lang="ruby">
paintTarget(painter)
</syntaxhighlight>

This line makes sure that the target is also painted when necessary.

<syntaxhighlight lang="ruby">
def paintTarget(painter)
painter.setBrush(Qt::Brush.new(Qt::red))
painter.setPen(Qt::Pen.new(Qt::Color.new(Qt::black)))
painter.drawRect(targetRect())
end
</syntaxhighlight>

This function paints the target; a rectangle filled with red and with a black outline.

<syntaxhighlight lang="ruby">
def targetRect()
result = Qt::Rect.new(0, 0, 20, 10)
result.moveCenter(Qt::Point.new(@target.x(), height() - 1 - @target.y()))
return result
end
</syntaxhighlight>

This private function returns the enclosing rectangle of the target. Remember from '''<tt>newTarget()</tt>''' that the '''<tt>target</tt>''' point uses y coordinate 0 at the bottom of the widget. We calculate the point in widget coordinates before we call [http://doc.qt.nokia.com/latest/qrect.html#moveCenter Qt::Rect::moveCenter()].

The reason we have chosen this coordinate mapping is to fix the distance between the target and the bottom of the widget. Remember that the widget can be resized by the user or the program at any time.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]'''

There are no new members in the '''<tt>MyWidget</tt>''' class, but we have slightly changed the constructor to set the new '''<tt>LCDRange</tt>''' text labels.

<syntaxhighlight lang="ruby">
angle = LCDRange.new(tr('ANGLE'))
</syntaxhighlight>

We set the angle text label to "ANGLE".

<syntaxhighlight lang="ruby">
force = LCDRange.new(tr('FORCE'))
</syntaxhighlight>

We set the force text label to "FORCE".

=== Sovelluksen suorittaminen ===

The '''<tt>LCDRange</tt>''' widgets look a bit strange: When resizing '''<tt>MyWidget</tt>''', the built-in layout management in [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] gives the labels too much space and the rest not enough; making the space between the two '''<tt>LCDRange</tt>''' widgets change size. We'll fix that in the next chapter

=== Harjoitukset ===

Make a cheat button that, when pressed, makes the '''<tt>CannonField</tt>''' display the shot trajectory for five seconds.

If you did the "round shot" exercise from the previous chapter, try changing the '''<tt>shotRect()</tt>''' to a '''<tt>shotRegion()</tt>''' that returns a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] so you can have really accurate collision detection.

Make a moving target.

Make sure that the target is always created entirely on-screen.

Make sure that the widget cannot be resized so that the target isn't visible. [Hint: [http://doc.qt.nokia.com/latest/qwidget.html#minimumSize-prop Qt::Widget::setMinimumSize()] is your friend.]

Not easy; make it possible to have several shots in the air at the same time. [Hint: Make a '''<tt>Shot</tt>''' class.]

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/8/fi

2011-11-01T17:29:24Z

Centerlink: Created page with "Tiedostot:"

Tiedostot:

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/fi

2011-11-01T17:29:06Z

Centerlink: Created page with "=== Harjoitukset ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Hanging in the Air the Way Bricks Don't|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_11|Oppikurssi 11 - Ammutaan tykillä]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Oppikurssi 13 - Peli loppui]]
}}
== Hanging in the Air the Way Bricks Don't ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_12.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]

=== Overview ===

In this example, we extend our '''<tt>LCDRange</tt>''' class to include a text label. We also provide something to shoot at.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
def initialize(s, parent = nil)
super(parent)
init()
setText(s)
end
</syntaxhighlight>

This constructor first calls '''<tt>init()</tt>''' and then sets the label text. '''<tt>init()</tt>''' is a separate function performing initialization mosty because of function overloading matters in the original C++ version.

<syntaxhighlight lang="ruby">
def init()
lcd = Qt::LCDNumber.new(2)
lcd.setSegmentStyle(Qt::LCDNumber::Filled)

@slider = Qt::Slider.new(Qt::Horizontal)
@slider.setRange(0, 99)
@slider.setValue(0)

@label = Qt::Label.new()
@label.setAlignment(Qt::AlignHCenter.to_i | Qt::AlignTop.to_i)

connect(@slider, SIGNAL('valueChanged(int)'),
lcd, SLOT('display(int)'))
connect(@slider, SIGNAL('valueChanged(int)'),
self, SIGNAL('valueChanged(int)'))

layout = Qt::VBoxLayout.new()
layout.addWidget(lcd)
layout.addWidget(@slider)
layout.addWidget(@label)
setLayout(layout)

setFocusProxy(@slider)
end
</syntaxhighlight>

The setup of '''<tt>lcd</tt>''' and '''<tt>slider</tt>''' is the same as in the previous chapter. Next we create a [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] and tell it to align the contents centered horizontally and to the top vertically. The [http://doc.qt.nokia.com/latest/qobject.html#connect Qt::Object::connect()] calls have also been taken from the previous chapter.

<syntaxhighlight lang="ruby">
def setText(s)
@label.setText(s)
end
</syntaxhighlight>

This function sets the label text.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has two new signals: '''<tt>hit()</tt>''' and '''<tt>missed()</tt>'''. In addition, it contains a target.

<syntaxhighlight lang="ruby">
signals 'hit()', 'missed()' #...
</syntaxhighlight>

The '''<tt>hit()</tt>''' signal is emitted when a shot hits the target. The '''<tt>missed()</tt>''' signal is emitted when the shot moves beyond the right or bottom edge of the widget (i.e., it is certain that it has not and will not hit the target).

<syntaxhighlight lang="ruby">
newTarget()
</syntaxhighlight>

This line has been added to the constructor. It creates a "random" position for the target. In fact, the '''<tt>newTarget()</tt>''' function will try to paint the target. Because we are in a constructor, the '''<tt>CannonField</tt>''' widget is invisible. Qt guarantees that no harm is done when calling [http://doc.qt.nokia.com/latest/qwidget.html#update Qt::Widget::update()] on a hidden widget.

<syntaxhighlight lang="ruby">
@@first_time = true

def newTarget()
if @@first_time
@@first_time = false
midnight = Qt::Time.new(0, 0, 0)
srand(midnight.secsTo(Qt::Time.currentTime()))
end

@target = Qt::Point.new(200 + rand(190), 10 + rand(255))
update()
end
</syntaxhighlight>

This function creates a target center point at a new random position.

We create the [http://doc.qt.nokia.com/latest/qtime.html Qt::Time] object '''<tt>midnight</tt>''', which represents the time 00:00:00. Next we fetch the number of seconds from midnight until now and use it as a random seed. See the documentation for [http://doc.qt.nokia.com/latest/qdate.html Qt::Date], [http://doc.qt.nokia.com/latest/qtime.html Qt::Time], and [http://doc.qt.nokia.com/latest/qdatetime.html Qt::DateTime] for more information.

Finally we calculate the target's center point. We keep it within the rectangle (x = 200, y = 35, width = 190, height = 255), i.e., the possible x and y values are 200 to 389 and 35 to 289, respectively) in a coordinate system where we put y position 0 at the bottom edge of the widget and let y values increase upwards x is as normal, with 0 at the left edge and with x values increasing to the right.

By experimentation we have found this to always be in reach of the shot.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()
</syntaxhighlight>

This part of the timer event has not changed from the previous chapter.

<syntaxhighlight lang="ruby">
if shotR.intersects(targetRect())
@autoShootTimer.stop()
emit hit()
</syntaxhighlight>

This '''<tt>if</tt>''' statement checks whether the shot rectangle intersects the target rectangle. If it does, the shot has hit the target (ouch!). We stop the shoot timer and emit the '''<tt>hit()</tt>''' signal to tell the outside world that a target was destroyed, and return. Note that we could have created a new target on the spot, but because the '''<tt>CannonField</tt>''' is a component we leave such decisions to the user of the component.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
emit missed()
</syntaxhighlight>

This is the same as in the previous chapter, except that it now emits the '''<tt>missed()</tt>''' signal to tell the outside world about the failure.

<syntaxhighlight lang="ruby">
else
region = region.unite(Qt::Region.new(shotR))
end

update(region)
end
</syntaxhighlight>

And the rest of the function is as before.

'''<tt>CannonField::paintEvent()</tt>''' is as before, except that this has been added:

<syntaxhighlight lang="ruby">
paintTarget(painter)
</syntaxhighlight>

This line makes sure that the target is also painted when necessary.

<syntaxhighlight lang="ruby">
def paintTarget(painter)
painter.setBrush(Qt::Brush.new(Qt::red))
painter.setPen(Qt::Pen.new(Qt::Color.new(Qt::black)))
painter.drawRect(targetRect())
end
</syntaxhighlight>

This function paints the target; a rectangle filled with red and with a black outline.

<syntaxhighlight lang="ruby">
def targetRect()
result = Qt::Rect.new(0, 0, 20, 10)
result.moveCenter(Qt::Point.new(@target.x(), height() - 1 - @target.y()))
return result
end
</syntaxhighlight>

This private function returns the enclosing rectangle of the target. Remember from '''<tt>newTarget()</tt>''' that the '''<tt>target</tt>''' point uses y coordinate 0 at the bottom of the widget. We calculate the point in widget coordinates before we call [http://doc.qt.nokia.com/latest/qrect.html#moveCenter Qt::Rect::moveCenter()].

The reason we have chosen this coordinate mapping is to fix the distance between the target and the bottom of the widget. Remember that the widget can be resized by the user or the program at any time.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]'''

There are no new members in the '''<tt>MyWidget</tt>''' class, but we have slightly changed the constructor to set the new '''<tt>LCDRange</tt>''' text labels.

<syntaxhighlight lang="ruby">
angle = LCDRange.new(tr('ANGLE'))
</syntaxhighlight>

We set the angle text label to "ANGLE".

<syntaxhighlight lang="ruby">
force = LCDRange.new(tr('FORCE'))
</syntaxhighlight>

We set the force text label to "FORCE".

=== Sovelluksen suorittaminen ===

The '''<tt>LCDRange</tt>''' widgets look a bit strange: When resizing '''<tt>MyWidget</tt>''', the built-in layout management in [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] gives the labels too much space and the rest not enough; making the space between the two '''<tt>LCDRange</tt>''' widgets change size. We'll fix that in the next chapter

=== Harjoitukset ===

Make a cheat button that, when pressed, makes the '''<tt>CannonField</tt>''' display the shot trajectory for five seconds.

If you did the "round shot" exercise from the previous chapter, try changing the '''<tt>shotRect()</tt>''' to a '''<tt>shotRegion()</tt>''' that returns a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] so you can have really accurate collision detection.

Make a moving target.

Make sure that the target is always created entirely on-screen.

Make sure that the widget cannot be resized so that the target isn't visible. [Hint: [http://doc.qt.nokia.com/latest/qwidget.html#minimumSize-prop Qt::Widget::setMinimumSize()] is your friend.]

Not easy; make it possible to have several shots in the air at the same time. [Hint: Make a '''<tt>Shot</tt>''' class.]

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/36/fi

2011-11-01T17:29:05Z

Centerlink: Created page with "=== Harjoitukset ==="

=== Harjoitukset ===

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/43/fi

2011-11-01T17:28:52Z

Centerlink: Created page with "Category:Ruby"

[[Category:Ruby]]

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/fi

2011-11-01T17:28:46Z

Centerlink: Created page with "=== Sovelluksen suorittaminen ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Hanging in the Air the Way Bricks Don't|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_11|Oppikurssi 11 - Ammutaan tykillä]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Oppikurssi 13 - Peli loppui]]
}}
== Hanging in the Air the Way Bricks Don't ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_12.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]

=== Overview ===

In this example, we extend our '''<tt>LCDRange</tt>''' class to include a text label. We also provide something to shoot at.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
def initialize(s, parent = nil)
super(parent)
init()
setText(s)
end
</syntaxhighlight>

This constructor first calls '''<tt>init()</tt>''' and then sets the label text. '''<tt>init()</tt>''' is a separate function performing initialization mosty because of function overloading matters in the original C++ version.

<syntaxhighlight lang="ruby">
def init()
lcd = Qt::LCDNumber.new(2)
lcd.setSegmentStyle(Qt::LCDNumber::Filled)

@slider = Qt::Slider.new(Qt::Horizontal)
@slider.setRange(0, 99)
@slider.setValue(0)

@label = Qt::Label.new()
@label.setAlignment(Qt::AlignHCenter.to_i | Qt::AlignTop.to_i)

connect(@slider, SIGNAL('valueChanged(int)'),
lcd, SLOT('display(int)'))
connect(@slider, SIGNAL('valueChanged(int)'),
self, SIGNAL('valueChanged(int)'))

layout = Qt::VBoxLayout.new()
layout.addWidget(lcd)
layout.addWidget(@slider)
layout.addWidget(@label)
setLayout(layout)

setFocusProxy(@slider)
end
</syntaxhighlight>

The setup of '''<tt>lcd</tt>''' and '''<tt>slider</tt>''' is the same as in the previous chapter. Next we create a [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] and tell it to align the contents centered horizontally and to the top vertically. The [http://doc.qt.nokia.com/latest/qobject.html#connect Qt::Object::connect()] calls have also been taken from the previous chapter.

<syntaxhighlight lang="ruby">
def setText(s)
@label.setText(s)
end
</syntaxhighlight>

This function sets the label text.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has two new signals: '''<tt>hit()</tt>''' and '''<tt>missed()</tt>'''. In addition, it contains a target.

<syntaxhighlight lang="ruby">
signals 'hit()', 'missed()' #...
</syntaxhighlight>

The '''<tt>hit()</tt>''' signal is emitted when a shot hits the target. The '''<tt>missed()</tt>''' signal is emitted when the shot moves beyond the right or bottom edge of the widget (i.e., it is certain that it has not and will not hit the target).

<syntaxhighlight lang="ruby">
newTarget()
</syntaxhighlight>

This line has been added to the constructor. It creates a "random" position for the target. In fact, the '''<tt>newTarget()</tt>''' function will try to paint the target. Because we are in a constructor, the '''<tt>CannonField</tt>''' widget is invisible. Qt guarantees that no harm is done when calling [http://doc.qt.nokia.com/latest/qwidget.html#update Qt::Widget::update()] on a hidden widget.

<syntaxhighlight lang="ruby">
@@first_time = true

def newTarget()
if @@first_time
@@first_time = false
midnight = Qt::Time.new(0, 0, 0)
srand(midnight.secsTo(Qt::Time.currentTime()))
end

@target = Qt::Point.new(200 + rand(190), 10 + rand(255))
update()
end
</syntaxhighlight>

This function creates a target center point at a new random position.

We create the [http://doc.qt.nokia.com/latest/qtime.html Qt::Time] object '''<tt>midnight</tt>''', which represents the time 00:00:00. Next we fetch the number of seconds from midnight until now and use it as a random seed. See the documentation for [http://doc.qt.nokia.com/latest/qdate.html Qt::Date], [http://doc.qt.nokia.com/latest/qtime.html Qt::Time], and [http://doc.qt.nokia.com/latest/qdatetime.html Qt::DateTime] for more information.

Finally we calculate the target's center point. We keep it within the rectangle (x = 200, y = 35, width = 190, height = 255), i.e., the possible x and y values are 200 to 389 and 35 to 289, respectively) in a coordinate system where we put y position 0 at the bottom edge of the widget and let y values increase upwards x is as normal, with 0 at the left edge and with x values increasing to the right.

By experimentation we have found this to always be in reach of the shot.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()
</syntaxhighlight>

This part of the timer event has not changed from the previous chapter.

<syntaxhighlight lang="ruby">
if shotR.intersects(targetRect())
@autoShootTimer.stop()
emit hit()
</syntaxhighlight>

This '''<tt>if</tt>''' statement checks whether the shot rectangle intersects the target rectangle. If it does, the shot has hit the target (ouch!). We stop the shoot timer and emit the '''<tt>hit()</tt>''' signal to tell the outside world that a target was destroyed, and return. Note that we could have created a new target on the spot, but because the '''<tt>CannonField</tt>''' is a component we leave such decisions to the user of the component.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
emit missed()
</syntaxhighlight>

This is the same as in the previous chapter, except that it now emits the '''<tt>missed()</tt>''' signal to tell the outside world about the failure.

<syntaxhighlight lang="ruby">
else
region = region.unite(Qt::Region.new(shotR))
end

update(region)
end
</syntaxhighlight>

And the rest of the function is as before.

'''<tt>CannonField::paintEvent()</tt>''' is as before, except that this has been added:

<syntaxhighlight lang="ruby">
paintTarget(painter)
</syntaxhighlight>

This line makes sure that the target is also painted when necessary.

<syntaxhighlight lang="ruby">
def paintTarget(painter)
painter.setBrush(Qt::Brush.new(Qt::red))
painter.setPen(Qt::Pen.new(Qt::Color.new(Qt::black)))
painter.drawRect(targetRect())
end
</syntaxhighlight>

This function paints the target; a rectangle filled with red and with a black outline.

<syntaxhighlight lang="ruby">
def targetRect()
result = Qt::Rect.new(0, 0, 20, 10)
result.moveCenter(Qt::Point.new(@target.x(), height() - 1 - @target.y()))
return result
end
</syntaxhighlight>

This private function returns the enclosing rectangle of the target. Remember from '''<tt>newTarget()</tt>''' that the '''<tt>target</tt>''' point uses y coordinate 0 at the bottom of the widget. We calculate the point in widget coordinates before we call [http://doc.qt.nokia.com/latest/qrect.html#moveCenter Qt::Rect::moveCenter()].

The reason we have chosen this coordinate mapping is to fix the distance between the target and the bottom of the widget. Remember that the widget can be resized by the user or the program at any time.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]'''

There are no new members in the '''<tt>MyWidget</tt>''' class, but we have slightly changed the constructor to set the new '''<tt>LCDRange</tt>''' text labels.

<syntaxhighlight lang="ruby">
angle = LCDRange.new(tr('ANGLE'))
</syntaxhighlight>

We set the angle text label to "ANGLE".

<syntaxhighlight lang="ruby">
force = LCDRange.new(tr('FORCE'))
</syntaxhighlight>

We set the force text label to "FORCE".

=== Sovelluksen suorittaminen ===

The '''<tt>LCDRange</tt>''' widgets look a bit strange: When resizing '''<tt>MyWidget</tt>''', the built-in layout management in [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] gives the labels too much space and the rest not enough; making the space between the two '''<tt>LCDRange</tt>''' widgets change size. We'll fix that in the next chapter

=== Exercises ===

Make a cheat button that, when pressed, makes the '''<tt>CannonField</tt>''' display the shot trajectory for five seconds.

If you did the "round shot" exercise from the previous chapter, try changing the '''<tt>shotRect()</tt>''' to a '''<tt>shotRegion()</tt>''' that returns a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] so you can have really accurate collision detection.

Make a moving target.

Make sure that the target is always created entirely on-screen.

Make sure that the widget cannot be resized so that the target isn't visible. [Hint: [http://doc.qt.nokia.com/latest/qwidget.html#minimumSize-prop Qt::Widget::setMinimumSize()] is your friend.]

Not easy; make it possible to have several shots in the air at the same time. [Hint: Make a '''<tt>Shot</tt>''' class.]

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/34/fi

2011-11-01T17:28:45Z

Centerlink: Created page with "=== Sovelluksen suorittaminen ==="

=== Sovelluksen suorittaminen ===

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/fi

2011-11-01T17:28:25Z

Centerlink: Created page with "=== Läpikäynti rivi riviltä ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Hanging in the Air the Way Bricks Don't|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_11|Oppikurssi 11 - Ammutaan tykillä]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Oppikurssi 13 - Peli loppui]]
}}
== Hanging in the Air the Way Bricks Don't ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_12.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]

=== Overview ===

In this example, we extend our '''<tt>LCDRange</tt>''' class to include a text label. We also provide something to shoot at.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
def initialize(s, parent = nil)
super(parent)
init()
setText(s)
end
</syntaxhighlight>

This constructor first calls '''<tt>init()</tt>''' and then sets the label text. '''<tt>init()</tt>''' is a separate function performing initialization mosty because of function overloading matters in the original C++ version.

<syntaxhighlight lang="ruby">
def init()
lcd = Qt::LCDNumber.new(2)
lcd.setSegmentStyle(Qt::LCDNumber::Filled)

@slider = Qt::Slider.new(Qt::Horizontal)
@slider.setRange(0, 99)
@slider.setValue(0)

@label = Qt::Label.new()
@label.setAlignment(Qt::AlignHCenter.to_i | Qt::AlignTop.to_i)

connect(@slider, SIGNAL('valueChanged(int)'),
lcd, SLOT('display(int)'))
connect(@slider, SIGNAL('valueChanged(int)'),
self, SIGNAL('valueChanged(int)'))

layout = Qt::VBoxLayout.new()
layout.addWidget(lcd)
layout.addWidget(@slider)
layout.addWidget(@label)
setLayout(layout)

setFocusProxy(@slider)
end
</syntaxhighlight>

The setup of '''<tt>lcd</tt>''' and '''<tt>slider</tt>''' is the same as in the previous chapter. Next we create a [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] and tell it to align the contents centered horizontally and to the top vertically. The [http://doc.qt.nokia.com/latest/qobject.html#connect Qt::Object::connect()] calls have also been taken from the previous chapter.

<syntaxhighlight lang="ruby">
def setText(s)
@label.setText(s)
end
</syntaxhighlight>

This function sets the label text.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has two new signals: '''<tt>hit()</tt>''' and '''<tt>missed()</tt>'''. In addition, it contains a target.

<syntaxhighlight lang="ruby">
signals 'hit()', 'missed()' #...
</syntaxhighlight>

The '''<tt>hit()</tt>''' signal is emitted when a shot hits the target. The '''<tt>missed()</tt>''' signal is emitted when the shot moves beyond the right or bottom edge of the widget (i.e., it is certain that it has not and will not hit the target).

<syntaxhighlight lang="ruby">
newTarget()
</syntaxhighlight>

This line has been added to the constructor. It creates a "random" position for the target. In fact, the '''<tt>newTarget()</tt>''' function will try to paint the target. Because we are in a constructor, the '''<tt>CannonField</tt>''' widget is invisible. Qt guarantees that no harm is done when calling [http://doc.qt.nokia.com/latest/qwidget.html#update Qt::Widget::update()] on a hidden widget.

<syntaxhighlight lang="ruby">
@@first_time = true

def newTarget()
if @@first_time
@@first_time = false
midnight = Qt::Time.new(0, 0, 0)
srand(midnight.secsTo(Qt::Time.currentTime()))
end

@target = Qt::Point.new(200 + rand(190), 10 + rand(255))
update()
end
</syntaxhighlight>

This function creates a target center point at a new random position.

We create the [http://doc.qt.nokia.com/latest/qtime.html Qt::Time] object '''<tt>midnight</tt>''', which represents the time 00:00:00. Next we fetch the number of seconds from midnight until now and use it as a random seed. See the documentation for [http://doc.qt.nokia.com/latest/qdate.html Qt::Date], [http://doc.qt.nokia.com/latest/qtime.html Qt::Time], and [http://doc.qt.nokia.com/latest/qdatetime.html Qt::DateTime] for more information.

Finally we calculate the target's center point. We keep it within the rectangle (x = 200, y = 35, width = 190, height = 255), i.e., the possible x and y values are 200 to 389 and 35 to 289, respectively) in a coordinate system where we put y position 0 at the bottom edge of the widget and let y values increase upwards x is as normal, with 0 at the left edge and with x values increasing to the right.

By experimentation we have found this to always be in reach of the shot.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()
</syntaxhighlight>

This part of the timer event has not changed from the previous chapter.

<syntaxhighlight lang="ruby">
if shotR.intersects(targetRect())
@autoShootTimer.stop()
emit hit()
</syntaxhighlight>

This '''<tt>if</tt>''' statement checks whether the shot rectangle intersects the target rectangle. If it does, the shot has hit the target (ouch!). We stop the shoot timer and emit the '''<tt>hit()</tt>''' signal to tell the outside world that a target was destroyed, and return. Note that we could have created a new target on the spot, but because the '''<tt>CannonField</tt>''' is a component we leave such decisions to the user of the component.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
emit missed()
</syntaxhighlight>

This is the same as in the previous chapter, except that it now emits the '''<tt>missed()</tt>''' signal to tell the outside world about the failure.

<syntaxhighlight lang="ruby">
else
region = region.unite(Qt::Region.new(shotR))
end

update(region)
end
</syntaxhighlight>

And the rest of the function is as before.

'''<tt>CannonField::paintEvent()</tt>''' is as before, except that this has been added:

<syntaxhighlight lang="ruby">
paintTarget(painter)
</syntaxhighlight>

This line makes sure that the target is also painted when necessary.

<syntaxhighlight lang="ruby">
def paintTarget(painter)
painter.setBrush(Qt::Brush.new(Qt::red))
painter.setPen(Qt::Pen.new(Qt::Color.new(Qt::black)))
painter.drawRect(targetRect())
end
</syntaxhighlight>

This function paints the target; a rectangle filled with red and with a black outline.

<syntaxhighlight lang="ruby">
def targetRect()
result = Qt::Rect.new(0, 0, 20, 10)
result.moveCenter(Qt::Point.new(@target.x(), height() - 1 - @target.y()))
return result
end
</syntaxhighlight>

This private function returns the enclosing rectangle of the target. Remember from '''<tt>newTarget()</tt>''' that the '''<tt>target</tt>''' point uses y coordinate 0 at the bottom of the widget. We calculate the point in widget coordinates before we call [http://doc.qt.nokia.com/latest/qrect.html#moveCenter Qt::Rect::moveCenter()].

The reason we have chosen this coordinate mapping is to fix the distance between the target and the bottom of the widget. Remember that the widget can be resized by the user or the program at any time.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]'''

There are no new members in the '''<tt>MyWidget</tt>''' class, but we have slightly changed the constructor to set the new '''<tt>LCDRange</tt>''' text labels.

<syntaxhighlight lang="ruby">
angle = LCDRange.new(tr('ANGLE'))
</syntaxhighlight>

We set the angle text label to "ANGLE".

<syntaxhighlight lang="ruby">
force = LCDRange.new(tr('FORCE'))
</syntaxhighlight>

We set the force text label to "FORCE".

=== Running the Application ===

The '''<tt>LCDRange</tt>''' widgets look a bit strange: When resizing '''<tt>MyWidget</tt>''', the built-in layout management in [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] gives the labels too much space and the rest not enough; making the space between the two '''<tt>LCDRange</tt>''' widgets change size. We'll fix that in the next chapter

=== Exercises ===

Make a cheat button that, when pressed, makes the '''<tt>CannonField</tt>''' display the shot trajectory for five seconds.

If you did the "round shot" exercise from the previous chapter, try changing the '''<tt>shotRect()</tt>''' to a '''<tt>shotRegion()</tt>''' that returns a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] so you can have really accurate collision detection.

Make a moving target.

Make sure that the target is always created entirely on-screen.

Make sure that the widget cannot be resized so that the target isn't visible. [Hint: [http://doc.qt.nokia.com/latest/qwidget.html#minimumSize-prop Qt::Widget::setMinimumSize()] is your friend.]

Not easy; make it possible to have several shots in the air at the same time. [Hint: Make a '''<tt>Shot</tt>''' class.]

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/11/fi

2011-11-01T17:28:25Z

Centerlink: Created page with "=== Läpikäynti rivi riviltä ==="

=== Läpikäynti rivi riviltä ===

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/7/fi

2011-11-01T17:28:09Z

Centerlink: Created page with "center"

[[Image:Qt4_Ruby_Tutorial_Screenshot_12.png|center]]

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/fi

2011-11-01T17:27:59Z

Centerlink: Created page with "Oppikurssi 11 - Ammutaan tykillä"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Hanging in the Air the Way Bricks Don't|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_11|Oppikurssi 11 - Ammutaan tykillä]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Oppikurssi 13 - Peli loppui]]
}}
== Hanging in the Air the Way Bricks Don't ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_12.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]

=== Overview ===

In this example, we extend our '''<tt>LCDRange</tt>''' class to include a text label. We also provide something to shoot at.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
def initialize(s, parent = nil)
super(parent)
init()
setText(s)
end
</syntaxhighlight>

This constructor first calls '''<tt>init()</tt>''' and then sets the label text. '''<tt>init()</tt>''' is a separate function performing initialization mosty because of function overloading matters in the original C++ version.

<syntaxhighlight lang="ruby">
def init()
lcd = Qt::LCDNumber.new(2)
lcd.setSegmentStyle(Qt::LCDNumber::Filled)

@slider = Qt::Slider.new(Qt::Horizontal)
@slider.setRange(0, 99)
@slider.setValue(0)

@label = Qt::Label.new()
@label.setAlignment(Qt::AlignHCenter.to_i | Qt::AlignTop.to_i)

connect(@slider, SIGNAL('valueChanged(int)'),
lcd, SLOT('display(int)'))
connect(@slider, SIGNAL('valueChanged(int)'),
self, SIGNAL('valueChanged(int)'))

layout = Qt::VBoxLayout.new()
layout.addWidget(lcd)
layout.addWidget(@slider)
layout.addWidget(@label)
setLayout(layout)

setFocusProxy(@slider)
end
</syntaxhighlight>

The setup of '''<tt>lcd</tt>''' and '''<tt>slider</tt>''' is the same as in the previous chapter. Next we create a [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] and tell it to align the contents centered horizontally and to the top vertically. The [http://doc.qt.nokia.com/latest/qobject.html#connect Qt::Object::connect()] calls have also been taken from the previous chapter.

<syntaxhighlight lang="ruby">
def setText(s)
@label.setText(s)
end
</syntaxhighlight>

This function sets the label text.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has two new signals: '''<tt>hit()</tt>''' and '''<tt>missed()</tt>'''. In addition, it contains a target.

<syntaxhighlight lang="ruby">
signals 'hit()', 'missed()' #...
</syntaxhighlight>

The '''<tt>hit()</tt>''' signal is emitted when a shot hits the target. The '''<tt>missed()</tt>''' signal is emitted when the shot moves beyond the right or bottom edge of the widget (i.e., it is certain that it has not and will not hit the target).

<syntaxhighlight lang="ruby">
newTarget()
</syntaxhighlight>

This line has been added to the constructor. It creates a "random" position for the target. In fact, the '''<tt>newTarget()</tt>''' function will try to paint the target. Because we are in a constructor, the '''<tt>CannonField</tt>''' widget is invisible. Qt guarantees that no harm is done when calling [http://doc.qt.nokia.com/latest/qwidget.html#update Qt::Widget::update()] on a hidden widget.

<syntaxhighlight lang="ruby">
@@first_time = true

def newTarget()
if @@first_time
@@first_time = false
midnight = Qt::Time.new(0, 0, 0)
srand(midnight.secsTo(Qt::Time.currentTime()))
end

@target = Qt::Point.new(200 + rand(190), 10 + rand(255))
update()
end
</syntaxhighlight>

This function creates a target center point at a new random position.

We create the [http://doc.qt.nokia.com/latest/qtime.html Qt::Time] object '''<tt>midnight</tt>''', which represents the time 00:00:00. Next we fetch the number of seconds from midnight until now and use it as a random seed. See the documentation for [http://doc.qt.nokia.com/latest/qdate.html Qt::Date], [http://doc.qt.nokia.com/latest/qtime.html Qt::Time], and [http://doc.qt.nokia.com/latest/qdatetime.html Qt::DateTime] for more information.

Finally we calculate the target's center point. We keep it within the rectangle (x = 200, y = 35, width = 190, height = 255), i.e., the possible x and y values are 200 to 389 and 35 to 289, respectively) in a coordinate system where we put y position 0 at the bottom edge of the widget and let y values increase upwards x is as normal, with 0 at the left edge and with x values increasing to the right.

By experimentation we have found this to always be in reach of the shot.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()
</syntaxhighlight>

This part of the timer event has not changed from the previous chapter.

<syntaxhighlight lang="ruby">
if shotR.intersects(targetRect())
@autoShootTimer.stop()
emit hit()
</syntaxhighlight>

This '''<tt>if</tt>''' statement checks whether the shot rectangle intersects the target rectangle. If it does, the shot has hit the target (ouch!). We stop the shoot timer and emit the '''<tt>hit()</tt>''' signal to tell the outside world that a target was destroyed, and return. Note that we could have created a new target on the spot, but because the '''<tt>CannonField</tt>''' is a component we leave such decisions to the user of the component.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
emit missed()
</syntaxhighlight>

This is the same as in the previous chapter, except that it now emits the '''<tt>missed()</tt>''' signal to tell the outside world about the failure.

<syntaxhighlight lang="ruby">
else
region = region.unite(Qt::Region.new(shotR))
end

update(region)
end
</syntaxhighlight>

And the rest of the function is as before.

'''<tt>CannonField::paintEvent()</tt>''' is as before, except that this has been added:

<syntaxhighlight lang="ruby">
paintTarget(painter)
</syntaxhighlight>

This line makes sure that the target is also painted when necessary.

<syntaxhighlight lang="ruby">
def paintTarget(painter)
painter.setBrush(Qt::Brush.new(Qt::red))
painter.setPen(Qt::Pen.new(Qt::Color.new(Qt::black)))
painter.drawRect(targetRect())
end
</syntaxhighlight>

This function paints the target; a rectangle filled with red and with a black outline.

<syntaxhighlight lang="ruby">
def targetRect()
result = Qt::Rect.new(0, 0, 20, 10)
result.moveCenter(Qt::Point.new(@target.x(), height() - 1 - @target.y()))
return result
end
</syntaxhighlight>

This private function returns the enclosing rectangle of the target. Remember from '''<tt>newTarget()</tt>''' that the '''<tt>target</tt>''' point uses y coordinate 0 at the bottom of the widget. We calculate the point in widget coordinates before we call [http://doc.qt.nokia.com/latest/qrect.html#moveCenter Qt::Rect::moveCenter()].

The reason we have chosen this coordinate mapping is to fix the distance between the target and the bottom of the widget. Remember that the widget can be resized by the user or the program at any time.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]'''

There are no new members in the '''<tt>MyWidget</tt>''' class, but we have slightly changed the constructor to set the new '''<tt>LCDRange</tt>''' text labels.

<syntaxhighlight lang="ruby">
angle = LCDRange.new(tr('ANGLE'))
</syntaxhighlight>

We set the angle text label to "ANGLE".

<syntaxhighlight lang="ruby">
force = LCDRange.new(tr('FORCE'))
</syntaxhighlight>

We set the force text label to "FORCE".

=== Running the Application ===

The '''<tt>LCDRange</tt>''' widgets look a bit strange: When resizing '''<tt>MyWidget</tt>''', the built-in layout management in [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] gives the labels too much space and the rest not enough; making the space between the two '''<tt>LCDRange</tt>''' widgets change size. We'll fix that in the next chapter

=== Exercises ===

Make a cheat button that, when pressed, makes the '''<tt>CannonField</tt>''' display the shot trajectory for five seconds.

If you did the "round shot" exercise from the previous chapter, try changing the '''<tt>shotRect()</tt>''' to a '''<tt>shotRegion()</tt>''' that returns a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] so you can have really accurate collision detection.

Make a moving target.

Make sure that the target is always created entirely on-screen.

Make sure that the widget cannot be resized so that the target isn't visible. [Hint: [http://doc.qt.nokia.com/latest/qwidget.html#minimumSize-prop Qt::Widget::setMinimumSize()] is your friend.]

Not easy; make it possible to have several shots in the air at the same time. [Hint: Make a '''<tt>Shot</tt>''' class.]

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/4/fi

2011-11-01T17:27:59Z

Centerlink: Created page with "Oppikurssi 11 - Ammutaan tykillä"

Oppikurssi 11 - Ammutaan tykillä

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/fi

2011-11-01T17:27:35Z

Centerlink: Created page with "Oppikurssi 13 - Peli loppui"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Hanging in the Air the Way Bricks Don't|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_11|Tutorial 11 - Giving It a Shot]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Oppikurssi 13 - Peli loppui]]
}}
== Hanging in the Air the Way Bricks Don't ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_12.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]

=== Overview ===

In this example, we extend our '''<tt>LCDRange</tt>''' class to include a text label. We also provide something to shoot at.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
def initialize(s, parent = nil)
super(parent)
init()
setText(s)
end
</syntaxhighlight>

This constructor first calls '''<tt>init()</tt>''' and then sets the label text. '''<tt>init()</tt>''' is a separate function performing initialization mosty because of function overloading matters in the original C++ version.

<syntaxhighlight lang="ruby">
def init()
lcd = Qt::LCDNumber.new(2)
lcd.setSegmentStyle(Qt::LCDNumber::Filled)

@slider = Qt::Slider.new(Qt::Horizontal)
@slider.setRange(0, 99)
@slider.setValue(0)

@label = Qt::Label.new()
@label.setAlignment(Qt::AlignHCenter.to_i | Qt::AlignTop.to_i)

connect(@slider, SIGNAL('valueChanged(int)'),
lcd, SLOT('display(int)'))
connect(@slider, SIGNAL('valueChanged(int)'),
self, SIGNAL('valueChanged(int)'))

layout = Qt::VBoxLayout.new()
layout.addWidget(lcd)
layout.addWidget(@slider)
layout.addWidget(@label)
setLayout(layout)

setFocusProxy(@slider)
end
</syntaxhighlight>

The setup of '''<tt>lcd</tt>''' and '''<tt>slider</tt>''' is the same as in the previous chapter. Next we create a [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] and tell it to align the contents centered horizontally and to the top vertically. The [http://doc.qt.nokia.com/latest/qobject.html#connect Qt::Object::connect()] calls have also been taken from the previous chapter.

<syntaxhighlight lang="ruby">
def setText(s)
@label.setText(s)
end
</syntaxhighlight>

This function sets the label text.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has two new signals: '''<tt>hit()</tt>''' and '''<tt>missed()</tt>'''. In addition, it contains a target.

<syntaxhighlight lang="ruby">
signals 'hit()', 'missed()' #...
</syntaxhighlight>

The '''<tt>hit()</tt>''' signal is emitted when a shot hits the target. The '''<tt>missed()</tt>''' signal is emitted when the shot moves beyond the right or bottom edge of the widget (i.e., it is certain that it has not and will not hit the target).

<syntaxhighlight lang="ruby">
newTarget()
</syntaxhighlight>

This line has been added to the constructor. It creates a "random" position for the target. In fact, the '''<tt>newTarget()</tt>''' function will try to paint the target. Because we are in a constructor, the '''<tt>CannonField</tt>''' widget is invisible. Qt guarantees that no harm is done when calling [http://doc.qt.nokia.com/latest/qwidget.html#update Qt::Widget::update()] on a hidden widget.

<syntaxhighlight lang="ruby">
@@first_time = true

def newTarget()
if @@first_time
@@first_time = false
midnight = Qt::Time.new(0, 0, 0)
srand(midnight.secsTo(Qt::Time.currentTime()))
end

@target = Qt::Point.new(200 + rand(190), 10 + rand(255))
update()
end
</syntaxhighlight>

This function creates a target center point at a new random position.

We create the [http://doc.qt.nokia.com/latest/qtime.html Qt::Time] object '''<tt>midnight</tt>''', which represents the time 00:00:00. Next we fetch the number of seconds from midnight until now and use it as a random seed. See the documentation for [http://doc.qt.nokia.com/latest/qdate.html Qt::Date], [http://doc.qt.nokia.com/latest/qtime.html Qt::Time], and [http://doc.qt.nokia.com/latest/qdatetime.html Qt::DateTime] for more information.

Finally we calculate the target's center point. We keep it within the rectangle (x = 200, y = 35, width = 190, height = 255), i.e., the possible x and y values are 200 to 389 and 35 to 289, respectively) in a coordinate system where we put y position 0 at the bottom edge of the widget and let y values increase upwards x is as normal, with 0 at the left edge and with x values increasing to the right.

By experimentation we have found this to always be in reach of the shot.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()
</syntaxhighlight>

This part of the timer event has not changed from the previous chapter.

<syntaxhighlight lang="ruby">
if shotR.intersects(targetRect())
@autoShootTimer.stop()
emit hit()
</syntaxhighlight>

This '''<tt>if</tt>''' statement checks whether the shot rectangle intersects the target rectangle. If it does, the shot has hit the target (ouch!). We stop the shoot timer and emit the '''<tt>hit()</tt>''' signal to tell the outside world that a target was destroyed, and return. Note that we could have created a new target on the spot, but because the '''<tt>CannonField</tt>''' is a component we leave such decisions to the user of the component.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
emit missed()
</syntaxhighlight>

This is the same as in the previous chapter, except that it now emits the '''<tt>missed()</tt>''' signal to tell the outside world about the failure.

<syntaxhighlight lang="ruby">
else
region = region.unite(Qt::Region.new(shotR))
end

update(region)
end
</syntaxhighlight>

And the rest of the function is as before.

'''<tt>CannonField::paintEvent()</tt>''' is as before, except that this has been added:

<syntaxhighlight lang="ruby">
paintTarget(painter)
</syntaxhighlight>

This line makes sure that the target is also painted when necessary.

<syntaxhighlight lang="ruby">
def paintTarget(painter)
painter.setBrush(Qt::Brush.new(Qt::red))
painter.setPen(Qt::Pen.new(Qt::Color.new(Qt::black)))
painter.drawRect(targetRect())
end
</syntaxhighlight>

This function paints the target; a rectangle filled with red and with a black outline.

<syntaxhighlight lang="ruby">
def targetRect()
result = Qt::Rect.new(0, 0, 20, 10)
result.moveCenter(Qt::Point.new(@target.x(), height() - 1 - @target.y()))
return result
end
</syntaxhighlight>

This private function returns the enclosing rectangle of the target. Remember from '''<tt>newTarget()</tt>''' that the '''<tt>target</tt>''' point uses y coordinate 0 at the bottom of the widget. We calculate the point in widget coordinates before we call [http://doc.qt.nokia.com/latest/qrect.html#moveCenter Qt::Rect::moveCenter()].

The reason we have chosen this coordinate mapping is to fix the distance between the target and the bottom of the widget. Remember that the widget can be resized by the user or the program at any time.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]'''

There are no new members in the '''<tt>MyWidget</tt>''' class, but we have slightly changed the constructor to set the new '''<tt>LCDRange</tt>''' text labels.

<syntaxhighlight lang="ruby">
angle = LCDRange.new(tr('ANGLE'))
</syntaxhighlight>

We set the angle text label to "ANGLE".

<syntaxhighlight lang="ruby">
force = LCDRange.new(tr('FORCE'))
</syntaxhighlight>

We set the force text label to "FORCE".

=== Running the Application ===

The '''<tt>LCDRange</tt>''' widgets look a bit strange: When resizing '''<tt>MyWidget</tt>''', the built-in layout management in [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] gives the labels too much space and the rest not enough; making the space between the two '''<tt>LCDRange</tt>''' widgets change size. We'll fix that in the next chapter

=== Exercises ===

Make a cheat button that, when pressed, makes the '''<tt>CannonField</tt>''' display the shot trajectory for five seconds.

If you did the "round shot" exercise from the previous chapter, try changing the '''<tt>shotRect()</tt>''' to a '''<tt>shotRegion()</tt>''' that returns a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] so you can have really accurate collision detection.

Make a moving target.

Make sure that the target is always created entirely on-screen.

Make sure that the widget cannot be resized so that the target isn't visible. [Hint: [http://doc.qt.nokia.com/latest/qwidget.html#minimumSize-prop Qt::Widget::setMinimumSize()] is your friend.]

Not easy; make it possible to have several shots in the air at the same time. [Hint: Make a '''<tt>Shot</tt>''' class.]

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/5/fi

2011-11-01T17:27:35Z

Centerlink: Created page with "Oppikurssi 13 - Peli loppui"

Oppikurssi 13 - Peli loppui

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/fi

2011-11-01T17:27:10Z

Centerlink: Created page with "Qt4 Ruby -oppikurssi"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Hanging in the Air the Way Bricks Don't|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_11|Tutorial 11 - Giving It a Shot]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Tutorial 13 - Game Over]]
}}
== Hanging in the Air the Way Bricks Don't ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_12.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]

=== Overview ===

In this example, we extend our '''<tt>LCDRange</tt>''' class to include a text label. We also provide something to shoot at.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
def initialize(s, parent = nil)
super(parent)
init()
setText(s)
end
</syntaxhighlight>

This constructor first calls '''<tt>init()</tt>''' and then sets the label text. '''<tt>init()</tt>''' is a separate function performing initialization mosty because of function overloading matters in the original C++ version.

<syntaxhighlight lang="ruby">
def init()
lcd = Qt::LCDNumber.new(2)
lcd.setSegmentStyle(Qt::LCDNumber::Filled)

@slider = Qt::Slider.new(Qt::Horizontal)
@slider.setRange(0, 99)
@slider.setValue(0)

@label = Qt::Label.new()
@label.setAlignment(Qt::AlignHCenter.to_i | Qt::AlignTop.to_i)

connect(@slider, SIGNAL('valueChanged(int)'),
lcd, SLOT('display(int)'))
connect(@slider, SIGNAL('valueChanged(int)'),
self, SIGNAL('valueChanged(int)'))

layout = Qt::VBoxLayout.new()
layout.addWidget(lcd)
layout.addWidget(@slider)
layout.addWidget(@label)
setLayout(layout)

setFocusProxy(@slider)
end
</syntaxhighlight>

The setup of '''<tt>lcd</tt>''' and '''<tt>slider</tt>''' is the same as in the previous chapter. Next we create a [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] and tell it to align the contents centered horizontally and to the top vertically. The [http://doc.qt.nokia.com/latest/qobject.html#connect Qt::Object::connect()] calls have also been taken from the previous chapter.

<syntaxhighlight lang="ruby">
def setText(s)
@label.setText(s)
end
</syntaxhighlight>

This function sets the label text.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has two new signals: '''<tt>hit()</tt>''' and '''<tt>missed()</tt>'''. In addition, it contains a target.

<syntaxhighlight lang="ruby">
signals 'hit()', 'missed()' #...
</syntaxhighlight>

The '''<tt>hit()</tt>''' signal is emitted when a shot hits the target. The '''<tt>missed()</tt>''' signal is emitted when the shot moves beyond the right or bottom edge of the widget (i.e., it is certain that it has not and will not hit the target).

<syntaxhighlight lang="ruby">
newTarget()
</syntaxhighlight>

This line has been added to the constructor. It creates a "random" position for the target. In fact, the '''<tt>newTarget()</tt>''' function will try to paint the target. Because we are in a constructor, the '''<tt>CannonField</tt>''' widget is invisible. Qt guarantees that no harm is done when calling [http://doc.qt.nokia.com/latest/qwidget.html#update Qt::Widget::update()] on a hidden widget.

<syntaxhighlight lang="ruby">
@@first_time = true

def newTarget()
if @@first_time
@@first_time = false
midnight = Qt::Time.new(0, 0, 0)
srand(midnight.secsTo(Qt::Time.currentTime()))
end

@target = Qt::Point.new(200 + rand(190), 10 + rand(255))
update()
end
</syntaxhighlight>

This function creates a target center point at a new random position.

We create the [http://doc.qt.nokia.com/latest/qtime.html Qt::Time] object '''<tt>midnight</tt>''', which represents the time 00:00:00. Next we fetch the number of seconds from midnight until now and use it as a random seed. See the documentation for [http://doc.qt.nokia.com/latest/qdate.html Qt::Date], [http://doc.qt.nokia.com/latest/qtime.html Qt::Time], and [http://doc.qt.nokia.com/latest/qdatetime.html Qt::DateTime] for more information.

Finally we calculate the target's center point. We keep it within the rectangle (x = 200, y = 35, width = 190, height = 255), i.e., the possible x and y values are 200 to 389 and 35 to 289, respectively) in a coordinate system where we put y position 0 at the bottom edge of the widget and let y values increase upwards x is as normal, with 0 at the left edge and with x values increasing to the right.

By experimentation we have found this to always be in reach of the shot.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()
</syntaxhighlight>

This part of the timer event has not changed from the previous chapter.

<syntaxhighlight lang="ruby">
if shotR.intersects(targetRect())
@autoShootTimer.stop()
emit hit()
</syntaxhighlight>

This '''<tt>if</tt>''' statement checks whether the shot rectangle intersects the target rectangle. If it does, the shot has hit the target (ouch!). We stop the shoot timer and emit the '''<tt>hit()</tt>''' signal to tell the outside world that a target was destroyed, and return. Note that we could have created a new target on the spot, but because the '''<tt>CannonField</tt>''' is a component we leave such decisions to the user of the component.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
emit missed()
</syntaxhighlight>

This is the same as in the previous chapter, except that it now emits the '''<tt>missed()</tt>''' signal to tell the outside world about the failure.

<syntaxhighlight lang="ruby">
else
region = region.unite(Qt::Region.new(shotR))
end

update(region)
end
</syntaxhighlight>

And the rest of the function is as before.

'''<tt>CannonField::paintEvent()</tt>''' is as before, except that this has been added:

<syntaxhighlight lang="ruby">
paintTarget(painter)
</syntaxhighlight>

This line makes sure that the target is also painted when necessary.

<syntaxhighlight lang="ruby">
def paintTarget(painter)
painter.setBrush(Qt::Brush.new(Qt::red))
painter.setPen(Qt::Pen.new(Qt::Color.new(Qt::black)))
painter.drawRect(targetRect())
end
</syntaxhighlight>

This function paints the target; a rectangle filled with red and with a black outline.

<syntaxhighlight lang="ruby">
def targetRect()
result = Qt::Rect.new(0, 0, 20, 10)
result.moveCenter(Qt::Point.new(@target.x(), height() - 1 - @target.y()))
return result
end
</syntaxhighlight>

This private function returns the enclosing rectangle of the target. Remember from '''<tt>newTarget()</tt>''' that the '''<tt>target</tt>''' point uses y coordinate 0 at the bottom of the widget. We calculate the point in widget coordinates before we call [http://doc.qt.nokia.com/latest/qrect.html#moveCenter Qt::Rect::moveCenter()].

The reason we have chosen this coordinate mapping is to fix the distance between the target and the bottom of the widget. Remember that the widget can be resized by the user or the program at any time.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]'''

There are no new members in the '''<tt>MyWidget</tt>''' class, but we have slightly changed the constructor to set the new '''<tt>LCDRange</tt>''' text labels.

<syntaxhighlight lang="ruby">
angle = LCDRange.new(tr('ANGLE'))
</syntaxhighlight>

We set the angle text label to "ANGLE".

<syntaxhighlight lang="ruby">
force = LCDRange.new(tr('FORCE'))
</syntaxhighlight>

We set the force text label to "FORCE".

=== Running the Application ===

The '''<tt>LCDRange</tt>''' widgets look a bit strange: When resizing '''<tt>MyWidget</tt>''', the built-in layout management in [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] gives the labels too much space and the rest not enough; making the space between the two '''<tt>LCDRange</tt>''' widgets change size. We'll fix that in the next chapter

=== Exercises ===

Make a cheat button that, when pressed, makes the '''<tt>CannonField</tt>''' display the shot trajectory for five seconds.

If you did the "round shot" exercise from the previous chapter, try changing the '''<tt>shotRect()</tt>''' to a '''<tt>shotRegion()</tt>''' that returns a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] so you can have really accurate collision detection.

Make a moving target.

Make sure that the target is always created entirely on-screen.

Make sure that the widget cannot be resized so that the target isn't visible. [Hint: [http://doc.qt.nokia.com/latest/qwidget.html#minimumSize-prop Qt::Widget::setMinimumSize()] is your friend.]

Not easy; make it possible to have several shots in the air at the same time. [Hint: Make a '''<tt>Shot</tt>''' class.]

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/2/fi

2011-11-01T17:27:10Z

Centerlink: Created page with "Qt4 Ruby -oppikurssi"

Qt4 Ruby -oppikurssi

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/1/fi

2011-11-01T17:26:57Z

Centerlink: Created page with "TutorialBrowser"

TutorialBrowser

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12/fi

2011-11-01T17:26:57Z

Centerlink: Created page with "TutorialBrowser"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 12}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby Tutorial]]|
name=Hanging in the Air the Way Bricks Don't|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_11|Tutorial 11 - Giving It a Shot]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_13|Tutorial 13 - Game Over]]
}}
== Hanging in the Air the Way Bricks Don't ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_12.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]

=== Overview ===

In this example, we extend our '''<tt>LCDRange</tt>''' class to include a text label. We also provide something to shoot at.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/lcdrange.rb lcdrange.rb]'''

<syntaxhighlight lang="ruby">
def initialize(s, parent = nil)
super(parent)
init()
setText(s)
end
</syntaxhighlight>

This constructor first calls '''<tt>init()</tt>''' and then sets the label text. '''<tt>init()</tt>''' is a separate function performing initialization mosty because of function overloading matters in the original C++ version.

<syntaxhighlight lang="ruby">
def init()
lcd = Qt::LCDNumber.new(2)
lcd.setSegmentStyle(Qt::LCDNumber::Filled)

@slider = Qt::Slider.new(Qt::Horizontal)
@slider.setRange(0, 99)
@slider.setValue(0)

@label = Qt::Label.new()
@label.setAlignment(Qt::AlignHCenter.to_i | Qt::AlignTop.to_i)

connect(@slider, SIGNAL('valueChanged(int)'),
lcd, SLOT('display(int)'))
connect(@slider, SIGNAL('valueChanged(int)'),
self, SIGNAL('valueChanged(int)'))

layout = Qt::VBoxLayout.new()
layout.addWidget(lcd)
layout.addWidget(@slider)
layout.addWidget(@label)
setLayout(layout)

setFocusProxy(@slider)
end
</syntaxhighlight>

The setup of '''<tt>lcd</tt>''' and '''<tt>slider</tt>''' is the same as in the previous chapter. Next we create a [http://doc.qt.nokia.com/latest/qlabel.html Qt::Label] and tell it to align the contents centered horizontally and to the top vertically. The [http://doc.qt.nokia.com/latest/qobject.html#connect Qt::Object::connect()] calls have also been taken from the previous chapter.

<syntaxhighlight lang="ruby">
def setText(s)
@label.setText(s)
end
</syntaxhighlight>

This function sets the label text.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has two new signals: '''<tt>hit()</tt>''' and '''<tt>missed()</tt>'''. In addition, it contains a target.

<syntaxhighlight lang="ruby">
signals 'hit()', 'missed()' #...
</syntaxhighlight>

The '''<tt>hit()</tt>''' signal is emitted when a shot hits the target. The '''<tt>missed()</tt>''' signal is emitted when the shot moves beyond the right or bottom edge of the widget (i.e., it is certain that it has not and will not hit the target).

<syntaxhighlight lang="ruby">
newTarget()
</syntaxhighlight>

This line has been added to the constructor. It creates a "random" position for the target. In fact, the '''<tt>newTarget()</tt>''' function will try to paint the target. Because we are in a constructor, the '''<tt>CannonField</tt>''' widget is invisible. Qt guarantees that no harm is done when calling [http://doc.qt.nokia.com/latest/qwidget.html#update Qt::Widget::update()] on a hidden widget.

<syntaxhighlight lang="ruby">
@@first_time = true

def newTarget()
if @@first_time
@@first_time = false
midnight = Qt::Time.new(0, 0, 0)
srand(midnight.secsTo(Qt::Time.currentTime()))
end

@target = Qt::Point.new(200 + rand(190), 10 + rand(255))
update()
end
</syntaxhighlight>

This function creates a target center point at a new random position.

We create the [http://doc.qt.nokia.com/latest/qtime.html Qt::Time] object '''<tt>midnight</tt>''', which represents the time 00:00:00. Next we fetch the number of seconds from midnight until now and use it as a random seed. See the documentation for [http://doc.qt.nokia.com/latest/qdate.html Qt::Date], [http://doc.qt.nokia.com/latest/qtime.html Qt::Time], and [http://doc.qt.nokia.com/latest/qdatetime.html Qt::DateTime] for more information.

Finally we calculate the target's center point. We keep it within the rectangle (x = 200, y = 35, width = 190, height = 255), i.e., the possible x and y values are 200 to 389 and 35 to 289, respectively) in a coordinate system where we put y position 0 at the bottom edge of the widget and let y values increase upwards x is as normal, with 0 at the left edge and with x values increasing to the right.

By experimentation we have found this to always be in reach of the shot.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()
</syntaxhighlight>

This part of the timer event has not changed from the previous chapter.

<syntaxhighlight lang="ruby">
if shotR.intersects(targetRect())
@autoShootTimer.stop()
emit hit()
</syntaxhighlight>

This '''<tt>if</tt>''' statement checks whether the shot rectangle intersects the target rectangle. If it does, the shot has hit the target (ouch!). We stop the shoot timer and emit the '''<tt>hit()</tt>''' signal to tell the outside world that a target was destroyed, and return. Note that we could have created a new target on the spot, but because the '''<tt>CannonField</tt>''' is a component we leave such decisions to the user of the component.

<syntaxhighlight lang="ruby">
elsif shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
emit missed()
</syntaxhighlight>

This is the same as in the previous chapter, except that it now emits the '''<tt>missed()</tt>''' signal to tell the outside world about the failure.

<syntaxhighlight lang="ruby">
else
region = region.unite(Qt::Region.new(shotR))
end

update(region)
end
</syntaxhighlight>

And the rest of the function is as before.

'''<tt>CannonField::paintEvent()</tt>''' is as before, except that this has been added:

<syntaxhighlight lang="ruby">
paintTarget(painter)
</syntaxhighlight>

This line makes sure that the target is also painted when necessary.

<syntaxhighlight lang="ruby">
def paintTarget(painter)
painter.setBrush(Qt::Brush.new(Qt::red))
painter.setPen(Qt::Pen.new(Qt::Color.new(Qt::black)))
painter.drawRect(targetRect())
end
</syntaxhighlight>

This function paints the target; a rectangle filled with red and with a black outline.

<syntaxhighlight lang="ruby">
def targetRect()
result = Qt::Rect.new(0, 0, 20, 10)
result.moveCenter(Qt::Point.new(@target.x(), height() - 1 - @target.y()))
return result
end
</syntaxhighlight>

This private function returns the enclosing rectangle of the target. Remember from '''<tt>newTarget()</tt>''' that the '''<tt>target</tt>''' point uses y coordinate 0 at the bottom of the widget. We calculate the point in widget coordinates before we call [http://doc.qt.nokia.com/latest/qrect.html#moveCenter Qt::Rect::moveCenter()].

The reason we have chosen this coordinate mapping is to fix the distance between the target and the bottom of the widget. Remember that the widget can be resized by the user or the program at any time.

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t12/t12.rb t12.rb]'''

There are no new members in the '''<tt>MyWidget</tt>''' class, but we have slightly changed the constructor to set the new '''<tt>LCDRange</tt>''' text labels.

<syntaxhighlight lang="ruby">
angle = LCDRange.new(tr('ANGLE'))
</syntaxhighlight>

We set the angle text label to "ANGLE".

<syntaxhighlight lang="ruby">
force = LCDRange.new(tr('FORCE'))
</syntaxhighlight>

We set the force text label to "FORCE".

=== Running the Application ===

The '''<tt>LCDRange</tt>''' widgets look a bit strange: When resizing '''<tt>MyWidget</tt>''', the built-in layout management in [http://doc.qt.nokia.com/latest/qvboxlayout.html Qt::VBoxLayout] gives the labels too much space and the rest not enough; making the space between the two '''<tt>LCDRange</tt>''' widgets change size. We'll fix that in the next chapter

=== Exercises ===

Make a cheat button that, when pressed, makes the '''<tt>CannonField</tt>''' display the shot trajectory for five seconds.

If you did the "round shot" exercise from the previous chapter, try changing the '''<tt>shotRect()</tt>''' to a '''<tt>shotRegion()</tt>''' that returns a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] so you can have really accurate collision detection.

Make a moving target.

Make sure that the target is always created entirely on-screen.

Make sure that the widget cannot be resized so that the target isn't visible. [Hint: [http://doc.qt.nokia.com/latest/qwidget.html#minimumSize-prop Qt::Widget::setMinimumSize()] is your friend.]

Not easy; make it possible to have several shots in the air at the same time. [Hint: Make a '''<tt>Shot</tt>''' class.]

[[Category:Ruby]]

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/fi

2011-10-29T12:46:34Z

Centerlink: Created page with "Kanuuna voi laukaista, mutta ei ole mitään mitä ampua."

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Giving It a Shot|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_10|Oppikurssi 10 - Sileää kuin silkki]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]
}}
== Giving It a Shot ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_11.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]

=== Yleiskuva ===

In this example we introduce a timer to implement animated shooting.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has shooting capabilities.

<syntaxhighlight lang="ruby">
include Math
</syntaxhighlight>

We include '''<tt>Math</tt>''' because we need the '''<tt>sin()</tt>''' and '''<tt>cos()</tt>''' functions.

<syntaxhighlight lang="ruby">
@timerCount = 0

@autoShootTimer = Qt::Timer.new(self)
connect(@autoShootTimer, SIGNAL('timeout()'),
self, SLOT('moveShot()'))

@shootAngle = 0
@shootForce = 0
</syntaxhighlight>

We initialize our new private variables and connect the [http://doc.qt.nokia.com/latest/qtimer.html#timeout Qt::Timer::timeout()] signal to our '''<tt>moveShot()</tt>''' slot. We'll move the shot every time the timer times out.

The '''<tt>timerCount</tt>''' keeps track of the time passed since the shot was fired. The '''<tt>shootAngle</tt>''' is the cannon angle and '''<tt>shootForce</tt>''' is the cannon force when the shot was fired.

<syntaxhighlight lang="ruby">
def shoot()
if @autoShootTimer.isActive()
return
end;

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
end
</syntaxhighlight>

This function shoots a shot unless a shot is in the air. The '''<tt>timerCount</tt>''' is reset to zero. The '''<tt>shootAngle</tt>''' and '''<tt>shootForce</tt>''' variables are set to the current cannon angle and force. Finally, we start the timer.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()

if shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
else
region = region.unite(Qt::Region.new(shotR))
end
update(region)
end
</syntaxhighlight>

'''<tt>moveShot()</tt>''' is the slot that moves the shot, called every 5 milliseconds when the [http://doc.qt.nokia.com/latest/qtimer.html Qt::Timer] fires.

Its tasks are to compute the new position, update the screen with the shot in the new position, and if necessary, stop the timer.

First we make a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] that holds the old '''<tt>shotRect()</tt>'''. A [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] is capable of holding any sort of region, and we'll use it here to simplify the painting. '''<tt>shotRect()</tt>''' returns the rectangle where the shot is now. It is explained in detail later.

Then we increment the '''<tt>timerCount</tt>''', which has the effect of moving the shot one step along its trajectory.

Next we fetch the new shot rectangle.

If the shot has moved beyond the right or bottom edge of the widget we stop the timer, or we add the new '''<tt>shotRect()</tt>''' to the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region].

Finally, we repaint the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region]. This will send a single paint event for just the one or two rectangles that need updating.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

paintCannon(painter)
if @autoShootTimer.isActive()
paintShot(painter)
end

painter.end()
end
</syntaxhighlight>

The paint event function has been simplified since the previous chapter. Most of the logic has been moved to the new '''<tt>paintShot()</tt>''' and '''<tt>paintCannon()</tt>''' functions.

<syntaxhighlight lang="ruby">
def paintShot(painter)
painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::black))
painter.drawRect(shotRect())
end
</syntaxhighlight>

This private function paints the shot by drawing a black filled rectangle.

We leave out the implementation of '''<tt>paintCannon()</tt>'''; it is the same as the [http://doc.qt.nokia.com/latest/qwidget.html#paintEvent Qt::Widget::paintEvent()] reimplementation from the previous chapter.

<syntaxhighlight lang="ruby">
def shotRect()
gravity = 4.0

time = @timerCount / 20.0
velocity = @shootForce
radians = @shootAngle * 3.14159265 / 180.0

velx = velocity * cos(radians)
vely = velocity * sin(radians)
x0 = (@barrelRect.right() + 5.0) * cos(radians)
y0 = (@barrelRect.right() + 5.0) * sin(radians)
x = x0 + velx * time
y = y0 + vely * time - 0.5 * gravity * time * time

result = Qt::Rect.new(0, 0, 6, 6)
result.moveCenter(Qt::Point.new(x.round, height() - 1 - y.round))
return result
end
</syntaxhighlight>

This private function calculates the center point of the shot and returns the enclosing rectangle of the shot. It uses the initial cannon force and angle in addition to '''<tt>timerCount</tt>''', which increases as time passes.

The formula used is the standard Newtonian formula for frictionless movement in a gravity field. For simplicity, we've chosen to disregard any Einsteinian effects.

We calculate the center point in a coordinate system where y coordinates increase upward. After we have calculated the center point, we construct a [http://doc.qt.nokia.com/latest/qrect.html Qt::Rect] with size 6 x 6 and move its center point to the point calculated above. In the same operation we convert the point into the widget's coordinate system (see [http://doc.qt.nokia.com/latest/coordsys.html The Coordinate System]).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]'''

The only addition is the Shoot button.

<syntaxhighlight lang="ruby">
shoot = Qt::PushButton.new(tr('&Shoot'))
shoot.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))
</syntaxhighlight>

In the constructor we create and set up the Shoot button exactly like we did with the Quit button.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), cannonField, SLOT('shoot()'))
</syntaxhighlight>

Connects the '''<tt>clicked()</tt>''' signal of the Shoot button to the '''<tt>shoot()</tt>''' slot of the '''<tt>CannonField</tt>'''.

=== Sovelluksen suorittaminen ===

Kanuuna voi laukaista, mutta ei ole mitään mitä ampua.

=== Harjoitukset ===

Tee laukauksesta täytetty ympyrä. [Vihje: [http://doc.qt.nokia.com/latest/qpainter.html#drawEllipse Qt::Painter::drawEllipse()] saattaa auttaa.]

Vaihda kanuunan väriä kun laukaus on ilmassa.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/34/fi

2011-10-29T12:46:34Z

Centerlink: Created page with "Kanuuna voi laukaista, mutta ei ole mitään mitä ampua."

Kanuuna voi laukaista, mutta ei ole mitään mitä ampua.

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/fi

2011-10-29T12:45:36Z

Centerlink: Created page with "Tee laukauksesta täytetty ympyrä. [Vihje: [http://doc.qt.nokia.com/latest/qpainter.html#drawEllipse Qt::Painter::drawEllipse()] saattaa auttaa.]"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Giving It a Shot|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_10|Oppikurssi 10 - Sileää kuin silkki]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]
}}
== Giving It a Shot ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_11.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]

=== Yleiskuva ===

In this example we introduce a timer to implement animated shooting.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has shooting capabilities.

<syntaxhighlight lang="ruby">
include Math
</syntaxhighlight>

We include '''<tt>Math</tt>''' because we need the '''<tt>sin()</tt>''' and '''<tt>cos()</tt>''' functions.

<syntaxhighlight lang="ruby">
@timerCount = 0

@autoShootTimer = Qt::Timer.new(self)
connect(@autoShootTimer, SIGNAL('timeout()'),
self, SLOT('moveShot()'))

@shootAngle = 0
@shootForce = 0
</syntaxhighlight>

We initialize our new private variables and connect the [http://doc.qt.nokia.com/latest/qtimer.html#timeout Qt::Timer::timeout()] signal to our '''<tt>moveShot()</tt>''' slot. We'll move the shot every time the timer times out.

The '''<tt>timerCount</tt>''' keeps track of the time passed since the shot was fired. The '''<tt>shootAngle</tt>''' is the cannon angle and '''<tt>shootForce</tt>''' is the cannon force when the shot was fired.

<syntaxhighlight lang="ruby">
def shoot()
if @autoShootTimer.isActive()
return
end;

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
end
</syntaxhighlight>

This function shoots a shot unless a shot is in the air. The '''<tt>timerCount</tt>''' is reset to zero. The '''<tt>shootAngle</tt>''' and '''<tt>shootForce</tt>''' variables are set to the current cannon angle and force. Finally, we start the timer.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()

if shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
else
region = region.unite(Qt::Region.new(shotR))
end
update(region)
end
</syntaxhighlight>

'''<tt>moveShot()</tt>''' is the slot that moves the shot, called every 5 milliseconds when the [http://doc.qt.nokia.com/latest/qtimer.html Qt::Timer] fires.

Its tasks are to compute the new position, update the screen with the shot in the new position, and if necessary, stop the timer.

First we make a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] that holds the old '''<tt>shotRect()</tt>'''. A [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] is capable of holding any sort of region, and we'll use it here to simplify the painting. '''<tt>shotRect()</tt>''' returns the rectangle where the shot is now. It is explained in detail later.

Then we increment the '''<tt>timerCount</tt>''', which has the effect of moving the shot one step along its trajectory.

Next we fetch the new shot rectangle.

If the shot has moved beyond the right or bottom edge of the widget we stop the timer, or we add the new '''<tt>shotRect()</tt>''' to the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region].

Finally, we repaint the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region]. This will send a single paint event for just the one or two rectangles that need updating.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

paintCannon(painter)
if @autoShootTimer.isActive()
paintShot(painter)
end

painter.end()
end
</syntaxhighlight>

The paint event function has been simplified since the previous chapter. Most of the logic has been moved to the new '''<tt>paintShot()</tt>''' and '''<tt>paintCannon()</tt>''' functions.

<syntaxhighlight lang="ruby">
def paintShot(painter)
painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::black))
painter.drawRect(shotRect())
end
</syntaxhighlight>

This private function paints the shot by drawing a black filled rectangle.

We leave out the implementation of '''<tt>paintCannon()</tt>'''; it is the same as the [http://doc.qt.nokia.com/latest/qwidget.html#paintEvent Qt::Widget::paintEvent()] reimplementation from the previous chapter.

<syntaxhighlight lang="ruby">
def shotRect()
gravity = 4.0

time = @timerCount / 20.0
velocity = @shootForce
radians = @shootAngle * 3.14159265 / 180.0

velx = velocity * cos(radians)
vely = velocity * sin(radians)
x0 = (@barrelRect.right() + 5.0) * cos(radians)
y0 = (@barrelRect.right() + 5.0) * sin(radians)
x = x0 + velx * time
y = y0 + vely * time - 0.5 * gravity * time * time

result = Qt::Rect.new(0, 0, 6, 6)
result.moveCenter(Qt::Point.new(x.round, height() - 1 - y.round))
return result
end
</syntaxhighlight>

This private function calculates the center point of the shot and returns the enclosing rectangle of the shot. It uses the initial cannon force and angle in addition to '''<tt>timerCount</tt>''', which increases as time passes.

The formula used is the standard Newtonian formula for frictionless movement in a gravity field. For simplicity, we've chosen to disregard any Einsteinian effects.

We calculate the center point in a coordinate system where y coordinates increase upward. After we have calculated the center point, we construct a [http://doc.qt.nokia.com/latest/qrect.html Qt::Rect] with size 6 x 6 and move its center point to the point calculated above. In the same operation we convert the point into the widget's coordinate system (see [http://doc.qt.nokia.com/latest/coordsys.html The Coordinate System]).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]'''

The only addition is the Shoot button.

<syntaxhighlight lang="ruby">
shoot = Qt::PushButton.new(tr('&Shoot'))
shoot.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))
</syntaxhighlight>

In the constructor we create and set up the Shoot button exactly like we did with the Quit button.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), cannonField, SLOT('shoot()'))
</syntaxhighlight>

Connects the '''<tt>clicked()</tt>''' signal of the Shoot button to the '''<tt>shoot()</tt>''' slot of the '''<tt>CannonField</tt>'''.

=== Sovelluksen suorittaminen ===

The cannon can shoot, but there's nothing to shoot at.

=== Harjoitukset ===

Tee laukauksesta täytetty ympyrä. [Vihje: [http://doc.qt.nokia.com/latest/qpainter.html#drawEllipse Qt::Painter::drawEllipse()] saattaa auttaa.]

Vaihda kanuunan väriä kun laukaus on ilmassa.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/36/fi

2011-10-29T12:45:36Z

Centerlink: Created page with "Tee laukauksesta täytetty ympyrä. [Vihje: [http://doc.qt.nokia.com/latest/qpainter.html#drawEllipse Qt::Painter::drawEllipse()] saattaa auttaa.]"

Tee laukauksesta täytetty ympyrä. [Vihje: [http://doc.qt.nokia.com/latest/qpainter.html#drawEllipse Qt::Painter::drawEllipse()] saattaa auttaa.]

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/fi

2011-10-29T12:44:56Z

Centerlink: Created page with "Vaihda kanuunan väriä kun laukaus on ilmassa."

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Giving It a Shot|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_10|Oppikurssi 10 - Sileää kuin silkki]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]
}}
== Giving It a Shot ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_11.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]

=== Yleiskuva ===

In this example we introduce a timer to implement animated shooting.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has shooting capabilities.

<syntaxhighlight lang="ruby">
include Math
</syntaxhighlight>

We include '''<tt>Math</tt>''' because we need the '''<tt>sin()</tt>''' and '''<tt>cos()</tt>''' functions.

<syntaxhighlight lang="ruby">
@timerCount = 0

@autoShootTimer = Qt::Timer.new(self)
connect(@autoShootTimer, SIGNAL('timeout()'),
self, SLOT('moveShot()'))

@shootAngle = 0
@shootForce = 0
</syntaxhighlight>

We initialize our new private variables and connect the [http://doc.qt.nokia.com/latest/qtimer.html#timeout Qt::Timer::timeout()] signal to our '''<tt>moveShot()</tt>''' slot. We'll move the shot every time the timer times out.

The '''<tt>timerCount</tt>''' keeps track of the time passed since the shot was fired. The '''<tt>shootAngle</tt>''' is the cannon angle and '''<tt>shootForce</tt>''' is the cannon force when the shot was fired.

<syntaxhighlight lang="ruby">
def shoot()
if @autoShootTimer.isActive()
return
end;

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
end
</syntaxhighlight>

This function shoots a shot unless a shot is in the air. The '''<tt>timerCount</tt>''' is reset to zero. The '''<tt>shootAngle</tt>''' and '''<tt>shootForce</tt>''' variables are set to the current cannon angle and force. Finally, we start the timer.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()

if shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
else
region = region.unite(Qt::Region.new(shotR))
end
update(region)
end
</syntaxhighlight>

'''<tt>moveShot()</tt>''' is the slot that moves the shot, called every 5 milliseconds when the [http://doc.qt.nokia.com/latest/qtimer.html Qt::Timer] fires.

Its tasks are to compute the new position, update the screen with the shot in the new position, and if necessary, stop the timer.

First we make a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] that holds the old '''<tt>shotRect()</tt>'''. A [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] is capable of holding any sort of region, and we'll use it here to simplify the painting. '''<tt>shotRect()</tt>''' returns the rectangle where the shot is now. It is explained in detail later.

Then we increment the '''<tt>timerCount</tt>''', which has the effect of moving the shot one step along its trajectory.

Next we fetch the new shot rectangle.

If the shot has moved beyond the right or bottom edge of the widget we stop the timer, or we add the new '''<tt>shotRect()</tt>''' to the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region].

Finally, we repaint the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region]. This will send a single paint event for just the one or two rectangles that need updating.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

paintCannon(painter)
if @autoShootTimer.isActive()
paintShot(painter)
end

painter.end()
end
</syntaxhighlight>

The paint event function has been simplified since the previous chapter. Most of the logic has been moved to the new '''<tt>paintShot()</tt>''' and '''<tt>paintCannon()</tt>''' functions.

<syntaxhighlight lang="ruby">
def paintShot(painter)
painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::black))
painter.drawRect(shotRect())
end
</syntaxhighlight>

This private function paints the shot by drawing a black filled rectangle.

We leave out the implementation of '''<tt>paintCannon()</tt>'''; it is the same as the [http://doc.qt.nokia.com/latest/qwidget.html#paintEvent Qt::Widget::paintEvent()] reimplementation from the previous chapter.

<syntaxhighlight lang="ruby">
def shotRect()
gravity = 4.0

time = @timerCount / 20.0
velocity = @shootForce
radians = @shootAngle * 3.14159265 / 180.0

velx = velocity * cos(radians)
vely = velocity * sin(radians)
x0 = (@barrelRect.right() + 5.0) * cos(radians)
y0 = (@barrelRect.right() + 5.0) * sin(radians)
x = x0 + velx * time
y = y0 + vely * time - 0.5 * gravity * time * time

result = Qt::Rect.new(0, 0, 6, 6)
result.moveCenter(Qt::Point.new(x.round, height() - 1 - y.round))
return result
end
</syntaxhighlight>

This private function calculates the center point of the shot and returns the enclosing rectangle of the shot. It uses the initial cannon force and angle in addition to '''<tt>timerCount</tt>''', which increases as time passes.

The formula used is the standard Newtonian formula for frictionless movement in a gravity field. For simplicity, we've chosen to disregard any Einsteinian effects.

We calculate the center point in a coordinate system where y coordinates increase upward. After we have calculated the center point, we construct a [http://doc.qt.nokia.com/latest/qrect.html Qt::Rect] with size 6 x 6 and move its center point to the point calculated above. In the same operation we convert the point into the widget's coordinate system (see [http://doc.qt.nokia.com/latest/coordsys.html The Coordinate System]).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]'''

The only addition is the Shoot button.

<syntaxhighlight lang="ruby">
shoot = Qt::PushButton.new(tr('&Shoot'))
shoot.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))
</syntaxhighlight>

In the constructor we create and set up the Shoot button exactly like we did with the Quit button.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), cannonField, SLOT('shoot()'))
</syntaxhighlight>

Connects the '''<tt>clicked()</tt>''' signal of the Shoot button to the '''<tt>shoot()</tt>''' slot of the '''<tt>CannonField</tt>'''.

=== Sovelluksen suorittaminen ===

The cannon can shoot, but there's nothing to shoot at.

=== Harjoitukset ===

Make the shot a filled circle. [Hint: [http://doc.qt.nokia.com/latest/qpainter.html#drawEllipse Qt::Painter::drawEllipse()] may help.]

Vaihda kanuunan väriä kun laukaus on ilmassa.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/37/fi

2011-10-29T12:44:56Z

Centerlink: Created page with "Vaihda kanuunan väriä kun laukaus on ilmassa."

Vaihda kanuunan väriä kun laukaus on ilmassa.

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/38/fi

2011-10-29T12:44:25Z

Centerlink: Created page with "Category:Ruby"

[[Category:Ruby]]

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/fi

2011-10-29T12:44:17Z

Centerlink: Created page with "=== Harjoitukset ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Giving It a Shot|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_10|Oppikurssi 10 - Sileää kuin silkki]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]
}}
== Giving It a Shot ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_11.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]

=== Yleiskuva ===

In this example we introduce a timer to implement animated shooting.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has shooting capabilities.

<syntaxhighlight lang="ruby">
include Math
</syntaxhighlight>

We include '''<tt>Math</tt>''' because we need the '''<tt>sin()</tt>''' and '''<tt>cos()</tt>''' functions.

<syntaxhighlight lang="ruby">
@timerCount = 0

@autoShootTimer = Qt::Timer.new(self)
connect(@autoShootTimer, SIGNAL('timeout()'),
self, SLOT('moveShot()'))

@shootAngle = 0
@shootForce = 0
</syntaxhighlight>

We initialize our new private variables and connect the [http://doc.qt.nokia.com/latest/qtimer.html#timeout Qt::Timer::timeout()] signal to our '''<tt>moveShot()</tt>''' slot. We'll move the shot every time the timer times out.

The '''<tt>timerCount</tt>''' keeps track of the time passed since the shot was fired. The '''<tt>shootAngle</tt>''' is the cannon angle and '''<tt>shootForce</tt>''' is the cannon force when the shot was fired.

<syntaxhighlight lang="ruby">
def shoot()
if @autoShootTimer.isActive()
return
end;

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
end
</syntaxhighlight>

This function shoots a shot unless a shot is in the air. The '''<tt>timerCount</tt>''' is reset to zero. The '''<tt>shootAngle</tt>''' and '''<tt>shootForce</tt>''' variables are set to the current cannon angle and force. Finally, we start the timer.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()

if shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
else
region = region.unite(Qt::Region.new(shotR))
end
update(region)
end
</syntaxhighlight>

'''<tt>moveShot()</tt>''' is the slot that moves the shot, called every 5 milliseconds when the [http://doc.qt.nokia.com/latest/qtimer.html Qt::Timer] fires.

Its tasks are to compute the new position, update the screen with the shot in the new position, and if necessary, stop the timer.

First we make a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] that holds the old '''<tt>shotRect()</tt>'''. A [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] is capable of holding any sort of region, and we'll use it here to simplify the painting. '''<tt>shotRect()</tt>''' returns the rectangle where the shot is now. It is explained in detail later.

Then we increment the '''<tt>timerCount</tt>''', which has the effect of moving the shot one step along its trajectory.

Next we fetch the new shot rectangle.

If the shot has moved beyond the right or bottom edge of the widget we stop the timer, or we add the new '''<tt>shotRect()</tt>''' to the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region].

Finally, we repaint the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region]. This will send a single paint event for just the one or two rectangles that need updating.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

paintCannon(painter)
if @autoShootTimer.isActive()
paintShot(painter)
end

painter.end()
end
</syntaxhighlight>

The paint event function has been simplified since the previous chapter. Most of the logic has been moved to the new '''<tt>paintShot()</tt>''' and '''<tt>paintCannon()</tt>''' functions.

<syntaxhighlight lang="ruby">
def paintShot(painter)
painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::black))
painter.drawRect(shotRect())
end
</syntaxhighlight>

This private function paints the shot by drawing a black filled rectangle.

We leave out the implementation of '''<tt>paintCannon()</tt>'''; it is the same as the [http://doc.qt.nokia.com/latest/qwidget.html#paintEvent Qt::Widget::paintEvent()] reimplementation from the previous chapter.

<syntaxhighlight lang="ruby">
def shotRect()
gravity = 4.0

time = @timerCount / 20.0
velocity = @shootForce
radians = @shootAngle * 3.14159265 / 180.0

velx = velocity * cos(radians)
vely = velocity * sin(radians)
x0 = (@barrelRect.right() + 5.0) * cos(radians)
y0 = (@barrelRect.right() + 5.0) * sin(radians)
x = x0 + velx * time
y = y0 + vely * time - 0.5 * gravity * time * time

result = Qt::Rect.new(0, 0, 6, 6)
result.moveCenter(Qt::Point.new(x.round, height() - 1 - y.round))
return result
end
</syntaxhighlight>

This private function calculates the center point of the shot and returns the enclosing rectangle of the shot. It uses the initial cannon force and angle in addition to '''<tt>timerCount</tt>''', which increases as time passes.

The formula used is the standard Newtonian formula for frictionless movement in a gravity field. For simplicity, we've chosen to disregard any Einsteinian effects.

We calculate the center point in a coordinate system where y coordinates increase upward. After we have calculated the center point, we construct a [http://doc.qt.nokia.com/latest/qrect.html Qt::Rect] with size 6 x 6 and move its center point to the point calculated above. In the same operation we convert the point into the widget's coordinate system (see [http://doc.qt.nokia.com/latest/coordsys.html The Coordinate System]).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]'''

The only addition is the Shoot button.

<syntaxhighlight lang="ruby">
shoot = Qt::PushButton.new(tr('&Shoot'))
shoot.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))
</syntaxhighlight>

In the constructor we create and set up the Shoot button exactly like we did with the Quit button.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), cannonField, SLOT('shoot()'))
</syntaxhighlight>

Connects the '''<tt>clicked()</tt>''' signal of the Shoot button to the '''<tt>shoot()</tt>''' slot of the '''<tt>CannonField</tt>'''.

=== Sovelluksen suorittaminen ===

The cannon can shoot, but there's nothing to shoot at.

=== Harjoitukset ===

Make the shot a filled circle. [Hint: [http://doc.qt.nokia.com/latest/qpainter.html#drawEllipse Qt::Painter::drawEllipse()] may help.]

Change the color of the cannon when a shot is in the air.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/35/fi

2011-10-29T12:44:17Z

Centerlink: Created page with "=== Harjoitukset ==="

=== Harjoitukset ===

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/fi

2011-10-29T12:43:49Z

Centerlink: Created page with "=== Sovelluksen suorittaminen ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Giving It a Shot|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_10|Oppikurssi 10 - Sileää kuin silkki]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]
}}
== Giving It a Shot ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_11.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]

=== Yleiskuva ===

In this example we introduce a timer to implement animated shooting.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has shooting capabilities.

<syntaxhighlight lang="ruby">
include Math
</syntaxhighlight>

We include '''<tt>Math</tt>''' because we need the '''<tt>sin()</tt>''' and '''<tt>cos()</tt>''' functions.

<syntaxhighlight lang="ruby">
@timerCount = 0

@autoShootTimer = Qt::Timer.new(self)
connect(@autoShootTimer, SIGNAL('timeout()'),
self, SLOT('moveShot()'))

@shootAngle = 0
@shootForce = 0
</syntaxhighlight>

We initialize our new private variables and connect the [http://doc.qt.nokia.com/latest/qtimer.html#timeout Qt::Timer::timeout()] signal to our '''<tt>moveShot()</tt>''' slot. We'll move the shot every time the timer times out.

The '''<tt>timerCount</tt>''' keeps track of the time passed since the shot was fired. The '''<tt>shootAngle</tt>''' is the cannon angle and '''<tt>shootForce</tt>''' is the cannon force when the shot was fired.

<syntaxhighlight lang="ruby">
def shoot()
if @autoShootTimer.isActive()
return
end;

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
end
</syntaxhighlight>

This function shoots a shot unless a shot is in the air. The '''<tt>timerCount</tt>''' is reset to zero. The '''<tt>shootAngle</tt>''' and '''<tt>shootForce</tt>''' variables are set to the current cannon angle and force. Finally, we start the timer.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()

if shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
else
region = region.unite(Qt::Region.new(shotR))
end
update(region)
end
</syntaxhighlight>

'''<tt>moveShot()</tt>''' is the slot that moves the shot, called every 5 milliseconds when the [http://doc.qt.nokia.com/latest/qtimer.html Qt::Timer] fires.

Its tasks are to compute the new position, update the screen with the shot in the new position, and if necessary, stop the timer.

First we make a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] that holds the old '''<tt>shotRect()</tt>'''. A [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] is capable of holding any sort of region, and we'll use it here to simplify the painting. '''<tt>shotRect()</tt>''' returns the rectangle where the shot is now. It is explained in detail later.

Then we increment the '''<tt>timerCount</tt>''', which has the effect of moving the shot one step along its trajectory.

Next we fetch the new shot rectangle.

If the shot has moved beyond the right or bottom edge of the widget we stop the timer, or we add the new '''<tt>shotRect()</tt>''' to the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region].

Finally, we repaint the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region]. This will send a single paint event for just the one or two rectangles that need updating.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

paintCannon(painter)
if @autoShootTimer.isActive()
paintShot(painter)
end

painter.end()
end
</syntaxhighlight>

The paint event function has been simplified since the previous chapter. Most of the logic has been moved to the new '''<tt>paintShot()</tt>''' and '''<tt>paintCannon()</tt>''' functions.

<syntaxhighlight lang="ruby">
def paintShot(painter)
painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::black))
painter.drawRect(shotRect())
end
</syntaxhighlight>

This private function paints the shot by drawing a black filled rectangle.

We leave out the implementation of '''<tt>paintCannon()</tt>'''; it is the same as the [http://doc.qt.nokia.com/latest/qwidget.html#paintEvent Qt::Widget::paintEvent()] reimplementation from the previous chapter.

<syntaxhighlight lang="ruby">
def shotRect()
gravity = 4.0

time = @timerCount / 20.0
velocity = @shootForce
radians = @shootAngle * 3.14159265 / 180.0

velx = velocity * cos(radians)
vely = velocity * sin(radians)
x0 = (@barrelRect.right() + 5.0) * cos(radians)
y0 = (@barrelRect.right() + 5.0) * sin(radians)
x = x0 + velx * time
y = y0 + vely * time - 0.5 * gravity * time * time

result = Qt::Rect.new(0, 0, 6, 6)
result.moveCenter(Qt::Point.new(x.round, height() - 1 - y.round))
return result
end
</syntaxhighlight>

This private function calculates the center point of the shot and returns the enclosing rectangle of the shot. It uses the initial cannon force and angle in addition to '''<tt>timerCount</tt>''', which increases as time passes.

The formula used is the standard Newtonian formula for frictionless movement in a gravity field. For simplicity, we've chosen to disregard any Einsteinian effects.

We calculate the center point in a coordinate system where y coordinates increase upward. After we have calculated the center point, we construct a [http://doc.qt.nokia.com/latest/qrect.html Qt::Rect] with size 6 x 6 and move its center point to the point calculated above. In the same operation we convert the point into the widget's coordinate system (see [http://doc.qt.nokia.com/latest/coordsys.html The Coordinate System]).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]'''

The only addition is the Shoot button.

<syntaxhighlight lang="ruby">
shoot = Qt::PushButton.new(tr('&Shoot'))
shoot.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))
</syntaxhighlight>

In the constructor we create and set up the Shoot button exactly like we did with the Quit button.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), cannonField, SLOT('shoot()'))
</syntaxhighlight>

Connects the '''<tt>clicked()</tt>''' signal of the Shoot button to the '''<tt>shoot()</tt>''' slot of the '''<tt>CannonField</tt>'''.

=== Sovelluksen suorittaminen ===

The cannon can shoot, but there's nothing to shoot at.

=== Exercises ===

Make the shot a filled circle. [Hint: [http://doc.qt.nokia.com/latest/qpainter.html#drawEllipse Qt::Painter::drawEllipse()] may help.]

Change the color of the cannon when a shot is in the air.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/33/fi

2011-10-29T12:43:48Z

Centerlink: Created page with "=== Sovelluksen suorittaminen ==="

=== Sovelluksen suorittaminen ===

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/fi

2011-10-29T12:43:23Z

Centerlink: Created page with "=== Läpikäynti rivi riviltä ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Giving It a Shot|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_10|Oppikurssi 10 - Sileää kuin silkki]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]
}}
== Giving It a Shot ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_11.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]

=== Yleiskuva ===

In this example we introduce a timer to implement animated shooting.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has shooting capabilities.

<syntaxhighlight lang="ruby">
include Math
</syntaxhighlight>

We include '''<tt>Math</tt>''' because we need the '''<tt>sin()</tt>''' and '''<tt>cos()</tt>''' functions.

<syntaxhighlight lang="ruby">
@timerCount = 0

@autoShootTimer = Qt::Timer.new(self)
connect(@autoShootTimer, SIGNAL('timeout()'),
self, SLOT('moveShot()'))

@shootAngle = 0
@shootForce = 0
</syntaxhighlight>

We initialize our new private variables and connect the [http://doc.qt.nokia.com/latest/qtimer.html#timeout Qt::Timer::timeout()] signal to our '''<tt>moveShot()</tt>''' slot. We'll move the shot every time the timer times out.

The '''<tt>timerCount</tt>''' keeps track of the time passed since the shot was fired. The '''<tt>shootAngle</tt>''' is the cannon angle and '''<tt>shootForce</tt>''' is the cannon force when the shot was fired.

<syntaxhighlight lang="ruby">
def shoot()
if @autoShootTimer.isActive()
return
end;

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
end
</syntaxhighlight>

This function shoots a shot unless a shot is in the air. The '''<tt>timerCount</tt>''' is reset to zero. The '''<tt>shootAngle</tt>''' and '''<tt>shootForce</tt>''' variables are set to the current cannon angle and force. Finally, we start the timer.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()

if shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
else
region = region.unite(Qt::Region.new(shotR))
end
update(region)
end
</syntaxhighlight>

'''<tt>moveShot()</tt>''' is the slot that moves the shot, called every 5 milliseconds when the [http://doc.qt.nokia.com/latest/qtimer.html Qt::Timer] fires.

Its tasks are to compute the new position, update the screen with the shot in the new position, and if necessary, stop the timer.

First we make a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] that holds the old '''<tt>shotRect()</tt>'''. A [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] is capable of holding any sort of region, and we'll use it here to simplify the painting. '''<tt>shotRect()</tt>''' returns the rectangle where the shot is now. It is explained in detail later.

Then we increment the '''<tt>timerCount</tt>''', which has the effect of moving the shot one step along its trajectory.

Next we fetch the new shot rectangle.

If the shot has moved beyond the right or bottom edge of the widget we stop the timer, or we add the new '''<tt>shotRect()</tt>''' to the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region].

Finally, we repaint the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region]. This will send a single paint event for just the one or two rectangles that need updating.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

paintCannon(painter)
if @autoShootTimer.isActive()
paintShot(painter)
end

painter.end()
end
</syntaxhighlight>

The paint event function has been simplified since the previous chapter. Most of the logic has been moved to the new '''<tt>paintShot()</tt>''' and '''<tt>paintCannon()</tt>''' functions.

<syntaxhighlight lang="ruby">
def paintShot(painter)
painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::black))
painter.drawRect(shotRect())
end
</syntaxhighlight>

This private function paints the shot by drawing a black filled rectangle.

We leave out the implementation of '''<tt>paintCannon()</tt>'''; it is the same as the [http://doc.qt.nokia.com/latest/qwidget.html#paintEvent Qt::Widget::paintEvent()] reimplementation from the previous chapter.

<syntaxhighlight lang="ruby">
def shotRect()
gravity = 4.0

time = @timerCount / 20.0
velocity = @shootForce
radians = @shootAngle * 3.14159265 / 180.0

velx = velocity * cos(radians)
vely = velocity * sin(radians)
x0 = (@barrelRect.right() + 5.0) * cos(radians)
y0 = (@barrelRect.right() + 5.0) * sin(radians)
x = x0 + velx * time
y = y0 + vely * time - 0.5 * gravity * time * time

result = Qt::Rect.new(0, 0, 6, 6)
result.moveCenter(Qt::Point.new(x.round, height() - 1 - y.round))
return result
end
</syntaxhighlight>

This private function calculates the center point of the shot and returns the enclosing rectangle of the shot. It uses the initial cannon force and angle in addition to '''<tt>timerCount</tt>''', which increases as time passes.

The formula used is the standard Newtonian formula for frictionless movement in a gravity field. For simplicity, we've chosen to disregard any Einsteinian effects.

We calculate the center point in a coordinate system where y coordinates increase upward. After we have calculated the center point, we construct a [http://doc.qt.nokia.com/latest/qrect.html Qt::Rect] with size 6 x 6 and move its center point to the point calculated above. In the same operation we convert the point into the widget's coordinate system (see [http://doc.qt.nokia.com/latest/coordsys.html The Coordinate System]).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]'''

The only addition is the Shoot button.

<syntaxhighlight lang="ruby">
shoot = Qt::PushButton.new(tr('&Shoot'))
shoot.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))
</syntaxhighlight>

In the constructor we create and set up the Shoot button exactly like we did with the Quit button.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), cannonField, SLOT('shoot()'))
</syntaxhighlight>

Connects the '''<tt>clicked()</tt>''' signal of the Shoot button to the '''<tt>shoot()</tt>''' slot of the '''<tt>CannonField</tt>'''.

=== Running the Application ===

The cannon can shoot, but there's nothing to shoot at.

=== Exercises ===

Make the shot a filled circle. [Hint: [http://doc.qt.nokia.com/latest/qpainter.html#drawEllipse Qt::Painter::drawEllipse()] may help.]

Change the color of the cannon when a shot is in the air.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/11/fi

2011-10-29T12:43:23Z

Centerlink: Created page with "=== Läpikäynti rivi riviltä ==="

=== Läpikäynti rivi riviltä ===

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/fi

2011-10-29T12:43:02Z

Centerlink: Created page with "=== Yleiskuva ==="

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Giving It a Shot|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_10|Oppikurssi 10 - Sileää kuin silkki]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]
}}
== Giving It a Shot ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_11.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]

=== Yleiskuva ===

In this example we introduce a timer to implement animated shooting.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has shooting capabilities.

<syntaxhighlight lang="ruby">
include Math
</syntaxhighlight>

We include '''<tt>Math</tt>''' because we need the '''<tt>sin()</tt>''' and '''<tt>cos()</tt>''' functions.

<syntaxhighlight lang="ruby">
@timerCount = 0

@autoShootTimer = Qt::Timer.new(self)
connect(@autoShootTimer, SIGNAL('timeout()'),
self, SLOT('moveShot()'))

@shootAngle = 0
@shootForce = 0
</syntaxhighlight>

We initialize our new private variables and connect the [http://doc.qt.nokia.com/latest/qtimer.html#timeout Qt::Timer::timeout()] signal to our '''<tt>moveShot()</tt>''' slot. We'll move the shot every time the timer times out.

The '''<tt>timerCount</tt>''' keeps track of the time passed since the shot was fired. The '''<tt>shootAngle</tt>''' is the cannon angle and '''<tt>shootForce</tt>''' is the cannon force when the shot was fired.

<syntaxhighlight lang="ruby">
def shoot()
if @autoShootTimer.isActive()
return
end;

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
end
</syntaxhighlight>

This function shoots a shot unless a shot is in the air. The '''<tt>timerCount</tt>''' is reset to zero. The '''<tt>shootAngle</tt>''' and '''<tt>shootForce</tt>''' variables are set to the current cannon angle and force. Finally, we start the timer.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()

if shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
else
region = region.unite(Qt::Region.new(shotR))
end
update(region)
end
</syntaxhighlight>

'''<tt>moveShot()</tt>''' is the slot that moves the shot, called every 5 milliseconds when the [http://doc.qt.nokia.com/latest/qtimer.html Qt::Timer] fires.

Its tasks are to compute the new position, update the screen with the shot in the new position, and if necessary, stop the timer.

First we make a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] that holds the old '''<tt>shotRect()</tt>'''. A [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] is capable of holding any sort of region, and we'll use it here to simplify the painting. '''<tt>shotRect()</tt>''' returns the rectangle where the shot is now. It is explained in detail later.

Then we increment the '''<tt>timerCount</tt>''', which has the effect of moving the shot one step along its trajectory.

Next we fetch the new shot rectangle.

If the shot has moved beyond the right or bottom edge of the widget we stop the timer, or we add the new '''<tt>shotRect()</tt>''' to the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region].

Finally, we repaint the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region]. This will send a single paint event for just the one or two rectangles that need updating.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

paintCannon(painter)
if @autoShootTimer.isActive()
paintShot(painter)
end

painter.end()
end
</syntaxhighlight>

The paint event function has been simplified since the previous chapter. Most of the logic has been moved to the new '''<tt>paintShot()</tt>''' and '''<tt>paintCannon()</tt>''' functions.

<syntaxhighlight lang="ruby">
def paintShot(painter)
painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::black))
painter.drawRect(shotRect())
end
</syntaxhighlight>

This private function paints the shot by drawing a black filled rectangle.

We leave out the implementation of '''<tt>paintCannon()</tt>'''; it is the same as the [http://doc.qt.nokia.com/latest/qwidget.html#paintEvent Qt::Widget::paintEvent()] reimplementation from the previous chapter.

<syntaxhighlight lang="ruby">
def shotRect()
gravity = 4.0

time = @timerCount / 20.0
velocity = @shootForce
radians = @shootAngle * 3.14159265 / 180.0

velx = velocity * cos(radians)
vely = velocity * sin(radians)
x0 = (@barrelRect.right() + 5.0) * cos(radians)
y0 = (@barrelRect.right() + 5.0) * sin(radians)
x = x0 + velx * time
y = y0 + vely * time - 0.5 * gravity * time * time

result = Qt::Rect.new(0, 0, 6, 6)
result.moveCenter(Qt::Point.new(x.round, height() - 1 - y.round))
return result
end
</syntaxhighlight>

This private function calculates the center point of the shot and returns the enclosing rectangle of the shot. It uses the initial cannon force and angle in addition to '''<tt>timerCount</tt>''', which increases as time passes.

The formula used is the standard Newtonian formula for frictionless movement in a gravity field. For simplicity, we've chosen to disregard any Einsteinian effects.

We calculate the center point in a coordinate system where y coordinates increase upward. After we have calculated the center point, we construct a [http://doc.qt.nokia.com/latest/qrect.html Qt::Rect] with size 6 x 6 and move its center point to the point calculated above. In the same operation we convert the point into the widget's coordinate system (see [http://doc.qt.nokia.com/latest/coordsys.html The Coordinate System]).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]'''

The only addition is the Shoot button.

<syntaxhighlight lang="ruby">
shoot = Qt::PushButton.new(tr('&Shoot'))
shoot.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))
</syntaxhighlight>

In the constructor we create and set up the Shoot button exactly like we did with the Quit button.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), cannonField, SLOT('shoot()'))
</syntaxhighlight>

Connects the '''<tt>clicked()</tt>''' signal of the Shoot button to the '''<tt>shoot()</tt>''' slot of the '''<tt>CannonField</tt>'''.

=== Running the Application ===

The cannon can shoot, but there's nothing to shoot at.

=== Exercises ===

Make the shot a filled circle. [Hint: [http://doc.qt.nokia.com/latest/qpainter.html#drawEllipse Qt::Painter::drawEllipse()] may help.]

Change the color of the cannon when a shot is in the air.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/9/fi

2011-10-29T12:43:01Z

Centerlink: Created page with "=== Yleiskuva ==="

=== Yleiskuva ===

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/7/fi

2011-10-29T12:42:22Z

Centerlink: Created page with "center"

[[Image:Qt4_Ruby_Tutorial_Screenshot_11.png|center]]

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/fi

2011-10-29T12:42:15Z

Centerlink: Created page with "Oppikurssi 10 - Sileää kuin silkki"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Giving It a Shot|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_10|Oppikurssi 10 - Sileää kuin silkki]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]
}}
== Giving It a Shot ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_11.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]

=== Overview ===

In this example we introduce a timer to implement animated shooting.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has shooting capabilities.

<syntaxhighlight lang="ruby">
include Math
</syntaxhighlight>

We include '''<tt>Math</tt>''' because we need the '''<tt>sin()</tt>''' and '''<tt>cos()</tt>''' functions.

<syntaxhighlight lang="ruby">
@timerCount = 0

@autoShootTimer = Qt::Timer.new(self)
connect(@autoShootTimer, SIGNAL('timeout()'),
self, SLOT('moveShot()'))

@shootAngle = 0
@shootForce = 0
</syntaxhighlight>

We initialize our new private variables and connect the [http://doc.qt.nokia.com/latest/qtimer.html#timeout Qt::Timer::timeout()] signal to our '''<tt>moveShot()</tt>''' slot. We'll move the shot every time the timer times out.

The '''<tt>timerCount</tt>''' keeps track of the time passed since the shot was fired. The '''<tt>shootAngle</tt>''' is the cannon angle and '''<tt>shootForce</tt>''' is the cannon force when the shot was fired.

<syntaxhighlight lang="ruby">
def shoot()
if @autoShootTimer.isActive()
return
end;

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
end
</syntaxhighlight>

This function shoots a shot unless a shot is in the air. The '''<tt>timerCount</tt>''' is reset to zero. The '''<tt>shootAngle</tt>''' and '''<tt>shootForce</tt>''' variables are set to the current cannon angle and force. Finally, we start the timer.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()

if shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
else
region = region.unite(Qt::Region.new(shotR))
end
update(region)
end
</syntaxhighlight>

'''<tt>moveShot()</tt>''' is the slot that moves the shot, called every 5 milliseconds when the [http://doc.qt.nokia.com/latest/qtimer.html Qt::Timer] fires.

Its tasks are to compute the new position, update the screen with the shot in the new position, and if necessary, stop the timer.

First we make a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] that holds the old '''<tt>shotRect()</tt>'''. A [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] is capable of holding any sort of region, and we'll use it here to simplify the painting. '''<tt>shotRect()</tt>''' returns the rectangle where the shot is now. It is explained in detail later.

Then we increment the '''<tt>timerCount</tt>''', which has the effect of moving the shot one step along its trajectory.

Next we fetch the new shot rectangle.

If the shot has moved beyond the right or bottom edge of the widget we stop the timer, or we add the new '''<tt>shotRect()</tt>''' to the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region].

Finally, we repaint the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region]. This will send a single paint event for just the one or two rectangles that need updating.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

paintCannon(painter)
if @autoShootTimer.isActive()
paintShot(painter)
end

painter.end()
end
</syntaxhighlight>

The paint event function has been simplified since the previous chapter. Most of the logic has been moved to the new '''<tt>paintShot()</tt>''' and '''<tt>paintCannon()</tt>''' functions.

<syntaxhighlight lang="ruby">
def paintShot(painter)
painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::black))
painter.drawRect(shotRect())
end
</syntaxhighlight>

This private function paints the shot by drawing a black filled rectangle.

We leave out the implementation of '''<tt>paintCannon()</tt>'''; it is the same as the [http://doc.qt.nokia.com/latest/qwidget.html#paintEvent Qt::Widget::paintEvent()] reimplementation from the previous chapter.

<syntaxhighlight lang="ruby">
def shotRect()
gravity = 4.0

time = @timerCount / 20.0
velocity = @shootForce
radians = @shootAngle * 3.14159265 / 180.0

velx = velocity * cos(radians)
vely = velocity * sin(radians)
x0 = (@barrelRect.right() + 5.0) * cos(radians)
y0 = (@barrelRect.right() + 5.0) * sin(radians)
x = x0 + velx * time
y = y0 + vely * time - 0.5 * gravity * time * time

result = Qt::Rect.new(0, 0, 6, 6)
result.moveCenter(Qt::Point.new(x.round, height() - 1 - y.round))
return result
end
</syntaxhighlight>

This private function calculates the center point of the shot and returns the enclosing rectangle of the shot. It uses the initial cannon force and angle in addition to '''<tt>timerCount</tt>''', which increases as time passes.

The formula used is the standard Newtonian formula for frictionless movement in a gravity field. For simplicity, we've chosen to disregard any Einsteinian effects.

We calculate the center point in a coordinate system where y coordinates increase upward. After we have calculated the center point, we construct a [http://doc.qt.nokia.com/latest/qrect.html Qt::Rect] with size 6 x 6 and move its center point to the point calculated above. In the same operation we convert the point into the widget's coordinate system (see [http://doc.qt.nokia.com/latest/coordsys.html The Coordinate System]).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]'''

The only addition is the Shoot button.

<syntaxhighlight lang="ruby">
shoot = Qt::PushButton.new(tr('&Shoot'))
shoot.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))
</syntaxhighlight>

In the constructor we create and set up the Shoot button exactly like we did with the Quit button.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), cannonField, SLOT('shoot()'))
</syntaxhighlight>

Connects the '''<tt>clicked()</tt>''' signal of the Shoot button to the '''<tt>shoot()</tt>''' slot of the '''<tt>CannonField</tt>'''.

=== Running the Application ===

The cannon can shoot, but there's nothing to shoot at.

=== Exercises ===

Make the shot a filled circle. [Hint: [http://doc.qt.nokia.com/latest/qpainter.html#drawEllipse Qt::Painter::drawEllipse()] may help.]

Change the color of the cannon when a shot is in the air.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/4/fi

2011-10-29T12:42:15Z

Centerlink: Created page with "Oppikurssi 10 - Sileää kuin silkki"

Oppikurssi 10 - Sileää kuin silkki

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/fi

2011-10-29T12:41:47Z

Centerlink: Created page with "Qt4 Ruby -oppikurssi"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Giving It a Shot|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_10|Tutorial 10 - Smooth as Silk]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]
}}
== Giving It a Shot ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_11.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]

=== Overview ===

In this example we introduce a timer to implement animated shooting.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has shooting capabilities.

<syntaxhighlight lang="ruby">
include Math
</syntaxhighlight>

We include '''<tt>Math</tt>''' because we need the '''<tt>sin()</tt>''' and '''<tt>cos()</tt>''' functions.

<syntaxhighlight lang="ruby">
@timerCount = 0

@autoShootTimer = Qt::Timer.new(self)
connect(@autoShootTimer, SIGNAL('timeout()'),
self, SLOT('moveShot()'))

@shootAngle = 0
@shootForce = 0
</syntaxhighlight>

We initialize our new private variables and connect the [http://doc.qt.nokia.com/latest/qtimer.html#timeout Qt::Timer::timeout()] signal to our '''<tt>moveShot()</tt>''' slot. We'll move the shot every time the timer times out.

The '''<tt>timerCount</tt>''' keeps track of the time passed since the shot was fired. The '''<tt>shootAngle</tt>''' is the cannon angle and '''<tt>shootForce</tt>''' is the cannon force when the shot was fired.

<syntaxhighlight lang="ruby">
def shoot()
if @autoShootTimer.isActive()
return
end;

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
end
</syntaxhighlight>

This function shoots a shot unless a shot is in the air. The '''<tt>timerCount</tt>''' is reset to zero. The '''<tt>shootAngle</tt>''' and '''<tt>shootForce</tt>''' variables are set to the current cannon angle and force. Finally, we start the timer.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()

if shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
else
region = region.unite(Qt::Region.new(shotR))
end
update(region)
end
</syntaxhighlight>

'''<tt>moveShot()</tt>''' is the slot that moves the shot, called every 5 milliseconds when the [http://doc.qt.nokia.com/latest/qtimer.html Qt::Timer] fires.

Its tasks are to compute the new position, update the screen with the shot in the new position, and if necessary, stop the timer.

First we make a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] that holds the old '''<tt>shotRect()</tt>'''. A [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] is capable of holding any sort of region, and we'll use it here to simplify the painting. '''<tt>shotRect()</tt>''' returns the rectangle where the shot is now. It is explained in detail later.

Then we increment the '''<tt>timerCount</tt>''', which has the effect of moving the shot one step along its trajectory.

Next we fetch the new shot rectangle.

If the shot has moved beyond the right or bottom edge of the widget we stop the timer, or we add the new '''<tt>shotRect()</tt>''' to the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region].

Finally, we repaint the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region]. This will send a single paint event for just the one or two rectangles that need updating.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

paintCannon(painter)
if @autoShootTimer.isActive()
paintShot(painter)
end

painter.end()
end
</syntaxhighlight>

The paint event function has been simplified since the previous chapter. Most of the logic has been moved to the new '''<tt>paintShot()</tt>''' and '''<tt>paintCannon()</tt>''' functions.

<syntaxhighlight lang="ruby">
def paintShot(painter)
painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::black))
painter.drawRect(shotRect())
end
</syntaxhighlight>

This private function paints the shot by drawing a black filled rectangle.

We leave out the implementation of '''<tt>paintCannon()</tt>'''; it is the same as the [http://doc.qt.nokia.com/latest/qwidget.html#paintEvent Qt::Widget::paintEvent()] reimplementation from the previous chapter.

<syntaxhighlight lang="ruby">
def shotRect()
gravity = 4.0

time = @timerCount / 20.0
velocity = @shootForce
radians = @shootAngle * 3.14159265 / 180.0

velx = velocity * cos(radians)
vely = velocity * sin(radians)
x0 = (@barrelRect.right() + 5.0) * cos(radians)
y0 = (@barrelRect.right() + 5.0) * sin(radians)
x = x0 + velx * time
y = y0 + vely * time - 0.5 * gravity * time * time

result = Qt::Rect.new(0, 0, 6, 6)
result.moveCenter(Qt::Point.new(x.round, height() - 1 - y.round))
return result
end
</syntaxhighlight>

This private function calculates the center point of the shot and returns the enclosing rectangle of the shot. It uses the initial cannon force and angle in addition to '''<tt>timerCount</tt>''', which increases as time passes.

The formula used is the standard Newtonian formula for frictionless movement in a gravity field. For simplicity, we've chosen to disregard any Einsteinian effects.

We calculate the center point in a coordinate system where y coordinates increase upward. After we have calculated the center point, we construct a [http://doc.qt.nokia.com/latest/qrect.html Qt::Rect] with size 6 x 6 and move its center point to the point calculated above. In the same operation we convert the point into the widget's coordinate system (see [http://doc.qt.nokia.com/latest/coordsys.html The Coordinate System]).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]'''

The only addition is the Shoot button.

<syntaxhighlight lang="ruby">
shoot = Qt::PushButton.new(tr('&Shoot'))
shoot.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))
</syntaxhighlight>

In the constructor we create and set up the Shoot button exactly like we did with the Quit button.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), cannonField, SLOT('shoot()'))
</syntaxhighlight>

Connects the '''<tt>clicked()</tt>''' signal of the Shoot button to the '''<tt>shoot()</tt>''' slot of the '''<tt>CannonField</tt>'''.

=== Running the Application ===

The cannon can shoot, but there's nothing to shoot at.

=== Exercises ===

Make the shot a filled circle. [Hint: [http://doc.qt.nokia.com/latest/qpainter.html#drawEllipse Qt::Painter::drawEllipse()] may help.]

Change the color of the cannon when a shot is in the air.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/2/fi

2011-10-29T12:41:47Z

Centerlink: Created page with "Qt4 Ruby -oppikurssi"

Qt4 Ruby -oppikurssi

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/1/fi

2011-10-29T12:41:30Z

Centerlink: Created page with "TutorialBrowser"

TutorialBrowser

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11/fi

2011-10-29T12:41:30Z

Centerlink: Created page with "TutorialBrowser"

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 11}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby Tutorial]]|
name=Giving It a Shot|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_10|Tutorial 10 - Smooth as Silk]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_12|Tutorial 12 - Hanging in the Air the Way Bricks Don't]]
}}
== Giving It a Shot ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_11.png|center]]
Files:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]

=== Overview ===

In this example we introduce a timer to implement animated shooting.

=== Line by Line Walkthrough ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/cannon.rb cannon.rb]'''

The '''<tt>CannonField</tt>''' now has shooting capabilities.

<syntaxhighlight lang="ruby">
include Math
</syntaxhighlight>

We include '''<tt>Math</tt>''' because we need the '''<tt>sin()</tt>''' and '''<tt>cos()</tt>''' functions.

<syntaxhighlight lang="ruby">
@timerCount = 0

@autoShootTimer = Qt::Timer.new(self)
connect(@autoShootTimer, SIGNAL('timeout()'),
self, SLOT('moveShot()'))

@shootAngle = 0
@shootForce = 0
</syntaxhighlight>

We initialize our new private variables and connect the [http://doc.qt.nokia.com/latest/qtimer.html#timeout Qt::Timer::timeout()] signal to our '''<tt>moveShot()</tt>''' slot. We'll move the shot every time the timer times out.

The '''<tt>timerCount</tt>''' keeps track of the time passed since the shot was fired. The '''<tt>shootAngle</tt>''' is the cannon angle and '''<tt>shootForce</tt>''' is the cannon force when the shot was fired.

<syntaxhighlight lang="ruby">
def shoot()
if @autoShootTimer.isActive()
return
end;

@timerCount = 0
@shootAngle = @currentAngle
@shootForce = @currentForce
@autoShootTimer.start(5)
end
</syntaxhighlight>

This function shoots a shot unless a shot is in the air. The '''<tt>timerCount</tt>''' is reset to zero. The '''<tt>shootAngle</tt>''' and '''<tt>shootForce</tt>''' variables are set to the current cannon angle and force. Finally, we start the timer.

<syntaxhighlight lang="ruby">
def moveShot()
region = Qt::Region.new(shotRect())
@timerCount += 1

shotR = shotRect()

if shotR.x() > width() || shotR.y() > height()
@autoShootTimer.stop()
else
region = region.unite(Qt::Region.new(shotR))
end
update(region)
end
</syntaxhighlight>

'''<tt>moveShot()</tt>''' is the slot that moves the shot, called every 5 milliseconds when the [http://doc.qt.nokia.com/latest/qtimer.html Qt::Timer] fires.

Its tasks are to compute the new position, update the screen with the shot in the new position, and if necessary, stop the timer.

First we make a [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] that holds the old '''<tt>shotRect()</tt>'''. A [http://doc.qt.nokia.com/latest/qregion.html Qt::Region] is capable of holding any sort of region, and we'll use it here to simplify the painting. '''<tt>shotRect()</tt>''' returns the rectangle where the shot is now. It is explained in detail later.

Then we increment the '''<tt>timerCount</tt>''', which has the effect of moving the shot one step along its trajectory.

Next we fetch the new shot rectangle.

If the shot has moved beyond the right or bottom edge of the widget we stop the timer, or we add the new '''<tt>shotRect()</tt>''' to the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region].

Finally, we repaint the [http://doc.qt.nokia.com/latest/qregion.html Qt::Region]. This will send a single paint event for just the one or two rectangles that need updating.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

paintCannon(painter)
if @autoShootTimer.isActive()
paintShot(painter)
end

painter.end()
end
</syntaxhighlight>

The paint event function has been simplified since the previous chapter. Most of the logic has been moved to the new '''<tt>paintShot()</tt>''' and '''<tt>paintCannon()</tt>''' functions.

<syntaxhighlight lang="ruby">
def paintShot(painter)
painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::black))
painter.drawRect(shotRect())
end
</syntaxhighlight>

This private function paints the shot by drawing a black filled rectangle.

We leave out the implementation of '''<tt>paintCannon()</tt>'''; it is the same as the [http://doc.qt.nokia.com/latest/qwidget.html#paintEvent Qt::Widget::paintEvent()] reimplementation from the previous chapter.

<syntaxhighlight lang="ruby">
def shotRect()
gravity = 4.0

time = @timerCount / 20.0
velocity = @shootForce
radians = @shootAngle * 3.14159265 / 180.0

velx = velocity * cos(radians)
vely = velocity * sin(radians)
x0 = (@barrelRect.right() + 5.0) * cos(radians)
y0 = (@barrelRect.right() + 5.0) * sin(radians)
x = x0 + velx * time
y = y0 + vely * time - 0.5 * gravity * time * time

result = Qt::Rect.new(0, 0, 6, 6)
result.moveCenter(Qt::Point.new(x.round, height() - 1 - y.round))
return result
end
</syntaxhighlight>

This private function calculates the center point of the shot and returns the enclosing rectangle of the shot. It uses the initial cannon force and angle in addition to '''<tt>timerCount</tt>''', which increases as time passes.

The formula used is the standard Newtonian formula for frictionless movement in a gravity field. For simplicity, we've chosen to disregard any Einsteinian effects.

We calculate the center point in a coordinate system where y coordinates increase upward. After we have calculated the center point, we construct a [http://doc.qt.nokia.com/latest/qrect.html Qt::Rect] with size 6 x 6 and move its center point to the point calculated above. In the same operation we convert the point into the widget's coordinate system (see [http://doc.qt.nokia.com/latest/coordsys.html The Coordinate System]).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t11/t11.rb t11.rb]'''

The only addition is the Shoot button.

<syntaxhighlight lang="ruby">
shoot = Qt::PushButton.new(tr('&Shoot'))
shoot.setFont(Qt::Font.new('Times', 18, Qt::Font::Bold))
</syntaxhighlight>

In the constructor we create and set up the Shoot button exactly like we did with the Quit button.

<syntaxhighlight lang="ruby">
connect(shoot, SIGNAL('clicked()'), cannonField, SLOT('shoot()'))
</syntaxhighlight>

Connects the '''<tt>clicked()</tt>''' signal of the Shoot button to the '''<tt>shoot()</tt>''' slot of the '''<tt>CannonField</tt>'''.

=== Running the Application ===

The cannon can shoot, but there's nothing to shoot at.

=== Exercises ===

Make the shot a filled circle. [Hint: [http://doc.qt.nokia.com/latest/qpainter.html#drawEllipse Qt::Painter::drawEllipse()] may help.]

Change the color of the cannon when a shot is in the air.

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10/30/fi

2011-10-29T12:35:25Z

Centerlink: Created page with "Category:Ruby"

[[Category:Ruby]]

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10/fi

2011-10-29T12:35:17Z

Centerlink: Created page with "Yritä lisätä parempi näppäimistörajapinta. Esimerkiksi, tee + ja - kasvattamaan ja pienennättämään voimaa ja laukaisemaan kanuunan. Jos olet vaivautunut tavasta, jolla ..."

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Sileää kuin silkki|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_09|Oppikurssi 9 - Kanuunalla onnistuu]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_11|Oppikurssi 11 - Annetaan sille laukaus]]
}}
== Sileää kuin silkki ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_10.png|center]]
Tiedostot:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/t10.rb t10.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/cannon.rb cannon.rb]

=== Yleiskuva ===

Tässä esimerkissä lisäämme voimaa ohjaimeen.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/cannon.rb cannon.rb]'''

Kentällä '''<tt>CannonField</tt>''' on nyt voima-arvo kulman lisäksi.

<syntaxhighlight lang="ruby">
signals 'angleChanged(int)', 'forceChanged(int)'
slots 'setAngle(int)', 'setForce(int)'
</syntaxhighlight>

Voiman rajapinta noudattaa samaa käytäntöä kuin kulma.

<syntaxhighlight lang="ruby">
def initialize(parent = nil)
super()

@currentAngle = 45
@currentForce = 0

setPalette(Qt::Palette.new(Qt::Color.new(250, 250, 200)))
setAutoFillBackground(true)
end
</syntaxhighlight>

Voima '''<tt>@currentForce</tt>''' on alustettu nollaksi.

<syntaxhighlight lang="ruby">
def setAngle(angle)
if angle < 5
angle = 5
elsif angle > 70
angle = 70
end

if @currentAngle == angle
return
end

@currentAngle = angle
update(cannonRect())
emit angleChanged(@currentAngle)
end
</syntaxhighlight>

Teimme pienen muutoksen '''<tt>setAngle()</tt>'''-funktioon. Se piirtää uudelleen käyttöliittymän osan, joka sisältää kanuunan.

<syntaxhighlight lang="ruby">
def setForce(force)
if force < 0
force = 0
end
if @currentForce == force
return
end

@currentForce = force
emit forceChanged(@currentForce)
end
</syntaxhighlight>

'''<tt>setForce()</tt>'''-toteutus on aika samanlainen kuin '''<tt>setAngle()</tt>'''. Ainoa erilaisuus on, että koska emme näytä voima-arvoa, käyttöliittymäkomponenttia ei tarvitse piirtää uudelleen.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::blue))

painter.translate(0, height())
painter.drawPie(Qt::Rect.new(-35, -35, 70, 70), 0, 90 * 16)
painter.rotate(-@currentAngle)
painter.drawRect(Qt::Rect.new(30, -5, 20, 10))
painter.end()
end
</syntaxhighlight>

Piirrämme kuin kappaleessa 9.

<syntaxhighlight lang="ruby">
def cannonRect()
result = Qt::Rect.new(0, 0, 50, 50)
result.moveBottomLeft(rect().bottomLeft())
return result
end
</syntaxhighlight>

Funktio '''<tt>cannonRect()</tt>''' palauttaa nelikulmion, joka sisältää kanuunan sisältävän käyttöliittymäkomponentin. Luomme aluksi nelikulmion, jonka koko on 50 x 50 ja siirrämme sen niin, että sen vasen alakulma on sama kuin käyttöliittymäkomponentin vasen alakulma.

Funktio [http://doc.qt.nokia.com/latest/qwidget.html#rect-prop Qt::Widget::rect()] palauttaa käyttöliittymän sisältämän nelikulmion käyttöliittymän omina koordinaatteina. Nelikulmion vasen yläkulma on aina (0, 0).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/t10.rb t10.rb]'''

Konstruktori on enimmäkseen sama, mutta joitakin uusia bittejä on lisätty.

<syntaxhighlight lang="ruby">
force = LCDRange.new()
force.setRange(10, 50)
</syntaxhighlight>

Lisäämme toisen '''<tt>LCDRange</tt>'''-komponentin, jota käytetään voiman asettamiseen.

<syntaxhighlight lang="ruby">
connect(force, SIGNAL('valueChanged(int)'),
cannonField, SLOT('setForce(int)'))
connect(cannonField, SIGNAL('forceChanged(int)'),
force, SLOT('setValue(int)'))
</syntaxhighlight>

Yhdistämme käyttöliittymäkomponentin '''<tt>force</tt>''' ja käyttöliittymäkomponentin '''<tt>cannonField</tt>''', aivan kuin teimme käyttöliittymäkomponentille '''<tt>angle</tt>'''.

<syntaxhighlight lang="ruby">
leftLayout = Qt::VBoxLayout.new()
leftLayout.addWidget(angle)
leftLayout.addWidget(force)

gridLayout = Qt::GridLayout.new()
gridLayout.addWidget(quit, 0, 0)
gridLayout.addLayout(leftLayout, 1, 0)
gridLayout.addWidget(cannonField, 1, 1, 2, 1)
gridLayout.setColumnStretch(1, 10)
</syntaxhighlight>

Kappaleessa 9 sijoitamme '''<tt>angle</tt>'''-komponentin asettelun vasemman alakulman soluun. Nyt haluamme siihen soluun kaksi käyttöliittymäkomponenttial, joten teemme pystysuoran ruudun, laitamme pystysuoran ruudun rasterinsoluunl, ja laitamme sekä '''<tt>angle</tt>''' että '''<tt>range</tt>''' pystysuoraan ruutuun.

<syntaxhighlight lang="ruby">
force.setValue(25)
</syntaxhighlight>

Alustamme voima-arvoksi 25.

=== Sovelluksen suorittaminen ===

Meillä on nyt voimaohjaus.

=== Harjoitukset ===
Tee kanuuna piipun koko riippuvaiseksi voimasta.

Laita kanuuna oikeaan alakulmaan.

Yritä lisätä parempi näppäimistörajapinta. Esimerkiksi, tee + ja - kasvattamaan ja pienennättämään voimaa ja laukaisemaan kanuunan. Jos olet vaivautunut tavasta, jolla näppäimet '''<tt>Left</tt>''' ja '''<tt>Right</tt>''' toimivat, muuta sitä myös. [Vihje: Toteuta uudelleen [http://doc.qt.nokia.com/latest/qwidget.html#keyPressEvent Qt::Widget::keyPressEvent()].]

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10/29/fi

2011-10-29T12:35:17Z

Yritä lisätä parempi näppäimistörajapinta. Esimerkiksi, tee + ja - kasvattamaan ja pienennättämään voimaa ja laukaisemaan kanuunan. Jos olet vaivautunut tavasta, jolla näppäimet '''<tt>Left</tt>''' ja '''<tt>Right</tt>''' toimivat, muuta sitä myös. [Vihje: Toteuta uudelleen [http://doc.qt.nokia.com/latest/qwidget.html#keyPressEvent Qt::Widget::keyPressEvent()].]

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10/fi

2011-10-29T12:32:01Z

Centerlink: Created page with "Laita kanuuna oikeaan alakulmaan."

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Sileää kuin silkki|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_09|Oppikurssi 9 - Kanuunalla onnistuu]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_11|Oppikurssi 11 - Annetaan sille laukaus]]
}}
== Sileää kuin silkki ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_10.png|center]]
Tiedostot:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/t10.rb t10.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/cannon.rb cannon.rb]

=== Yleiskuva ===

Tässä esimerkissä lisäämme voimaa ohjaimeen.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/cannon.rb cannon.rb]'''

Kentällä '''<tt>CannonField</tt>''' on nyt voima-arvo kulman lisäksi.

<syntaxhighlight lang="ruby">
signals 'angleChanged(int)', 'forceChanged(int)'
slots 'setAngle(int)', 'setForce(int)'
</syntaxhighlight>

Voiman rajapinta noudattaa samaa käytäntöä kuin kulma.

<syntaxhighlight lang="ruby">
def initialize(parent = nil)
super()

@currentAngle = 45
@currentForce = 0

setPalette(Qt::Palette.new(Qt::Color.new(250, 250, 200)))
setAutoFillBackground(true)
end
</syntaxhighlight>

Voima '''<tt>@currentForce</tt>''' on alustettu nollaksi.

<syntaxhighlight lang="ruby">
def setAngle(angle)
if angle < 5
angle = 5
elsif angle > 70
angle = 70
end

if @currentAngle == angle
return
end

@currentAngle = angle
update(cannonRect())
emit angleChanged(@currentAngle)
end
</syntaxhighlight>

Teimme pienen muutoksen '''<tt>setAngle()</tt>'''-funktioon. Se piirtää uudelleen käyttöliittymän osan, joka sisältää kanuunan.

<syntaxhighlight lang="ruby">
def setForce(force)
if force < 0
force = 0
end
if @currentForce == force
return
end

@currentForce = force
emit forceChanged(@currentForce)
end
</syntaxhighlight>

'''<tt>setForce()</tt>'''-toteutus on aika samanlainen kuin '''<tt>setAngle()</tt>'''. Ainoa erilaisuus on, että koska emme näytä voima-arvoa, käyttöliittymäkomponenttia ei tarvitse piirtää uudelleen.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::blue))

painter.translate(0, height())
painter.drawPie(Qt::Rect.new(-35, -35, 70, 70), 0, 90 * 16)
painter.rotate(-@currentAngle)
painter.drawRect(Qt::Rect.new(30, -5, 20, 10))
painter.end()
end
</syntaxhighlight>

Piirrämme kuin kappaleessa 9.

<syntaxhighlight lang="ruby">
def cannonRect()
result = Qt::Rect.new(0, 0, 50, 50)
result.moveBottomLeft(rect().bottomLeft())
return result
end
</syntaxhighlight>

Funktio '''<tt>cannonRect()</tt>''' palauttaa nelikulmion, joka sisältää kanuunan sisältävän käyttöliittymäkomponentin. Luomme aluksi nelikulmion, jonka koko on 50 x 50 ja siirrämme sen niin, että sen vasen alakulma on sama kuin käyttöliittymäkomponentin vasen alakulma.

Funktio [http://doc.qt.nokia.com/latest/qwidget.html#rect-prop Qt::Widget::rect()] palauttaa käyttöliittymän sisältämän nelikulmion käyttöliittymän omina koordinaatteina. Nelikulmion vasen yläkulma on aina (0, 0).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/t10.rb t10.rb]'''

Konstruktori on enimmäkseen sama, mutta joitakin uusia bittejä on lisätty.

<syntaxhighlight lang="ruby">
force = LCDRange.new()
force.setRange(10, 50)
</syntaxhighlight>

Lisäämme toisen '''<tt>LCDRange</tt>'''-komponentin, jota käytetään voiman asettamiseen.

<syntaxhighlight lang="ruby">
connect(force, SIGNAL('valueChanged(int)'),
cannonField, SLOT('setForce(int)'))
connect(cannonField, SIGNAL('forceChanged(int)'),
force, SLOT('setValue(int)'))
</syntaxhighlight>

Yhdistämme käyttöliittymäkomponentin '''<tt>force</tt>''' ja käyttöliittymäkomponentin '''<tt>cannonField</tt>''', aivan kuin teimme käyttöliittymäkomponentille '''<tt>angle</tt>'''.

<syntaxhighlight lang="ruby">
leftLayout = Qt::VBoxLayout.new()
leftLayout.addWidget(angle)
leftLayout.addWidget(force)

gridLayout = Qt::GridLayout.new()
gridLayout.addWidget(quit, 0, 0)
gridLayout.addLayout(leftLayout, 1, 0)
gridLayout.addWidget(cannonField, 1, 1, 2, 1)
gridLayout.setColumnStretch(1, 10)
</syntaxhighlight>

Kappaleessa 9 sijoitamme '''<tt>angle</tt>'''-komponentin asettelun vasemman alakulman soluun. Nyt haluamme siihen soluun kaksi käyttöliittymäkomponenttial, joten teemme pystysuoran ruudun, laitamme pystysuoran ruudun rasterinsoluunl, ja laitamme sekä '''<tt>angle</tt>''' että '''<tt>range</tt>''' pystysuoraan ruutuun.

<syntaxhighlight lang="ruby">
force.setValue(25)
</syntaxhighlight>

Alustamme voima-arvoksi 25.

=== Sovelluksen suorittaminen ===

Meillä on nyt voimaohjaus.

=== Harjoitukset ===
Tee kanuuna piipun koko riippuvaiseksi voimasta.

Laita kanuuna oikeaan alakulmaan.

Try adding a better keyboard interface. For example, make + and - increase and decrease the force and enter shoot. If you're bothered by the way the '''<tt>Left</tt>''' and '''<tt>Right</tt>''' keys work, change that too. [Hint: Reimplement [http://doc.qt.nokia.com/latest/qwidget.html#keyPressEvent Qt::Widget::keyPressEvent()].]

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10/28/fi

2011-10-29T12:32:01Z

Centerlink: Created page with "Laita kanuuna oikeaan alakulmaan."

Laita kanuuna oikeaan alakulmaan.

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10/fi

2011-10-29T12:31:17Z

Centerlink: Created page with "=== Harjoitukset === Tee kanuuna piipun koko riippuvaiseksi voimasta."

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Sileää kuin silkki|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_09|Oppikurssi 9 - Kanuunalla onnistuu]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_11|Oppikurssi 11 - Annetaan sille laukaus]]
}}
== Sileää kuin silkki ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_10.png|center]]
Tiedostot:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/t10.rb t10.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/cannon.rb cannon.rb]

=== Yleiskuva ===

Tässä esimerkissä lisäämme voimaa ohjaimeen.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/cannon.rb cannon.rb]'''

Kentällä '''<tt>CannonField</tt>''' on nyt voima-arvo kulman lisäksi.

<syntaxhighlight lang="ruby">
signals 'angleChanged(int)', 'forceChanged(int)'
slots 'setAngle(int)', 'setForce(int)'
</syntaxhighlight>

Voiman rajapinta noudattaa samaa käytäntöä kuin kulma.

<syntaxhighlight lang="ruby">
def initialize(parent = nil)
super()

@currentAngle = 45
@currentForce = 0

setPalette(Qt::Palette.new(Qt::Color.new(250, 250, 200)))
setAutoFillBackground(true)
end
</syntaxhighlight>

Voima '''<tt>@currentForce</tt>''' on alustettu nollaksi.

<syntaxhighlight lang="ruby">
def setAngle(angle)
if angle < 5
angle = 5
elsif angle > 70
angle = 70
end

if @currentAngle == angle
return
end

@currentAngle = angle
update(cannonRect())
emit angleChanged(@currentAngle)
end
</syntaxhighlight>

Teimme pienen muutoksen '''<tt>setAngle()</tt>'''-funktioon. Se piirtää uudelleen käyttöliittymän osan, joka sisältää kanuunan.

<syntaxhighlight lang="ruby">
def setForce(force)
if force < 0
force = 0
end
if @currentForce == force
return
end

@currentForce = force
emit forceChanged(@currentForce)
end
</syntaxhighlight>

'''<tt>setForce()</tt>'''-toteutus on aika samanlainen kuin '''<tt>setAngle()</tt>'''. Ainoa erilaisuus on, että koska emme näytä voima-arvoa, käyttöliittymäkomponenttia ei tarvitse piirtää uudelleen.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::blue))

painter.translate(0, height())
painter.drawPie(Qt::Rect.new(-35, -35, 70, 70), 0, 90 * 16)
painter.rotate(-@currentAngle)
painter.drawRect(Qt::Rect.new(30, -5, 20, 10))
painter.end()
end
</syntaxhighlight>

Piirrämme kuin kappaleessa 9.

<syntaxhighlight lang="ruby">
def cannonRect()
result = Qt::Rect.new(0, 0, 50, 50)
result.moveBottomLeft(rect().bottomLeft())
return result
end
</syntaxhighlight>

Funktio '''<tt>cannonRect()</tt>''' palauttaa nelikulmion, joka sisältää kanuunan sisältävän käyttöliittymäkomponentin. Luomme aluksi nelikulmion, jonka koko on 50 x 50 ja siirrämme sen niin, että sen vasen alakulma on sama kuin käyttöliittymäkomponentin vasen alakulma.

Funktio [http://doc.qt.nokia.com/latest/qwidget.html#rect-prop Qt::Widget::rect()] palauttaa käyttöliittymän sisältämän nelikulmion käyttöliittymän omina koordinaatteina. Nelikulmion vasen yläkulma on aina (0, 0).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/t10.rb t10.rb]'''

Konstruktori on enimmäkseen sama, mutta joitakin uusia bittejä on lisätty.

<syntaxhighlight lang="ruby">
force = LCDRange.new()
force.setRange(10, 50)
</syntaxhighlight>

Lisäämme toisen '''<tt>LCDRange</tt>'''-komponentin, jota käytetään voiman asettamiseen.

<syntaxhighlight lang="ruby">
connect(force, SIGNAL('valueChanged(int)'),
cannonField, SLOT('setForce(int)'))
connect(cannonField, SIGNAL('forceChanged(int)'),
force, SLOT('setValue(int)'))
</syntaxhighlight>

Yhdistämme käyttöliittymäkomponentin '''<tt>force</tt>''' ja käyttöliittymäkomponentin '''<tt>cannonField</tt>''', aivan kuin teimme käyttöliittymäkomponentille '''<tt>angle</tt>'''.

<syntaxhighlight lang="ruby">
leftLayout = Qt::VBoxLayout.new()
leftLayout.addWidget(angle)
leftLayout.addWidget(force)

gridLayout = Qt::GridLayout.new()
gridLayout.addWidget(quit, 0, 0)
gridLayout.addLayout(leftLayout, 1, 0)
gridLayout.addWidget(cannonField, 1, 1, 2, 1)
gridLayout.setColumnStretch(1, 10)
</syntaxhighlight>

Kappaleessa 9 sijoitamme '''<tt>angle</tt>'''-komponentin asettelun vasemman alakulman soluun. Nyt haluamme siihen soluun kaksi käyttöliittymäkomponenttial, joten teemme pystysuoran ruudun, laitamme pystysuoran ruudun rasterinsoluunl, ja laitamme sekä '''<tt>angle</tt>''' että '''<tt>range</tt>''' pystysuoraan ruutuun.

<syntaxhighlight lang="ruby">
force.setValue(25)
</syntaxhighlight>

Alustamme voima-arvoksi 25.

=== Sovelluksen suorittaminen ===

Meillä on nyt voimaohjaus.

=== Harjoitukset ===
Tee kanuuna piipun koko riippuvaiseksi voimasta.

Put the cannon in the bottom-right corner.

Try adding a better keyboard interface. For example, make + and - increase and decrease the force and enter shoot. If you're bothered by the way the '''<tt>Left</tt>''' and '''<tt>Right</tt>''' keys work, change that too. [Hint: Reimplement [http://doc.qt.nokia.com/latest/qwidget.html#keyPressEvent Qt::Widget::keyPressEvent()].]

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10/27/fi

2011-10-29T12:31:16Z

Centerlink: Created page with "=== Harjoitukset === Tee kanuuna piipun koko riippuvaiseksi voimasta."

=== Harjoitukset ===
Tee kanuuna piipun koko riippuvaiseksi voimasta.

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10/26/fi

2011-10-29T12:29:52Z

Centerlink: Created page with "Meillä on nyt voimaohjaus."

Meillä on nyt voimaohjaus.

Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10/fi

2011-10-29T12:29:52Z

Centerlink: Created page with "Meillä on nyt voimaohjaus."

<languages />

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10}}

{{TutorialBrowser|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby -oppikurssi]]|
name=Sileää kuin silkki|
pre=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_09|Oppikurssi 9 - Kanuunalla onnistuu]]|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_11|Oppikurssi 11 - Annetaan sille laukaus]]
}}
== Sileää kuin silkki ==
[[Image:Qt4_Ruby_Tutorial_Screenshot_10.png|center]]
Tiedostot:
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/lcdrange.rb lcdrange.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/t10.rb t10.rb]
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/cannon.rb cannon.rb]

=== Yleiskuva ===

Tässä esimerkissä lisäämme voimaa ohjaimeen.

=== Läpikäynti rivi riviltä ===
'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/cannon.rb cannon.rb]'''

Kentällä '''<tt>CannonField</tt>''' on nyt voima-arvo kulman lisäksi.

<syntaxhighlight lang="ruby">
signals 'angleChanged(int)', 'forceChanged(int)'
slots 'setAngle(int)', 'setForce(int)'
</syntaxhighlight>

Voiman rajapinta noudattaa samaa käytäntöä kuin kulma.

<syntaxhighlight lang="ruby">
def initialize(parent = nil)
super()

@currentAngle = 45
@currentForce = 0

setPalette(Qt::Palette.new(Qt::Color.new(250, 250, 200)))
setAutoFillBackground(true)
end
</syntaxhighlight>

Voima '''<tt>@currentForce</tt>''' on alustettu nollaksi.

<syntaxhighlight lang="ruby">
def setAngle(angle)
if angle < 5
angle = 5
elsif angle > 70
angle = 70
end

if @currentAngle == angle
return
end

@currentAngle = angle
update(cannonRect())
emit angleChanged(@currentAngle)
end
</syntaxhighlight>

Teimme pienen muutoksen '''<tt>setAngle()</tt>'''-funktioon. Se piirtää uudelleen käyttöliittymän osan, joka sisältää kanuunan.

<syntaxhighlight lang="ruby">
def setForce(force)
if force < 0
force = 0
end
if @currentForce == force
return
end

@currentForce = force
emit forceChanged(@currentForce)
end
</syntaxhighlight>

'''<tt>setForce()</tt>'''-toteutus on aika samanlainen kuin '''<tt>setAngle()</tt>'''. Ainoa erilaisuus on, että koska emme näytä voima-arvoa, käyttöliittymäkomponenttia ei tarvitse piirtää uudelleen.

<syntaxhighlight lang="ruby">
def paintEvent(event)
painter = Qt::Painter.new(self)

painter.setPen(Qt::NoPen)
painter.setBrush(Qt::Brush.new(Qt::blue))

painter.translate(0, height())
painter.drawPie(Qt::Rect.new(-35, -35, 70, 70), 0, 90 * 16)
painter.rotate(-@currentAngle)
painter.drawRect(Qt::Rect.new(30, -5, 20, 10))
painter.end()
end
</syntaxhighlight>

Piirrämme kuin kappaleessa 9.

<syntaxhighlight lang="ruby">
def cannonRect()
result = Qt::Rect.new(0, 0, 50, 50)
result.moveBottomLeft(rect().bottomLeft())
return result
end
</syntaxhighlight>

Funktio '''<tt>cannonRect()</tt>''' palauttaa nelikulmion, joka sisältää kanuunan sisältävän käyttöliittymäkomponentin. Luomme aluksi nelikulmion, jonka koko on 50 x 50 ja siirrämme sen niin, että sen vasen alakulma on sama kuin käyttöliittymäkomponentin vasen alakulma.

Funktio [http://doc.qt.nokia.com/latest/qwidget.html#rect-prop Qt::Widget::rect()] palauttaa käyttöliittymän sisältämän nelikulmion käyttöliittymän omina koordinaatteina. Nelikulmion vasen yläkulma on aina (0, 0).

'''[http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t10/t10.rb t10.rb]'''

Konstruktori on enimmäkseen sama, mutta joitakin uusia bittejä on lisätty.

<syntaxhighlight lang="ruby">
force = LCDRange.new()
force.setRange(10, 50)
</syntaxhighlight>

Lisäämme toisen '''<tt>LCDRange</tt>'''-komponentin, jota käytetään voiman asettamiseen.

<syntaxhighlight lang="ruby">
connect(force, SIGNAL('valueChanged(int)'),
cannonField, SLOT('setForce(int)'))
connect(cannonField, SIGNAL('forceChanged(int)'),
force, SLOT('setValue(int)'))
</syntaxhighlight>

Yhdistämme käyttöliittymäkomponentin '''<tt>force</tt>''' ja käyttöliittymäkomponentin '''<tt>cannonField</tt>''', aivan kuin teimme käyttöliittymäkomponentille '''<tt>angle</tt>'''.

<syntaxhighlight lang="ruby">
leftLayout = Qt::VBoxLayout.new()
leftLayout.addWidget(angle)
leftLayout.addWidget(force)

gridLayout = Qt::GridLayout.new()
gridLayout.addWidget(quit, 0, 0)
gridLayout.addLayout(leftLayout, 1, 0)
gridLayout.addWidget(cannonField, 1, 1, 2, 1)
gridLayout.setColumnStretch(1, 10)
</syntaxhighlight>

Kappaleessa 9 sijoitamme '''<tt>angle</tt>'''-komponentin asettelun vasemman alakulman soluun. Nyt haluamme siihen soluun kaksi käyttöliittymäkomponenttial, joten teemme pystysuoran ruudun, laitamme pystysuoran ruudun rasterinsoluunl, ja laitamme sekä '''<tt>angle</tt>''' että '''<tt>range</tt>''' pystysuoraan ruutuun.

<syntaxhighlight lang="ruby">
force.setValue(25)
</syntaxhighlight>

Alustamme voima-arvoksi 25.

=== Sovelluksen suorittaminen ===

Meillä on nyt voimaohjaus.

=== Exercises ===
Make the size of the cannon barrel be dependent on the force.

Put the cannon in the bottom-right corner.

Try adding a better keyboard interface. For example, make + and - increase and decrease the force and enter shoot. If you're bothered by the way the '''<tt>Left</tt>''' and '''<tt>Right</tt>''' keys work, change that too. [Hint: Reimplement [http://doc.qt.nokia.com/latest/qwidget.html#keyPressEvent Qt::Widget::keyPressEvent()].]

[[Category:Ruby]]

Translations:Development/Tutorials/Qt4 Ruby Tutorial/Chapter 10/25/fi

2011-10-29T12:23:58Z

Centerlink: Created page with "=== Sovelluksen suorittaminen ==="

=== Sovelluksen suorittaminen ===