1
0
mirror of https://bitbucket.org/librepilot/librepilot.git synced 2024-12-04 12:24:11 +01:00
The LibrePilot open source project was founded in July 2015. It focuses on research and development of software and hardware to be used in a variety of applications including vehicle control and stabilization, unmanned autonomous vehicles and robotics.
Go to file
Kevin Finisterre 92c19f2d74 Changed the element id's in one of the SVG files that I incorrectly edited. This prevents the error:
Could not resolve property : SVGID_1_

Error comes from qsvghandler.cpp or qsvgstyle.cpp in the QT libraries Qt5.2.0//5.2.0-beta1/Src/qtsvg/src/svg/

The fixedwing-shapes.svg and flyingwing-shapes.svg files need modified to prevent the errors caused by qsvgtinydocument.cpp in the QT libraries.

Couldn't find node aileron. Skipping rendering.
Couldn't find node vtail. Skipping rendering.

These errors come from the case statement that was added to updateImageAnd Description() for FixedWingPage

+    switch (type) {
+    case SetupWizard::FIXED_WING_AILERON:
+        elementId = "aileron";
+        break;
+    case SetupWizard::FIXED_WING_VTAIL:
+        elementId = "vtail";
+        break;
+    default:
+        elementId = "";
+        break;
+    }

A similar error needs to be resolved in connectiondiagram.cpp
+            switch (m_configSource->getVehicleSubType()) {
+            case VehicleConfigurationSource::FIXED_WING_AILERON:
+                elementsToShow << "aileron";
+                break;
+            case VehicleConfigurationSource::FIXED_WING_VTAIL:
+                elementsToShow << "vtail";
+                break;
+            default:
+                break;
+            }

Likewise outputcalibrationpage.cpp will need to reverence the elements inside the SVG file properly.
+        m_vehicleElementIds << "fixed-aileron" << "aileron";
+        m_vehicleHighlightElementIndexes << 0 << 1;
...
+        m_vehicleElementIds << "fixed-vtail" << "vtail";
+        m_vehicleHighlightElementIndexes << 0 << 1;

Until these elements are fixed in the SVG files the wizard will not render properly and allow the user to click *next*.
2013-11-24 17:29:38 -05:00
artwork Add a simply readme 2013-11-14 23:14:24 +11:00
flight Merge branch 'next' into corvuscorax/callbackeventdispatcher2 2013-11-19 18:36:20 +01:00
ground Changed the element id's in one of the SVG files that I incorrectly edited. This prevents the error: 2013-11-24 17:29:38 -05:00
hardware Add hardware files 2012-10-16 22:52:45 +11:00
make OP-1103 There was a typo in tools.mk 2013-11-04 08:07:07 +11:00
matlab Reset executable bits from non-executable files (Windows legacy) 2013-04-24 01:18:46 +03:00
package OP-1103 Some minor cleanup work and adding a version check for Qt5.1 2013-11-13 21:04:57 +11:00
shared Merge remote-tracking branch 'origin/next' into amorale/OP-1058_uavo_named_accessors 2013-08-31 16:03:30 +02:00
.gitattributes .gitattributes: add a note how to renormalize old branches for merge 2013-04-24 03:31:09 +03:00
.gitignore OP-1103 Fix for build error on OSX 10.8 after Qt5.1.1 update 2013-11-04 00:13:14 +11:00
.gitmodules OP-892: fix broken op_overo path in .gitmodules 2013-04-12 20:10:20 +03:00
CREDITS.txt Fixed typos 2013-11-13 18:03:20 +01:00
GPLv3.txt Move GPLv3.txt from flight/Doc/License/ to top directory and convert to CRLF 2013-04-24 22:39:28 +03:00
LICENSE.txt OP-910: reformat LICENSE.txt, no text changes 2013-06-01 22:10:39 +02:00
Makefile Makefile: remove unused target (gcs_all_clean) 2013-05-28 20:58:07 +03:00
MILESTONES.txt OP-910: reformat and update MILESTONES.txt 2013-06-01 22:10:44 +02:00
README.txt Update README.txt with project sites list 2013-04-25 13:13:34 +03:00
WHATSNEW.txt Merge branch 'rel-13.06.02' 2013-07-05 19:02:39 -07:00

What is OpenPilot all about?
----------------------------

The project aims at implementing the best features of all existing similar systems developed by
enthusiasts and combines them into a single, easy-to-use software/hardware package. The ease-of-use
in this case does not imply functional simplicity or compromises. There are no rigidly defined
constraints and settings, but a full-fledged programming language configuration loaded via a
Ground Control Station and other advanced features. OpenPilot is developed as a powerful platform
for all types of vehicles.

This is a non-profit project of the OpenPilot Foundation
--------------------------------------------------------

This is a project using only volunteer personnel who have donated enormous amounts of time, money
and effort. Please respect the people that are part of the project and their generosity. OpenPilot
is funded entirely at the expense of those who spend their time and money in the development of the
public project which helps it grow. Giving complete and correct references to all their work is not
only a legal requirement of the CC-BY-SA license, but also simple respect for their work. The people
who create this project, really deserve it for their very hard work.

The OpenPilot project web sites
-------------------------------

The project provides feature-rich development and collaboration environment using advanced tools such
as GCC compilers, git, Atlassian JIRA, Confluence, FishEye, Crucible, Bamboo, Crowd, forums and blogs.

Main project web site:	http://www.openpilot.org/
Project forums:		http://forums.openpilot.org/
Wiki, docs and manuals:	http://wiki.openpilot.org/
Bug and issue tracker:	http://progress.openpilot.org/
Source code repository:	http://git.openpilot.org/
Crucible code reviews:	http://reviews.openpilot.org/cru
Project build server:	http://bamboo.openpilot.org/
Community blogs:	http://forums.openpilot.org/blogs/
Software downloads:	http://wiki.openpilot.org/display/BUILDS/OpenPilot+Software+Downloads

How to build from source?
-------------------------

make all_sdk_install
make all

The project supports Windows, Linux and Mac OS X platforms as well as Android.
Check the wiki for more details: http://wiki.openpilot.org/display/Doc/OpenPilot+Developer+Manual