From: "Alexei A. Frounze" Newsgroups: comp.os.msdos.djgpp Subject: Re: Advantages/Disadvantages of RHIDE Date: Sun, 4 Mar 2001 14:25:09 -0500 Lines: 31 Message-ID: <97u4oc$psk37$1@ID-57378.news.dfncis.de> References: <3AA2763B DOT 96DA12BF AT home DOT com> NNTP-Posting-Host: nas-204-244.rochester.navipath.net (64.20.204.244) X-Trace: fu-berlin.de 983733837 27152487 64.20.204.244 (16 [57378]) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Paul Michailidis" wrote in message news:3AA2763B DOT 96DA12BF AT home DOT com... > Just as the subject states? Is there any downfalls to rhide? I > personally like the gui cause it resembles the borland compiler gui I > used to work with. I actually have the same problem as "xavier", it says > "allegro.h": no such file or directory and i included "alleg" in the > check box as well. Apparantly I now have to create some batch files > before running rhide to ensure rhide works correctly. If I didn't use > rhide and used command line compilation instead,would I need to do all > that extra stuff? RHIDE simplifies life greatly. But one should get a rid of all problems with it first. Like RHIDE creates some stuff in the temporary directory and doesn't delete it, has some problems with mouse and video modes. But there are simple ways to fix those problems manually (like batch files that delete RHIDE-produced junk, add a switch to set up mouse proper support, probably use 80x25 in a window and never let it expand or something (e.g. set up a PIF file)... Moreover, it's easy to debug programs in the IDE. As for Allegro, one must compile it first. Good Luck -- Alexei A. Frounze alexfru [AT] chat [DOT] ru http://alexfru.chat.ru http://members.xoom.com/alexfru/ http://welcome.to/pmode/