So, as I said, I'm pretty sure that the functionality that I am looking for is not (currently) in GZDB. It's actually quite a pain, especially if the found items list is long (as in the above example) and it's a pretty major limitation IMO.
So, doing the above task is a much longer process because every time I jump to a new line 160, I have to exit the found items dialogue, go to sector mode, check the sector's properties (and edit if necessary) then start a new search, remember where I was on the found items last time, scroll to that entry, pick the next one, rinse and repeat. I can't change to sector mode in the map without closing the found items dialogue (so I can't quickly check if the found line is attached to a sector that I want to edit) and I certainly can't edit, delete or otherwise change anything other than the found line. With GZDB, the above, basically, can't be done. If it is I can then hit enter to edit the sector, finish what I want to do with it, go back to the found items list and click on the next entry (which would then jump the map to centre on the next found line 160) and I can rinse and repeat until I have found all of the sectors that I want to change. In DeePsea, I can find all of the line type 160s, click through the found items list, move my mouse across to the map area of the screen, hit "S" to enter sectors mode and hover over the control sector to see its properties to find out if it is one that I want to edit. The results of this search (in both GZDB and DeePsea are shown above.) So what's the best way to find 3D control sectors? Search for line type 160. There isn't anything to particularly identify these sectors because there is nothing unusual about them versus other sectors. The following is what I was doing when I generated the above pictures: I wanted to find the control sectors for 3D floors and edit the sector properties. Or, as another example, it also means that I can't work on other items nearby that were not in the "found" list. I have to quit the found items dialogue, delete the item and search again.* So, I can't - for example, move my mouse across to the map, delete the item in question, move back to the found items, pick another one and continue. True, and that does much of what I want, but the problem is, all it allows me to do is edit the selection. "But Enjay, GZDB has the "Edit selection" button". In GZDB, the focus stays on the found items dialogue and (correct me if I'm wrong) I can't interact with the map at all. So, I can edit whatever I want on the map and then move back to the found items to click on another item.
Gzdoom builder bugfix full#
The found items dialogue stays on top, but I have full access to the normal 2D mapping features, the other menus, dialogues, everything. However, in DeePsea I can move my mouse away from the found items list and interact with the map screen in the normal way. (The result dialogue is simpler partly because the search type and parameters are picked from menus rather than the dialogue - many of the options in GZDB are also present in the DeePsea menus.) click on a found item and the map jumps to that position and highlights the found item). In DeePsea (sorry to keep harping on about it, but it's what I am familiar with) there is a very similar find functionality that up to this point behaves in much the same way as GZDB, producing a similar looking (if simpler) results dialogue that performs in a very similar way (i.e. That's where problems/limitations can manifest. Then I come to try and edit the found item. When I click on the various found items in the list, the map screen jumps to that item and centres it on the screen.
It can search for (and replace) many different types of objects and presents the search result in a nice, easy to read pop-up dialogue. Request 1: be able to interact with the rest of GZDB (especially the mapping functions) when the find dialogue results are active. Until my thoughts crystalise, it's probably too much to explain on a Github comment asking about the features. This post is more to float an idea or two and to find out about the feasibility of these particular feature requests as anything.
0 kommentar(er)
