![]() I just thought I’d point that out as your own coding in the same area may be useful to me too. (As it does not reflect my own system correctly.) There are also some “blank lines” that could do with being altered, but it’s a minor point I suppose. Remove the CR info permanently rather than simply mask it. It’s great to see others working on this kind of thing.Īnd the dragon AI is looking very cool … or not (due to fire)? I would definitely be able to put that to use somewhere, even if it is not until module 3 … or unless you give access earlier.ĮDIT: To avoid traumatization, I made the assumption that the rabbit burrowed away to live for another day.ĮDIT 2: As an aside, I am trying to “tidy” the Examine GUI some more, as it has some elements that I do not need, and at my last messing with it, I still had not managed to alter it to how I wanted it. What do they represent/do? It’s certainly something that piqued my interest. So, it’s an area I let “sit”, but this video has made me want to look at it again.Īlso, I note you have some interesting looking icons in the top bar, where I currently have the RANGE section of my code. EDIT: Currently, adding text using it messes with my “mask” to obscure the OC CR info, which I need to do. What you have done seems like a good way of using it. ![]() For instance, I notice you have used pre-examine text (what I have named PRE_DESCRIPTION_TEXT in my GUI code), which I have in place but have not yet implemented in any way. Great stuff!Īs you know, I have been working on some Examine GUI stuff, and I don’t want to “reinvent the wheel” if you have already done a lot of work. Oooooh … You knew this would grab my attention.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |