rzaba0 / polybobin Goto Github PK

In PolyWorks it works like this:

1. RMB opens a list with found sceneries
2. in normal mode, it places a new scenery

list of found sceneries looks like this:

Additional frame with scenery options:

If "Rotate" is selected, after placing a new scenery user can rotate it.
If "Scale" is selected, after placing a new scenery and rotating (if selected too) user can scale it.

In PolyWorks it moves every selected object by default. With ALT it rotates everything by the opposite origin (it has 8). With CTRL it scales everything.

Properties window should work like in Polyworks. For now we only need to handle map, polygon, scenery and texture settings.

• https://forums.soldat.pl/index.php?topic=35195.0
• https://github.com/Soldat/polyworks/

While placing a new vertice for a polygon, it should snap to the nearest vertices of other polygons.

In PolyWorks it moves texture on selected polygon vertices, if none are selected then it transforms only one vertice at the current cursor position

Now it is needed to make settings.ini manually.

It should remember X last opened/created maps so you can reopen particular map faster:

In PolyWorks it colours all selected vertices and also sceneries at once with current colour. If none are selected then it colours first polygon or scenery behind cursor. With ALT being pressed it picks vertice or scenery colour behind the cursor.

In PolyWorks it works like this:

1. in default mode picks nearest vertex colour
2. with SHIFT pressed, picks colour at the current position of the cursor
3. with CTRL pressed, moves selection as in selection tool

Currently only 1st frame is rendered

In PolyWorks it colours vertices (without sceneries) behind the cursor with the current colour. User can hold and drag to colour multiple vertices. If there are selected vertices it colours only those. With ALT pressed user can pick colour behind the cursor.

With current design it's hard to switch to other libraries so we want to have modular design. And then we could switch for example from wxWidgets to Qt easily in the future.

By modular design i mean having functionality separated into modules so when one module is deleted the whole program still works somehow and it's not that devastating.

Example structure would look like this:

1. Frontend (all drawing, wxWidgets currently)
2. Backend (functionality of tools and others)
3. Core (communication between modules)

I'm not sure how it works exactly but when you switch tabs and add sceneries in both maps multiple times, program crashes at line 322 eventually.

TBA