-
I was wondering if someone could tell me how I can use Curses in my own ASCII game programming. I assume that I can somehow use curses.dll as I'd like to use Studio .Net if i can to develop but any hints or tips to somehow find somewhere to download Curses and get it running on any compiler are appreciated.
Thanks.
-
You'll need a header file and a library file to write Curses programs. You can find PDCurses all over the internet.
You can try this:
PDCurses
although it isn't the exact same as the one I use. I'm having trouble finding the link. I still have the zip file (for Visual Studio) if you want it.
There seem to be lots of implementations.
Curses Help Files (Look in Chapter 2)
There are a number of tutorials around. If you have any specific questions once you get started with these files, let me know.
-
I've downloaded PDCurses before but couldn't get it to work right with Visual Studio. Always willing to get another shot though if you've got some trick as to how I can get the compiler to recognize the curses.h file and the plethora of functions contained within.
-
You need to use the curses library. Even with the DLL, it seems to need the regular library file too. Here is the zip file that I use:
Curses
The layout is more straight-forward than other versions I've seen on the net. Just include "curses.h" and link "curses.lib" with your Visual Studio project. Then it should recognize curses functions.
Be warned that "curses.h" has a ton of badly named macros in it, so names that you might want to use yourself (such as clear() and erase()) are already reserved. I've taken to commenting out things in curses.h that I don't want.
Let me know if it works. I used Visual Studio 6 for the games in the Curses Arcade, so I should be able to get you through to a compiled program.
[ March 15, 2003: Message edited by: Toady One ]
-
Sorry to not reply for awhile, been kinda preoccupied.
Here's a stupid question:
How exactly do I go about linking curses.lib with my Visual Studio project?
-
There are a couple of ways that should work.
One is to add the file to the work space that's on the left (where your source files are). You right click where it says "<name> files" and select "Add Files to Project". Or you can go up to PROJECT:Add to Project:Files and put curses.lib in there.
So in my Workspace "Liberal Crime Squad"
I have game.cpp, curses.h, and curses.lib
under the Fileview tab.
The other way is to go into (in MSVC6, anyway) the menu at the top
PROJECT:SETTINGS (or Alt + F7).
Then select the tab "Link" on the right.
There should be a field called
Object/Library modules. Just
type in curses.lib there, assuming
you've stuck the lib file in your
MSVC lib directory (or in the main
directory with your source might work
too). If you have both debug and release modes for your project, you'll want to make sure you Link it into both if you use this method.
-
Ok thanks, got things to compile. Now just have to go do some reading on how to use it all!
-
I am just posting this to make sure that the tripe lpbs remains.
lbps: Last Post By Spelguru
Have fun all!
-
How do you do the real time input for most of the curses games you made?? I know of only getch() and cin and both of those delay for a keystroke.
-
Are you ever going to release the source code to any of your games? I'd like to look through BCoS to learn a little...
-
The forum dosnt seem to realise I'm posting, so I'm trying again...
-
Bumping a thread from 2003. Lol.
-
Why?
-
Because.
-
Hey, a decade old forum necro isn't too shabby
-
I was very polite and indifferent when you bumped the National LCS thread because it was relevant to an ongoing discussion and I wanted to assume your one word bump was well-intentioned. But don't make a habit of this sort of thing.
I'm a big softie when it comes to thread necromancy. People bump threads about various other games, or otherwise seek to revive a years-old discussion, and I don't blink twice. But bumping ten year old threads just because you can... mmm. It's cute once, but it's going to get old fast. Everyone else needs to use the forum too; please don't make it harder for them to find current content.