@@ -4,13 +4,11 @@ There will be bugs. This is simply too large of a library for me to test every
4
4
If you have any trouble, or think that something should be fixed, create a bug report and I'll get right on it.
5
5
6
6
WARNINGS:
7
- ACS vars currently break from the norm, I'm looking into int , but I'm not sure if It can
7
+ ACS vars currently break from the norm, I'm looking into it , but I'm not sure if It can
8
8
be done exactly the same that C does it.
9
- instead of writing "addch(ACS_ULCORNER);", Instead write "addch(acs_map[ACS.ULCORNER]);".
10
-
11
- The problem lies with the fact that I'm not sure how to recreate the preprocessor commands.
12
- It's definitely possible, but It might not be possible at compile time. It might
13
- require highjacking the init() function in order to set it up.
9
+ ////instead of writing "addch(ACS_ULCORNER);", Instead write "addch(acs_map[ACS.ULCORNER]);". fixed
10
+ Instead of writing "addch(ACS_ULCORNER);", Instead write "addch(ACS_ULCORNER());"
11
+ I think that this is as close as we are going to get without digging through the source to extract what acs_map[] really is.
14
12
15
13
This should work for most of your needs, however there are still one or two more things that need to be done.
16
14
I plan on having those completed in the next few days.
@@ -22,4 +20,4 @@ WARNINGS:
22
20
I simply need more eyes on this to bug check and ensure that things are working properly.
23
21
24
22
If you are familiar with the FREE acronym(Functional, Reliable, Elegant, Efficient) I would say we are an F.
25
- I doubt we can get any farther than FR, but let's go for it!
23
+ I doubt we can get any farther than FR, but let's go for it!
0 commit comments