ID:135041
 
Here are a few handy functions found in some text editors that would work wonders for the functionality of code eating in Dream Maker:

* The ability to select multiple sections that are not adjacent to each other.

if(T)
for(var/obj/<B>track</B>/O in T)
if(O && O.track_number == src.<B>track_number</B>)
return T
T = get_step(src, turn(src.dir, -90))
if(T)
for(var/obj/<B>track</B>/O in T)
if(O && O.track_number == src.track_number)
return T

I could then select various blocks and perform advanced find/replace functions on them.


* Regex wildcards. Alternatively, use zMUD/TinTin MUD client pattern matching as a more simplistic (and still quite powerful) means.


* Block highlighting, similar to if you have a command prompt window open on a Windows OS. It highlights a block of text instead of lines.


* Multiple-line fields for find and replace. Simply have it insert \n at the line breaks when actually performing the function. This would be EXTREMELY handy.


* Line bookmarks, or rather, text anchored bookmarks. These could be accessed with a quick bookmark panel, or a bookmark drop-down on the menu.


* Cached clipboard function, so that the last 20 or so text entries to the clipboard are saved. This would only check entries saved to the clipboard if they were done in Dream Maker itself using the copy or cut functions, not external programs. (This prevents looping continually through the clipboard.)


* Most important: Have the Update button, or a new "Reload" button do just that -- reload files in the environment. This would allow us to easily edit files in another text editor (provided the above features were not added) and then reload the environment quickly, then compile to test.


~Polatrite~
Polatrite wrote:
* Most important: Have the Update button, or a new "Reload" button do just that -- reload files in the environment. This would allow us to easily edit files in another text editor (provided the above features were not added) and then reload the environment quickly, then compile to test.

Open up Dream Maker and look on the bottom left. Dream Maker already has an "Update" button that does just what you're looking for.
In response to Wizkidd0123
Wizkidd0123 wrote:
Polatrite wrote:
* Most important: Have the Update button, or a new "Reload" button do just that -- reload files in the environment. This would allow us to easily edit files in another text editor (provided the above features were not added) and then reload the environment quickly, then compile to test.

Open up Dream Maker and look on the bottom left. Dream Maker already has an "Update" button that does just what you're looking for.

The update button doesn't reload *.dm code files. It also doesn't seem to reload *.dmi files that have been loaded (and cached) into memory.

To test, open a *.dm file in a notepad window, edit it, then click the Update button in your environment. You'll notice it doesn't reload with the new changes. This might only occur with the currently open *.dm file though, I haven't tested it otherwise. Either way, Update may want to close all windows, remove all objects from the cache, then reload the environment entirely.


~Polatrite~