For example, on the OSX version, when you. I use it mainly on OSX and there are so many things that are fundamentally flawed with it.
Im not a huge fan of the Adobe Extendscript Toolkit IDE. Whatever tools you use for editing or otherwise changing your source files, make sure that you always have DOS style CR+LF line endings ( \r\n, #13#10) in all lines, as LF only ( \n, #10) tends to confuse the IDE – you will notice that the blue dots in the debugger are out of sync with the source lines, and that compiler error line numbers are wrong. Hi There, I may be the only one who has this opinion, but Ill throw it out there for discussion anyways. It is also important for debugging when you have several source files with the same name in different directories that are in your search / browse path, or if you have not all your source directories in the search / browse path. To have this always work (even with visual form or frame inheritance) a correct project file is crucial. When you use the debugger in the IDE it will usually first compile the project. This is a safe thing to do if you never edit inside the IDE, but to keep the confirmations from appearing it is best to not have source files open in the Delphi editor at all while you edit them in emacs.Įven if you use a custom build script and build the project from emacs you should still keep the project file up-to-date. When you switch back to the IDE it will notice that files have been changed outside of it, and ask you whether to reload them (if they are currently opened in the editor). You can of course edit source files outside of the Delphi IDE.
0 kommentar(er)
