QOrbitermanager: Difference between revisions
Langstonius (talk | contribs) No edit summary |
Langstonius (talk | contribs) No edit summary |
||
| Line 19: | Line 19: | ||
</table> | </table> | ||
<table width="80%" border=" | <table width="80%" border="1"> | ||
<tr> | <tr> | ||
<td colspan="3" bgcolor="#33CC00">''void'' '''showFloorplan'''(''int floorplantype'')</td> | <td colspan="3" bgcolor="#33CC00">''void'' '''showFloorplan'''(''int floorplantype'')</td> | ||
| Line 35: | Line 35: | ||
</table> | </table> | ||
<table width="80%" border=" | <table width="80%" border="1"> | ||
<tr> | <tr> | ||
<td colspan="3" bgcolor="#33CC00">''void'' '''saveScreenshot'''(''int attribute_number'')</td> | <td colspan="3" bgcolor="#33CC00">''void'' '''saveScreenshot'''(''int attribute_number'')</td> | ||
| Line 77: | Line 77: | ||
</table> | </table> | ||
<table width="80%" border=" | <table width="80%" border="1"> | ||
<tr> | <tr> | ||
<td colspan="3" bgcolor="#33CC00">''void'' '''cleanupScreenie'''('''')</td> | <td colspan="3" bgcolor="#33CC00">''void'' '''cleanupScreenie'''('''')</td> | ||
</tr> | </tr> | ||
<tr bgcolor="#999999"> | <tr bgcolor="#999999"> | ||
<td>Params</td> | <td width=%33>Params</td> | ||
<td>Description</td> | <td width=%33>Description</td> | ||
<td>Output</td> | <td>Output</td> | ||
</tr> | </tr> | ||
Revision as of 19:27, 3 October 2012
QOrbiter manager is what it sounds like. It manages the flow of operations in QOrbiter between the different context objects and the threaded dce side of the program. It can be accessed through 'manager'
Functions
| void getLiveTVPlaylist(') | ||
| Params | Description | EX |
| No Params | Calling this function will tell the router to populate the live tv playlist and return it to the playlist element. Calling it when no tv is playing has no result | Component.onCompleted:manager.getLiveTVPlaylist() |
| void showFloorplan(int floorplantype) | ||
| Params | Description | Example |
| int - The type of floorplan you want to display | This function brings up the floorplan for the selected room and populates the devices there on the screenshot image | |
| void saveScreenshot(int attribute_number) | ||
| Params | Description | Example |
| int - The Attribute number of the attribute you want to associate with the screenshot. It is provided in the screenshotAttributes listmodel that is prepared when grabbing a screeshot |
Saves the current screenshot to the attribute image |
Component {
id:thumbdelegate
Rectangle{
id:attributedelegate
height: 50
width: parent.width-1
color: style.accentcolor
Text {
id: propertystring
text: attributeType
}
MouseArea{
anchors.fill: parent
hoverEnabled: true
onEntered: attributedelegate.color = "aliceblue"
onExited: attributedelegate.color = style.accentcolor
onClicked: {
manager.saveScreenShot(attributeNo)
manager.cleanupScreenie()
assignscreenshot.destroy()
}
}
}
}
|
| void cleanupScreenie(') | ||
| Params | Description | Output |
| None | Destroys the last screenshot and empties the model. Depreciated and will be made automatic | |
| void resentCode(int parentDevice, int commandNumber) | ||
| Params | Description | Output |
| parentDevice - int - device number of the parent
commandNumber- int - the number of the command you wish to resend |
Resend and av control code. This function should be utilized within the device_commands model. The parameters are attributes of said mdel |
ListView
{
id:device_command_list
height: parent.height
width: scaleX(10)
anchors.top: parent.top
anchors.left: codelist.right
anchors.leftMargin: scaleY(5)
clip: true
model: device_commands
delegate: Rectangle{
id:device_box
height: scaleY(8)
width: scaleX(20)
color: "slateblue"
Column{
spacing: scaleY(1)
Text{
id:command_label
text:qs_command
font.pixelSize: scaleY(2)
}
}
MouseArea{
anchors.fill: parent
hoverEnabled: true
onEntered: device_box.color = "white"
onExited: device_box.color = "slateblue"
onClicked: manager.resendCode(i_parentDevice, i_commandnum)
}
}
}
|