Message-ID: <001401bdb59b$f7cff000$784d08c3@arthur> Reply-To: "Arthur" From: "Arthur" To: "DJGPP Mailing List" Subject: Re: DJGPP & Rhide Date: Wed, 22 Jul 1998 19:01:04 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Precedence: bulk >> >1) Creating a project takes less than 20 seconds. >> >> Yup. 20 seconds. OK, so I've just written a piece of code that's crashed the >> computer. It takes the best part of a minute to get me up to the desktop >> (more if scandisk has to run), and 20 seconds just seems a little too much. >> It's an extra click or two. And I have to do this over and over again until >> I fix the bit which crashes. > >Wrong! Write your project, exit RHIDE to save it on disk (flush the >cache if you can do it) enter RHIDE again. Now crash the machine the >project will be there when you reboot. Yes, but I still don't want to use projects. >> >2) What do you mean with "import all the stuff", what stuff? >> >> You create a project then import the file(s) into it (OK, so it's not called >> importing...) > >That's needed just ones. And if you are creating a multifile program >you *need* a project with any IDE, isn't just with RHIDE. Yes, I know. Or a makefile. >> >3) You don't need to setup directories for a simple file. You only >> >need to setup directories for a multidirectory project. >> >> I do. Every time you load up your C file and want to get it to run, you have >> to use Options->Directories->Sources otherwise it won't compile (given that >> not all of my sources are in the same place). This is the real problem.Why >> can't it do this as it loads the file? > >You are doing something *very* wrong. Run RHIDE from the directory >where your sources are located, that's all. You only need to specify >the source dir if the files are located in more than one directory. OK, let me repeat: not all of my sources are in the same place. I like it that way. They're all in their own folders according to type, current project etc. Also, I've got RHIDE in my Start Menu, so unless I want to create a shell or batch file for it I can't do what you suggest. >> >4) What is "the correct working resolution"? I never setup a thing >> >with this name ... >> >> Well, the resolution (Options->Environment->Preferences) that I find less >> straining on the eyes... The correct resolution for ME. > >That's needed only in rhide.gpr, you don't need to setup it all the >time. OK. >> >Normally loading the file and presing CTRL+F9 all is OK. In some >> >cases (for example when you have a rhide.gpr file) you need to just >> >create a project with the file. What's so complex? >> >> Nothing, it's just a little bit more to do, that's all. When I did have >> DFE95 working, I could open the file, click on compile, click on run and >> it's done. I didn't need to create a project, I didn't need to change the >> directories. Even though I can't get it to compile anymore, I still use it >> to edit my code and then open a DOSBOX and call gpp myself. I find that >> quicker than using RHIDE. >> > >That's because you are wrongly using the projects and you are calling >RHIDE with "working directory" empty or pointing to the bin directory >(a very common error). It's not an error, it's by choice (see above). I do not want to use a project if I'm only using one file. In my current setup, I can open Explorer and double-click on the file to edit it. I can then open a DOSBOX which defaults to the open directory in Explorer. I type "gpp file.cc -o file.exe" which compiles my file. I can call RHIDE from the DOSBOX if I want to, and it works properly ('cos it's in the right directory). And I do, if there's more than one file to edit. But for a single file, on which I am experimenting new routines etc, it's easier to fiddle about with the switches manually (IMO). I'm going to have a look at your editor, SET, and see if it's an improvement :^) James Arthur jaa AT arfa DOT clara DOT net