greebo

You want the property panel completely closed? I think that might be one of the things that are not possible with the new layout, I have to add support for that.

See the first post, the various controls are listed in the "Window" menu now. With the new docking capabilities any of the removed layouts should be achievable in DR 3.5.0.

Specify incorrect, how does it look like?

Confirmed, I'll look into that for the next release. https://bugs.thedarkmod.com/view.php?id=6143 edit: fixed in source.

It's a limitation of the wxWidgets AUI framework that there is one "center" or "main" pane that cannot be removed or undocked or moved around. But you can swap out the main view with another one with a shortcut, have a look at the Edit > Keyboard shortcuts and look for the ones starting with ToggleMainControl. You should find one with ToggleMainControl_Camera - this one will replace the main orthoview with a camera view. By repeatedly pressing the shortcut you will keep changing between ortho and camera.

There's not much difference between the installer and the portable version. The installer just puts it into your Program Files folder and registers DR in the "Programs and Features" list for uninstallation. When uninstalling the data in the AppData\Roaming\DarkRadiant folder should and will not get touched, they stick around. If you plan on going ahead with the portable versions, just uninstall the old 2.x version and keep using the portable one.

A file has been missing in CMakeLists.txt, can you try again using latest master, please?

Linux, I suppose?

Some day, when my backlog has reached 100+ missions It might be a ghosting marathon, using a two-week supply of coke, peanuts and diapers.

DarkRadiant 3.5.0 is ready for download. What's new: Feature: More customisable layout, all windows and panes can be dragged and arranged Layouts like Embedded, Regular and Splitpane are superseded and have been removed Tweak: The LayerControlPanel's tooltip popup is now less annoying Tweak: Clarify distinction between Shadow render mode and other render modes Fixed: Show/hide Light Volumes for combined entities inconsistent Fixed: Currently applied particleDef not selected in Particle Selector Fixed: Layer visibility checkbox not reacting to double-clicks Fixed: Cannot toggle visibility of layers in Linux Fixed: Drag-and-dropping layers is not working in Linux Feature: Customisable Layout (click to see the videos) Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.5.0 and of course linked from the website https://www.darkradiant.net Thanks to all the awesome people who keep using DarkRadiant to create Fan Missions - they are the main reason for me to keep going. Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. The list of changes can be found on the our bugtracker changelog. Have fun mapping!

I'd like to finish working on the user interface changes, it's taking shape already. A release is always a chunk of work, and since Linux folks tend to compile from source more than Windows users, I'd be inclined to not push out an emergency release. I won't be too long till 3.5.0, I'd like to keep the pace of doing a release every 2-3 weeks anyway. The UI changes are rather substantial, this is why it takes a bit longer than usual. After getting that back into master, I'm going to fix the most urgent issues like crashes or other annoyances, and 3.5.0 is done.

This is an XPath, used to handle the internal DR registry (it's XML). I'll have to fix that warning some time, but right now I don't think it's critical.

This is a very old feature, and I got the impression that nobody is using it. If that's the case, I'd like to get rid of the corresponding code, unused features are just a maintenance burden. edit: not even knowing that feature counts as "no"

You can also drag-select items, so dragging alone wouldn't determine the action yet. One had to separate the drag-selection from the regular toggle selection command (they are bound to the same mouse action at the moment). Note, I'm not trying to defend the system, just stating how DR's code is determining things (it is still using the same old GtkRadiant principles, once you perform the click (mouse down) the action is determined immediately). Of course it's possible to fundamentally change the way DR is handling manipulations and selections, but for every such change you'll probably face differing opinions and/or resistance.

So you have LMB assigned to both Sekection and Manipulation? I guess that's just a conflict of interest, DR can't know what you intend to do with the LMB.

It has a bug with the camera arrow keys not working. I'll fix that in a few days, until then I wouldn't recommend switching. Otherwise it'd be functional.

It depends on how difficult or expensive it is to classify the entities. Should doors be recognised by their classname, or by the model they use? If it's too hard to figure out for an algorithm, then the filter wouldn't be very responsive.

Great. In my branch with the experimental layout there's already a button to maximise the docked panes, but I'll have to look into it if there's a way to maximise a certain area using a shortcut. I bet there is.

For the camera this should already be possible, I think the key command is named "ToggleFullScreenCamera".

There's no restriction on which layer you decide to put your map elements. The layer hierarchy is a purely organisational help, it doesn't impose anything to the map itself, all the layers are equally capable, whether a child layer has been assigned to it or not. Why can't you select a parent node alone? If you need that parent layer exclusively, right now you have to select the layer, then de-select the child nodes one by one. I could add a context menu option to select just the parent layer without children.

Got it. It's possible, but I can't estimate yet how much work that'd require. I'm going to do some experimenting on the layout handling first.

You mean that the floating dialog is adjusting its size based on the selected tab? It'd be possible, I guess.

You mean the drag-and-drop code? It's in radiant/ui/layers/LayerControlDialog.h/.cpp

It's sorted alphabetically right now. The layers don't persist any sort order in the map files. Yes, drag and drop works much better in Windows, the wxGTK port is not giving good visual feedback about where you're going to drop the layer.

I've opened an issue on the tracker to explore things a bit (#6131). Maybe we can improve the dockable layout to replace all existing hardcoded window layouts.