Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checking Properties in Assessment #35

Open
caioviel opened this issue Jul 24, 2012 · 1 comment
Open

Checking Properties in Assessment #35

caioviel opened this issue Jul 24, 2012 · 1 comment
Labels
Milestone

Comments

@caioviel
Copy link
Member

This bug was detected in the presente lacture NCL.

See relevant NCL code:

    <media src="imagens/btnVideos.png" descriptor="dpBtnMainVideo" id="btnMainVideo">
          <property name="linkedVideo" value="mainVideo"/>
          <property name="visible" value="true"/>
    </media>

    <context>
            <media refer="btnMainVideo" instance="new" id="chap1_btnMainVideo"/>

            <link xconnector="onSelectionTestSetStart">
                    <bind role="propertyType" interface="linkedVideo" component="chap1_btnMainVideo">
                            <bindParam name="testValue" value="mainVideo"/>
                    </bind>
            ...
            </link>

    <context>

There is a media (btnMainVideo) with a property "linkedVideo". This media is refereed inside a context by a refer-node called chap1_btnMainVideo.

A link uses a assessment to compare the value of the property.

In the Listener.js, there is a call: (line 147)

var propertyValue = $(thisAssessment.bindComponent).data('property')[thisAssessment.bindInterface];

This call gets the value to be compared, but the value return is undefined.

Actually the value of $(thisAssessment.bindComponent) is similar to the folling:

[
<img class="player" id="ncl2_chap1_btnMiniVideo2" src="aula/​imagens/​btnVideos.png" style="z-index:​ 100;​ width:​ 171px;​ height:​ 96px;​ cursor:​ pointer;​ opacity:​ 1;​ border-color:​ yellow;​ ">​
] 

I believe this is caused due the refer.

@caioviel
Copy link
Member Author

The value printed in the issue description is from other media with similar behaviour.

@ghost ghost assigned alexcr Aug 7, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants