Similar to in-game search feature (F in map) so you can find things easier.

just diving into this whole type of thing and when i looked into getting qt5 it said that the full version is nearly $500/month so i was wondering if the free version is suitable for the editor and if so, how to get it to work. as i said, completely new to this sort of thing so any advice would be greatly appreciated!

When i created a new system, i can see lines indicating planets, but no textures on said planets.
Issue/bug prehaps? On windows 10

When I rename on the same system, It's will pop-up a "the name has existed system" worming window sometimes.

Currently this map editor is outdated by several years and will cause a lot of mess if used with current map, the only release tag is even more severely outdated and while the "nightly" build exist it's extremely obscure and not exactly public(it was shared only on Discord for all I know) making people think they need to build it themselves only to find that this project lacks of any actual guide or documentation for building it.

Currently we have a much more updated map editor here: https://github.com/quyykk/plugin-editor which also appears to be preferred by current dev as well as being considered as the new standard since it can handle multiple map file (which is part of the reason for the recent map file splitting).

I suggest we either actually maintain it (which seems unlikely) or archive it and change all the links to Quyykk's editor and add some redirect message here in case someone ends up here somehow.

Accidentally shifting planets and systems can be annoying, especially when the general working area is a relatively convoluted.

As it stands, however, being careful is sufficient, but having this feature would make things a bit better. Locked systems can also serve as a reminder that this system is satisfactorily designed.

just thought you should know

To avoid having to save the map, open it in the game and finding the system, it would be nice to have a "preview" button in the system tab that shows how the selected system looks in game, which means rendering the stars in the background and removing the UI elements like the planet orbits and the habitable zone. An alternative is to be able to select individually which of these UI elements to show, plus a button for the background stars

Hi all, loving the game! I just packaged the map editor for Arch Linux when I noticed this:

The target path really should be /usr/bin/, according to Linux's Filesystem Hierarchy Standard.

Currently, the area from where a planet can be selected doesn't expand on some planets, which makes it difficult to select them

I'm pretty noob, but I am trying to do some custom map-making. When I create hyperlinks between systems, they display red. Does that indicate anything?

I know you have to manually create wormholes, but how do you link them code-wise?

After running qmake, make returns a compiler error.
Log:
g++ -c -pipe -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -o main.o main.cpp In file included from main.cpp:13:0: MainWindow.h:63:5: warning: identifier ‘nullptr’ is a keyword in C++11 [-Wc++0x-compat] QTabWidget *tabs = nullptr; ^ MainWindow.h:50:48: warning: override controls (override/final) only available with -std=c++11 or -std=gnu++11 virtual void keyPressEvent(QKeyEvent *event) override; ^ MainWindow.h:51:47: warning: override controls (override/final) only available with -std=c++11 or -std=gnu++11 virtual void closeEvent(QCloseEvent *event) override; ^ MainWindow.h:52:55: warning: override controls (override/final) only available with -std=c++11 or -std=gnu++11 virtual void dragEnterEvent(QDragEnterEvent *event) override; ^ MainWindow.h:53:45: warning: override controls (override/final) only available with -std=c++11 or -std=gnu++11 virtual void dropEvent(QDropEvent *event) override; ^ MainWindow.h:63:24: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 QTabWidget *tabs = nullptr; ^ MainWindow.h:64:30: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 DetailView *detailView = nullptr; ^ MainWindow.h:65:30: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 GalaxyView *galaxyView = nullptr; ^ MainWindow.h:66:30: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 SystemView *systemView = nullptr; ^ MainWindow.h:67:30: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 PlanetView *planetView = nullptr; ^ MainWindow.h:69:25: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 QMenu *galaxyMenu = nullptr; ^ MainWindow.h:70:25: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 QMenu *systemMenu = nullptr; ^ MainWindow.h:63:24: error: ‘nullptr’ was not declared in this scope QTabWidget *tabs = nullptr; ^ MainWindow.h:64:30: error: ‘nullptr’ was not declared in this scope DetailView *detailView = nullptr; ^ MainWindow.h:65:30: error: ‘nullptr’ was not declared in this scope GalaxyView *galaxyView = nullptr; ^ MainWindow.h:66:30: error: ‘nullptr’ was not declared in this scope SystemView *systemView = nullptr; ^ MainWindow.h:67:30: error: ‘nullptr’ was not declared in this scope PlanetView *planetView = nullptr; ^ MainWindow.h:69:25: error: ‘nullptr’ was not declared in this scope QMenu *galaxyMenu = nullptr; ^ MainWindow.h:70:25: error: ‘nullptr’ was not declared in this scope QMenu *systemMenu = nullptr; ^ In file included from Map.h:17:0, from main.cpp:14: Planet.h:111:72: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 double requiredReputation = std::numeric_limits<double>::quiet_NaN(); ^ Planet.h:112:59: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 double bribe = std::numeric_limits<double>::quiet_NaN(); ^ Planet.h:113:62: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 double security = std::numeric_limits<double>::quiet_NaN(); ^ Planet.h:115:61: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 double tribute = std::numeric_limits<double>::quiet_NaN(); ^ Planet.h:116:70: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 double tributeThreshold = std::numeric_limits<double>::quiet_NaN(); ^ Planet.h:117:74: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 double tributeFleetQuantity = std::numeric_limits<double>::quiet_NaN(); ^ In file included from System.h:16:0, from Map.h:18, from main.cpp:14: StellarObject.h:89:23: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 double distance = 0.; ^ StellarObject.h:90:21: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 double period = 0.; ^ StellarObject.h:91:21: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 double offset = 0.; ^ StellarObject.h:92:19: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 int parent = -1; ^ In file included from Map.h:18:0, from main.cpp:14: System.h:131:10: error: ‘map’ in namespace ‘std’ does not name a template type std::map<QString, int> trade; ^ In file included from main.cpp:14:0: Map.h:72:30: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 mutable bool isChanged = false; ^ make: *** [Makefile:282: main.o] Error 1
I am using Gentoo under AMD64.

The program freezes and crashes for unknown reasons.

The first time it froze was when renaming a newly created system. I chose a name that, already existed and, upon renaming, the program froze and crashed.
The second time it crashed was when rearranging planets (I just clicked and dragged a random planet) in one of my systems.

Looks like I'll have to use the old ways until this is sorted.

P.S. How do I add labels to this issue?

The editor is usable without documentation, but it would be nice for new users.

When using the pre-compiled Win64 binaries, and after finding and downloading several missing DLLs, endless-sky-editor.exe, specifically libwinpthread-1.dll, libstdc++-6.dll, and libgcc_s_dw2-1.dll, I got the following error when I attempted to run endless-sky-editor.exe:

---------------------------
endless-sky-editor.exe - Entry Point Not Found
---------------------------
The procedure entry point _ZNSt8__detail15_List_node_base11_M_transferEPS0_S1_ could not be located in the dynamic link library D:\Games\endless-sky-win64-0.7.11\endless-sky-editor-win64-0.7.10\endless-sky-editor.exe.

I am using Windows 8.1 64bit with an Intel Intel Core i7 4770 and 24 GB of RAM.

Have an option to immediately see on the galactic map view those systems that have planets defined. Similar to how you're able to see what government is related to what systems.

Currently, stations and wormholes cannot be 'selected'. Their 'selection circles' are much smaller than planets, which may be why we can't 'select' them.

Also, allow us to create 'planets' like the stars that orbit the wormhole in the Pleiades.

Sorry to bug you again but I've run into a new error.

MainWindow.cpp: In member function ‘virtual void MainWindow::dropEvent(QDropEvent*)’:
MainWindow.cpp:146:51: error: invalid use of incomplete type ‘const class QUrl’
     QString path = event->mimeData()->urls().at(0).path();
                                                   ^
In file included from /usr/include/qt4/QtGui/qvector2d.h:46:0,
                 from /usr/include/qt4/QtGui/QVector2D:1,
                 from GalaxyView.h:18,
                 from MainWindow.cpp:16:
/usr/include/qt4/QtCore/qmetatype.h:299:7: note: forward declaration of ‘class QUrl’
 class QUrl;
       ^
In file included from /usr/include/qt4/QtCore/qnamespace.h:45:0,
                 from /usr/include/qt4/QtCore/qobjectdefs.h:45,
                 from /usr/include/qt4/QtGui/qwindowdefs.h:45,
                 from /usr/include/qt4/QtGui/qwidget.h:46,
                 from /usr/include/qt4/QtGui/qmainwindow.h:45,
                 from /usr/include/qt4/QtGui/QMainWindow:1,
                 from MainWindow.h:16,
                 from MainWindow.cpp:13:
/usr/include/qt4/QtCore/qglobal.h: In instantiation of ‘class QTypeInfo<QUrl>’:
/usr/include/qt4/QtCore/qlist.h:113:62:   required from ‘T& QList<T>::Node::t() [with T = QUrl]’
/usr/include/qt4/QtCore/qlist.h:470:46:   required from ‘const T& QList<T>::at(int) const [with T = QUrl]’
MainWindow.cpp:146:50:   required from here
/usr/include/qt4/QtCore/qglobal.h:2242:26: error: invalid application of ‘sizeof’ to incomplete type ‘QUrl’
         isLarge = (sizeof(T)>sizeof(void*)),
                          ^
In file included from /usr/include/qt4/QtCore/qobject.h:50:0,
                 from /usr/include/qt4/QtGui/qwidget.h:47,
                 from /usr/include/qt4/QtGui/qmainwindow.h:45,
                 from /usr/include/qt4/QtGui/QMainWindow:1,
                 from MainWindow.h:16,
                 from MainWindow.cpp:13:
/usr/include/qt4/QtCore/qlist.h: In instantiation of ‘void QList<T>::node_destruct(QList<T>::Node*, QList<T>::Node*) [with T = QUrl]’:
/usr/include/qt4/QtCore/qlist.h:757:18:   required from ‘void QList<T>::free(QListData::Data*) [with T = QUrl ’
/usr/include/qt4/QtCore/qlist.h:732:13:   required from ‘QList<T>::~QList() [with T = QUrl]’
MainWindow.cpp:138:38:   required from here
/usr/include/qt4/QtCore/qlist.h:431:31: warning: possible problem detected in invocation of delete operator: [-Wdelete-incomplete]
         while(from != to) --to, delete reinterpret_cast<T*>(to->v);
                               ^
/usr/include/qt4/QtCore/qlist.h:431:31: warning: invalid use of incomplete type ‘class QUrl’
In file included from /usr/include/qt4/QtGui/qvector2d.h:46:0,
                 from /usr/include/qt4/QtGui/QVector2D:1,
                 from GalaxyView.h:18,
                 from MainWindow.cpp:16:
/usr/include/qt4/QtCore/qmetatype.h:299:7: note: forward declaration of ‘class QUrl’
 class QUrl;
       ^
In file included from /usr/include/qt4/QtCore/qobject.h:50:0,
                 from /usr/include/qt4/QtGui/qwidget.h:47,
                 from /usr/include/qt4/QtGui/qmainwindow.h:45,
                 from /usr/include/qt4/QtGui/QMainWindow:1,
                 from MainWindow.h:16,
                 from MainWindow.cpp:13:
/usr/include/qt4/QtCore/qlist.h:431:31: note: neither the destructor nor the class-specific operator delete will be called, even if they are declared when the class is defined
         while(from != to) --to, delete reinterpret_cast<T*>(to->v);
                               ^
/usr/include/qt4/QtCore/qlist.h:433:32: error: invalid use of incomplete type ‘class QUrl’
         while (from != to) --to, reinterpret_cast<T*>(to)->~T();
                                ^
In file included from /usr/include/qt4/QtGui/qvector2d.h:46:0,
                 from /usr/include/qt4/QtGui/QVector2D:1,
                 from GalaxyView.h:18,
                 from MainWindow.cpp:16:
/usr/include/qt4/QtCore/qmetatype.h:299:7: note: forward declaration of ‘class QUrl’
 class QUrl;
       ^
make: *** [Makefile:307: MainWindow.o] Error 1

Checked after commit from Aug 5, 2017

All the planet sprites that were added in endless-sky/endless-sky#3458 and that finish with -b seem to never be used by the map editor when randomizing a system or a planet, which reduces differentiation quite a lot

Within the planet tab, there is a field labelled "Security". What does this field change?

Currently, simply opening the ES map in the map editor and saving the file with no modifications creates a lot of changes, which makes adding systems to the vanilla map harder. The changes I could find it does:
-reordering the data under planets (e.g. bribe after shipyard and outfitter)
-reordering planets in alphabetical order
-removal of unnecessary lines between systems
-removal of "" around planets, sprites (e.g. the black hole) and fleets that don't need it
-removal of "description" and "spaceport" empty lines under wormholes
-if there are more than one tribute fleets, all but the last one are removed
-reordering system links in alphabetical order (lots and lots of these)
-reordering of the "haze" line to go after habitable

While some of these seem reasonable, and perhaps could be fixed by changing them in the vanilla ES, others are proper errors, like the tribute fleets and the deletion of empty description and spaceport lines

It seems that, currently, if a wormhole has a description or spaceport the map editor automatically removes them

Sorry if this is a repeat/mentioned somewhere, but is there a makefile/cmake/scons setup if I'm compiling from source?

Have an option that allows the view on the galactic and/or system map to be recentered with typed in coordinates. This helps make navigating much faster when editing galactic maps that are further out of the view.

Please add a full documentation (including the build instructions) for the map editor. Thanks

Issue:
The vanilla Endless Sky game has systems located in more than one file, which means that the pug systems are effectively invisible and undetectable to anyone who doesn't spend a lot of time trying to find them.

Desired Solution:
That the map editor support looking in multiple files

Proposed method:

• Have an option or setting whereby the user can set the default path to the base Endless Sky folder (used to find images and other resources)
• Have the map-editor scan conduct a limited "loading" just like endless-sky itself does, which would then locate all relevant files regardless of where they are in the data folder.
• Have an "designate file" command that allows an additional file that may or may not be located within the endless sky folder (most commonly, a plug-in data file). This "designated file" would be loaded (if it isn't already), and would be remembered by the map editor as the designated location for any changes to be saved. In the case of editing vanilla endless sky, this file could be an included map file.

Result:
These changes would result in a map editor that is much more robust and thorough than it is currently, and one that would display all existing systems by default. This would also allow the map file to be broken up into multiple more manageable pieces, or support the addition of additional regions without having the core map file(s) bloated by additional content. It would also make it much easier to work with plug-in systems.

If there are more than one tribute fleets on a planet, which is supported in ES, the map editor seems to automatically remove all but the last line of the fleets

I hope i'm not overlooking something but I can't seem to find a way to open the editor.

It seems that the Save button in the Map editor doesn't work, only the Save as one does

Problem:
On the galaxy map, all systems are represented by an identical pale green dot, which conveys no useful information. Further more, it is impossible to tell from the galaxy map which systems belong to which government, which ones are inhabited, or even which ones have anything at all within the system.

Solution:

• change the system icon to represent something about the system so that the icon actually conveys something useful to the user.

Option 1:

• Emulate the map viewer from the game (the "mission" option) itself using a dummy set of reputations equivalent to a brand new starting character.
• As such, the galaxy view would show the galaxy as it exists at the start of the game with things colour coded accordingly. (this reveals where is uninhabited, restricted, hostile, and neutral)

Option 2:

• Change the system icon into a ring, and colour code it according to the government assigned to that system.
• Inside the ring, place a dot if there is someplace the player can land. (these could be colour coded according to the same government colours as well, perhaps with a split colour if there's more than one government in the system. Half blue half green, etc.)
• This would make it easy to see what government controls the system, and whether or not there are permanent places of interest within said system.

Of these two options, option 2 is my preference; but either one would be a significant improvement over the current.

Using the lastest editor's nightly, Windows 10, the app's icon that was added by MZ in 1f154b0 doesn't appear, and instead only the default windows no-icon image is shown

The bottom part is hidden from my view and I cannot scroll down.