Jump to content

EricBall

Members
  • Content Count

    2,361
  • Joined

  • Last visited

Blog Comments posted by EricBall


  1. Some suggestions

     

    master[MAXSIZE], working[WORKSIZE]; // declare as global or use malloc so they use the heap rather than the stack

     

    Replace for (i = 0; (a = fgetc(fp)) != EOF; i++) master = a; with fread

    Or, make the code line based & use fgets rather than trying to load the entire file into memory at once.

     

    All of those hexcode comparisons are ugly. Better to use the actual characters so you don't make errors remembering ASCII codes. You should probably also look at the ctype.h functions.

     

    Looks like you're doing a tokenizer. Wouldn't hurt to see if you could use strtok rather than brute forcing it yourself. (Although strtok isn't the easiest function to understand & use.)

     

    I'd also use pointers rather than array indexes - more efficient code.

     

    That all being said - sometimes being told you can't do something is enough to motivate you to prove them wrong. And there's nothing wrong with brute force code to get you over the initial challenges. But learn the libraries and leverage those functions - you don't have to re-invent the wheel (why write your own quick sort routine when qsort exists), there's less risk of introducing your own bugs and they are typically faster because the library can be in native code.


  2. Yeah. Before I junked my last 5 1/4 equipped tower PC I went through my stash of floppies and copied them to an external hard drive.

     

    Butt that was easy in comparison to recovering the files from a proprietary format backup CD. In that case I lucked out 'cause I still had the original software, the parallel port CD burner, and an old laptop which could support both.

     

    I also managed to do some backups using a laplink null-modem cable with a PC to PC copy program.


  3. Black is easy - the absence of light energy coming from an object. Of course, black might just be very little light energy, or the colors the object reflects aren't those being generated by the local light sources, or the colors aren't those which can be detected by the observer.

     

    White is much more difficult. For humans it's when the signals generated by the three adjacent "RGB" cones are high and relatively equal. Then our brains say "that's white".

     

    Black is primarily a function of light energy, white is primarily a function of the observer.


  4. I few years ago I went through my stash of (legal) PC software (games), seeing what would still run. Stuff which ran on DOS was basically no problem, and I'm sure a bit of fiddling with DOSBox would handle any exceptions. Anything which needed Windows 3.1 was a write-off, mostly because of stuff like Win-G and obsolete video codecs. Windows 9x software had a better chance of working, although some still had "wrong version" install issues.


  5. I know what you mean. But at the same time, sometimes playing a game stops being fun. So while I want to complete the game, I don't want to keep playing the game.

     

    However, I do remember completing several N64 games like Super Mario 64 (100%), both Zeldas, both Banjos and Diddy Kong Racing.


  6. It appears manufacturers are still making 3-D Blu-Ray players, although who knows for how much longer.

     

    Although it does make me wonder whether the lack of new 3D TVs will have a "trickle back" impact on the sales of 3D Blu-Ray discs, and from there on 3D films.

     

     

    The HDR standards increase both the dynamic range and the color gamut which, in theory, will make the resulting video more realistic (ignoring the differences between RGB and full spectrum).


  7. I agree with both of you on all points.

     

    IMHO 4K is only good when you sit really close to a really big TV - and when the signal isn't severely compressed. (Although 4K+ does make more sense on the production side.) And not only would I have to replace my perfectly good HDTV for 4K, but I'd need to replace my home theater amplifier (plus a source of 4K content).

     

    HDR is a nice bullet point on the box, but I doubt it will make many inroads beyond the console crowd.


  8. BBSs were also big for file sharing, especially in the 90s.

     

    I played around on BBSs quite a bit. In the 80s the BBSs were mostly single user. While you were connected other callers got busy signals. Mostly text based message boards - lowest common denominator as this was the time of 8 bit home computers.

     

    In the 90s I remember big multi-user BBSs. Lots of phone numbers to handle the different modem flavors. The BBSs were often interconnected with others (e.g. FidoNet). Some had lots of files with new ones evry day - this was the time of shareware and the PC dominated (although I'm sure there were Amiga and ST specific BBSs).

     

    There were also the big guys - CompuServe, Genie, Delphi, AOL.


  9. Yeah, I imagine any VoIP based phoneline (e.g. MagicJack) would trash modem audio. Modems were designed for analog copper connections and the the simple codecs used by old channel based telcos. The 56K modems actually required a digital connection from the BBS to the digital to analog converter at the caller's end.


  10. Cool video - I'll have to watch the whole thing later.

     

    I like the part about the kit bash library. Maybe the problem Eric mentioned was that they didn't use enough CG glue when putting everything together. ;)

     

    I agree, a very interesting video - thanks for linking to it.

     

    Now knowing how they probably created it, I don't think it was a texture / model issue (although I have to wonder why they didn't start with the 8 foot model, maybe it doesn't exist anymore...), more a paint & shadow problem I think. It was just too smooth and too perfect, maybe. Something to freeze frame when it comes out on Bluray.


  11. Saw it in IMAX 3D yeterday. I think part of the problem with 3D movies (especially those not shot in 3D) is the dichotomy between depth of focus and 3D depth. This really (really) stood out in the hanger scene with Cassian being in focus and "in front" of the out-of-focus volunteers. But then the camera changes focus for just a moment to put the crowd in focus, and Cassian out of focus. Ugh

     

    Nathan, do you know how they created the CGI models of the Star Destroyers? For some reason they sometimes looked to me like they were made from LEGO.

     

    My only problem with the movie is it's a one-shot. While it does a great job filling in the backstory for a couple of lines in A New Hope, I'm not sure there's a lot of other similar opportunities in the movie canon.


  12. Finally got to see it yesterday - in IMAX 3D

     

    I think Leia worked much better than Tarkin because of time, little / no dialog, and scale. The more Tarkin filled the screen, the less "life like" he looked.

     

    But on the CGI front, I found the Star Destroyers looked like they were made of LEGO.

     

    Re R2D2 and C3PO while a cool cameo, it begs the question - shouldn't they have been on the blockade runner?

     

    I agree it was a fine movie.


  13. Hi Darrell,

     

    Maybe, but the input is from an attachment (with a kvp extension) which is marked as application/octet-stream. I haven't tried to access and decode the raw SMTP, but I that should keep it as a binary file from iOS to my Download directory. The actual contents are utf8 text, and I've successfully passed Chinese, Hebrew and Arabic characters and even emoji. It's just the EOL which is being changed. Not a big deal, just annoying.

     

    <Edit>

    Just downloaded and checked the file on my work laptop (Windows) and it's only LF. So it's either MacOS or the String from file initializer (bets on the latter).


  14. I've loaded the alpha code on my boss's and two coworker's phones, in addition to my son's and wife's iPods. Everyone is very impressed. (Although I think with the idea that I've created an actual iOS game rather than being impressed with the game itself.)

     

    The transition to Swift 2.3 was relatively painless (although I still don't know how to create a Swift 2.3 project in XCode 8 - but if I need to I can create one in XCode 7). Renaming the project from the development name to the actual name was less than painless (the XCode "rename" only does one step of many), but I found a step-by-step YouTube video. Hooray for the Internet.

     

    My current challenge is putting together the screen which will list all of the levels you have created. While XCode & UIKit have the basic framework (UITableView) - there's a lot of "write from scratch" instead of "tweak to suit". I've also had to write a bunch of sqlite interface code to handle the actual data. While there are some free toolkits out there, I wasn't able to get the nicest one to install correctly. I'm also leery of making my code dependent on someone else's (other than Apple's - which I can't avoid). And even the sqlite code isn't that bad with some help from a StackExchange post.

×
×
  • Create New...