[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

7. Some FAQs

Question: I have enabled the `Use tabs' option, but if I move the cursor through that tab, it seems, that RHIDE uses spaces

Answer:This behavior cannot (currently) be changed. Even when you have enabled the use of real tabs (characters with the code 9), the cursor is moved as if there are spaces.

Question: Are there any sample project files, to show how RHIDE works?

Answer:The sources of RHIDE include many project files to rebuild at least RHIDE with itself and many others.

Question: I have written some libraries. How can I use them in a project?

Question: How I can use a library, which I have?

Answer: There are some different ways to do this. On the one side you can include them directly in the project with the Add to project item function see section 3.8.3 Add item. But if they are not in the current directory, you must also set the library search path to the directory, where they are see section 3.9.1.2 Library directories. The other variant is to include them in the list of libraries see section 3.9.3 Libraries.

If this library is created with RHIDE, that means you have a project file for building this library you can also simply include that project file in your project. For examples, look at the RHIDE sources in the project file for RHIDE.

Question: I have a directory, where all my include files are. Can I setup RHIDE to have this directory every time in the include search path, when creating a new project?

Question: I prefer the 80x28 video mode over the default 80x25 mode. How I can turn this mode on by default for all newly created project files?

Answer: You can create a default project file. From this file RHIDE reads all the options, if it creates a new project. The default project must have the same basename as the executable of RHIDE and must be located in the same directory.

The creation of such a default project file is very simple. Change to the directory, where `rhide.exe' is located and run there
 
rhide rhide

Now make any changes in the options which you want to have as default for all newly created projects. This includes also settings in the various search paths. If you are ready, exit RHIDE and this project file will be your default project file.

Question: I know, that I can create a default project file. Can I create and use more than one?

Answer:Since DJGPP supports a quasi-Unix-like link for executables, you can create such a link also for RHIDE. As an example I will create a link to `rhide.exe' with the name `myrhide.exe'. At first I have to create the new file.
 
stubify -g myrhide.exe
Now I must tell `myrhide.exe' which program it really should run.
 
stubedit myrhide.exe runfile=rhide
Thats all. Or, if you have installed the GNU fileutils, you can use also now the `ln.exe' program to create the link:
 
ln -s rhide.exe myrhide.exe

Question: I don't want to type every time I start RHIDE the commandline -L de to use the German user interface. Is there any better way?

Answer: Create an environment variable LANGUAGE with your preferred language like
 
set LANGUAGE=de
and your problem is solved.

Question: I have 4 Mb RAM in my computer and every time, when I compile large files with optimizations enabled, my hard disk is working very hard.

Answer:Buy more RAM!

Question: I heard something about a newer version RHIDE. From where I can get exact information about this?

Answer: See
at the RHIDE home page.
This page contains the latest news and the latest version of RHIDE.

Question: I have a lot of money and don't know what to do with it. Can you help me?

Answer: Send it to me, so I can spend more time for developing RHIDE. My Address is:
 
Robert H&ouml;hne
Am Berg 3
D-09573 Dittmannsdorf
Germany

Question: RHIDE does all sorts of unpredictable and silly things. I.e. does not remember the paths and other settings that I give it.

Answer: Did you start RHIDE with a project file i.e. invoke rhide with
 
rhide projfile
RHIDE needs a place to keep this information. Then go into projects tab and select add then follow the dialog to add the `.c' or `.cc' file to the project.

Question: I do not generate an `.exe' file.

Answer: Enter RHIDE from the dos prompt by
 
rhide projname
click project tab then add and select your `Hello.c' or `hello.cc' file. Then compile and then link or else build all. There should be a file `projname.exe'.

Question: The linker reports multiple int main() in my object file.

Answer: You have more than one `.c' or `.cc' file in your project with int main() and the linker does not know where to start the `.exe' file.

Question: It is not finding the include files `*.h'.

Answer: You are not referring to the djgpp distribution `*.h' files that are part of the DJGPP standard distribution. If so see DJGPP FAQ. In RHIDE click the Options tab on top of RHIDE window, then Directories, then Include, then add the path to the `dot.h' files in the text box as follows:
 
$(DJDIR)/contrib/grx/include $(DJDIR)/contrib/here/there etc
This path can also be set in the `djgpp.env' file (see the DJGPP information).

Question: It's still not finding the `dot.h' files.

Answer: Invoke Win95 long file names at the command line via
 
rhide -y projname

Question: How do I set rhide to long file names without -y each time?

Answer: Add the -y to your RHIDEOPT environment variable.

Question: The linker is not finding various library functions that are in an extension to DJGPP. For example functions that are part of SWORD Graphic User Interface or GRX. Graphic Package.

Answer: Click the Options tab then Libraries then mark one of the boxes and type in the Library name that you need i.e. grx for `libgrx.a'.

Question: It's still not finding the library functions.

Answer: Go into Options tab on top of the RHIDE window then Directories then Libraries, then add the path to the `libdot.a' files in the text box as follows:
 
$(DJDIR)/contrib/lib/here/there $(DJDIR)/contrib/grx/lib
This can also be set in the `djgpp.env' file (see the DJGPP information).

Question: Where is the rhide documentation and how do I read it?

Answer:Get the file txixxxb.zip and unzip it. Go into dir info and edit the file DIR. Add `rhide.inf' or any other `dot.inf' to DIR. Use the same format as the existing `dot.inf' files in DIR. It's obvious from the format how to do this. Save and exit from the edit session. Type "info" take the lesson on how to run info and you are fully equipped to run an old world non gui browser and are ready to learn all about gnu.

If you are using RHIDE, simply hit F1 and browse through the help, it IS the RHIDE documentation!

Question: The linker reports out of memory when linking many `*.o' files.

Answer: This should occour only on Windows 95 users (or W98). Give dos more memory. Quit rhide and dos. Select the dos icon or its alias (it's in `windows/start/programs') RIGHT click select properties then select memory tab then set Protected mode DPMI to maximum 65535 and have another go.

Question: I have a big svga monitor and rhide looks like cga screen. What can I do to take advantage of my monitor?

Answer:Set the dos and rhide screens to suite your taste. Quit rhide and dos. Select the dos icon or its alias (it's in `windows/start/programs') RIGHT click select properties then select screen tab then set the type of screen that you require in dos. Then get into RHIDE and select options tab on the top of the screen then Environment and then Preferences then set the type of screen to your liking.

Question: I`m running under W95/98 with long filenames and have some source files ond/or directory names with spaces in it. I get many errors when trying to compile or link. How can I solve this?

Answer: This is a limitation of RHIDE. Theortically it could be fixed, but this would need many changes in the RHIDE sources. I`m not willing to do. So, simply do not not filenames with spaces.

Question: How do I setup RHIDE to run under OS/2?

Answer: OS/2 (WARP3 and above) Users have to pay attention to the following DOS-Settings:
 
- DPMI_DOS_API must be set to "Enabled"
- DPMI_MEMORY_LIMIT should be set above 8MB (better >10)
- DOS_HIGH must be set to OFF
- DOS_UMB must be set to OFF
- DOS_FILES should be set fairly higher than 20 (>60)
- DOS_BREAK "ON" might be useful sometimes :-)
- MOUSE_EXCLUSIVE_ACCESS should be set to off
- You can use RHIDE with or without the "-M" option

Question: I think, I found a bug in RHIDE. How can I report it?

Answer:At first try for your own to solve the problem by checking the documentation.

If the bug is releated to the editor (some keys do not work, autoindenting is not like you expect, program crash after some special editing ...) please send them to salvador@inti.gov.ar, because he is the author of the in RHIDE integrated editor.

See at the RHIDE home page, if this problem was already reported by other users. As the next ask the problem in the news group news:comp.os.msdos.djgpp, because there may be some other people with the same problem, and they can give you an answer or I, because I read this group also.

GNU/Linux users should post the problems in the linux group. To make sure that I will read it also, please send a CC to me because my time doesn`t allow me to read that huge newsgroups.

If this don't help you, do the following:

Try to reproduce the error with the smallest possible project or source file. Run RHIDE with all debugging options enabled and redirect the printed output to a file see section 1.5.2 Debugging RHIDE. Send me this file and a detailed as possible description of the problem and include in your report the exact version of RHIDE you are using.

The exact version is shown in the About-Dialog and means the version number together with the build date.

And a last note. If I get bug reports or questions or problems with RHIDE which I think that they are of common interest be warned that I bounce them simply to the news groups because at this time it is impossible for me to answer all the mails I get. So the best is to post the questions and/or problems only in the news groups.


[ << ] [ >> ]           [Top] [Contents] [Index] [ ? ]

This document was generated by Robert Hoehne on February, 16 2003 using texi2html