Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Do you plan on including any basic drawing functionality? We're just talking simple colored lines, or maybe an ellipse function. (For drawing UI borders and such.)Not sure. Such "classic" drawing primitives do not combine well with cells/characters architecture. The library does not draw tiles the moment you issue 'put' or 'print' command but constructs a 'scene description' for later render. This allows more 'terminal'-way operation where you can replace some of the characters while leaving everything else intact. This also allows library to redraw the scene all by itself if necessary. Lines and circles are rather foreign to characters-based modifiable scene structure, and I do not see a way to make a clear API with those.
When using composition to stack tiles on the same location on the same layer, is there any way to make a copy of the composed tile and save it off as a temporary (or even permanent) tile that can be reused, or would I always need to rebuild (recompose) the tile each move?Right now the only option is to reconstruct them every time. Given the scene architecture it is not as straightforward as copying pixels, but I think its possible to allow to save an output string (which usually goes to 'print' and supports combining via formatting) as a precomputed template, e. g. like this:
terminal_set("0xE100: 'a[+][color=red]/'");
terminal_put(2, 1, 0xE100);Though it will take a decent amount of coding =).Similar to question 2, is there a function to simply copy an area of the screen and paste it somewhere else? (It wouldn't need to retain all the layers; purely just a pixel copy of a designated space, placed into it's own layer in a different spot.)As I mentioned above, pixel copy is almost impossible and layers do make a problem. However, it indeed may be a useful feature, will think about it. What do you intend to use it for exactly?
Did you use "wine start testprog" or "wineconsole testprog" or something else?Whoa. As I rarely use Wine, I did not even know about wineconsole. Indeed, after running the snippet application this way, it behaves more like under native Windows and WaitForSingleObject does not hang now. Though output still differs from that under Windows. Wine 1.4 under Ubuntu 12.04:
11-00-08
41-01-08
41-01-08
11-00-00
11-00-00Shift down, A down, A up, Shift up | but Shift down, A down, Shift up, A up
10-00-10 | 10-00-10
41-41-10 | 41-41-10
41-41-10 | 10-41-00
10-00-00 | 10-00-00
10-00-00 | 41-00-00Where I honestly see only chaos.12-00-02
41-61-02
41-61-02
12-00-00
12-00-00The alternative libraries don't seem to have current D wrappers.I specifically designed BearLibTerminal's API to simplify wrapping for another languages. If you are interested in this pseudoterminal output approach, I'll make a wrapper for D. Also, BearLibTerminal works fine under Wine (well, at least where I was able to test it).
Get curses <...>I do not really understand this pure terminal way. It's harder to set up properly. In its extreme it requires networking for no real game purpose. In the end it just shifts the drawing responsibility from external library to external application. And even while using external tools for output it still severely restricts output functionality. Telnet games are cool in their own way but they are harder both ways, requiring more effort from both programmer and player.
Combination | Wine | Windows
-------------+-----------+---------
A | 41-61-00 | 41-61-00
| 41-61-00 | 41-61-00
-------------+-----------+---------
Ctrl+A | 11-00-08 | 11-00-08
| 00-01-08 | 41-01-08
| 00-01-08 | 41-01-08
| 11-00-00 | 11-00-00
-------------+-----------+---------
Shift+A | 10-00-10 | 10-00-10
| 141-41-10 | 41-41-10
| 141-41-10 | 41-41-10
| 10-00-00 | 10-00-00
-------------+-----------+---------
Ctrl+Shift+A | 11-00-08 | 11-00-08
| 00-01-08 | 10-00-18
| 00-01-08 | 41-01-18
| 11-00-00 | 41-01-18
| | 10-00-08
| | 11-00-00
-------------+-----------+---------
Alt+A | 1B-1B-00 | 12-00-02
| 1B-1B-00 | 41-61-02
| 41-61-00 | 41-00-02
| 41-61-00 | 12-00-00Dunno what all these numbers are good for but once you started collecting data it's hard to stop.However it's a major rewrite to use it instead of libtcod as libtcod handles all the fovs also.Well, it is only natural for such a rewrite (if any) to be postponed until the right time. However, now the cumulative potential of tools available to you should be somewhat higher =). As for libtcod's fovs, it is BSD licensed and therefore allows extracting parts of the library. It could be something like BearLibTerminal.dll + libtcod-fov.dll.
T.print_(40, 12, "[align=bottom-right]Spike Vixen\nGrease Monk")
T.print_(40, 12, "[bbox=30x10]Void Initiate: gain 1 rune. "
"You may banish a card in your hand or "
"discard pile.") 
int height = terminal_measuref(L“[bbox=%d]%ls”, width, ws.c_str());terminal_print(“One [font=0xE000]Two”);
T.print_(2, 1, "This spell requires: 2[0xE004] 3[0xE022]")
T.print_(2, 3, "The scroll says \"[font=0xE100]whatewer[/font]\"")
import PyBearLibTerminal as T
T.open()
T.print_(2, 1, “Hello, wordl”)
while True:
T.refresh()
key = T.read()
if key == T.TK_CLOSE or key == T.TK_ESCAPE:
break
T.close()My quoted argument still holds.Well, if taken literally the statement is undeniably true right now, my bad. However, the initial question was whether is it safe to look at the source code or not.
The jury similarly found that Google did not infringe on English-language comments in CodeSourceTest.java and CollectionCertStoreParameters Test.java or source code in seven "Impl.java" files. However, it agreed that Google did infringe on the rangeCheck method in TimSort.java and ComparableTimSort.Java.Here is the code of rangeCheck:
/**
* Checks that {@code fromIndex} and {@code toIndex} are in
* the range and throws an appropriate exception, if they aren't.
*/
private static void rangeCheck(int length, int fromIndex, int toIndex) {
if (fromIndex > toIndex) {
throw new IllegalArgumentException(
"fromIndex(" + fromIndex + ") > toIndex(" + toIndex + ")");
}
if (fromIndex < 0) {
throw new ArrayIndexOutOfBoundsException(fromIndex);
}
if (toIndex > length) {
throw new ArrayIndexOutOfBoundsException(toIndex);
}
}Google might have copied thousands of lines but in the end the war was fought over individual pieces a dozen of lines in length. If you look at some source code you are more likely to write a similar one. With modules as small and trivial as rangeCheck or modules demonstrating some clever trick you might end up writing the same (or very similar) code unintentionally.Nothing in 1452 years of copyright case law leads me to believe that any of the following logically equivalent cases are true <...> A programmer violates copyright if they read any copyrighted source code and then solve the same problem in their own works.False statement. Oracle vs. Google case has shown one indeed can be attacked because of the code that simply looks copied. This time it ended good. However, it did happen once and monstrous Google being on the receiving end must have contributed greatly to the result.
When trying out small code snippets It's often easier to type a single command line with few compiler switches than click your mouse to death setting up a new project in an IDE.Quote from: KirbypoweredWhat would I be missing?Common sense of not using IDE while it's easier than command line.
What would I be missing?You missed to mention the library: -lBearLibTerminal. The -I and -L switches are only telling where to look, not what to look for.Code: [Select]g++ bearlibtest.cpp -o bearlibtest -Iinclude -Llib
I can't find any way to get the pitch which is needed to read the texture pixels.A brief peek into SDL2 sources revealed that this pitch parameter tells SDL the width of a single line in your buffer, in bytes. SDL copies the data to your buffer line-by-line, incrementing the pointer by that value.