349 replies to this topic

[CascadingDragon]

theoriginalbit, on 04 September 2013 - 04:31 PM, said:

Fair enough, as I said it wasn't a problem in your code, I was just curious with that one. And wow thanks for actually reading my documentation! So many people don't, and so many people don't appreciate or understand the time I put into those to make them useful.

But... if you don't read documentation... how do you know if you are doing it right? Common sense must be worth a fortune by now.

theoriginalbit, on 04 September 2013 - 04:31 PM, said:

I am considering changing it now slightly in a version 3.0, we shall see what I end up with. Also if you wish to continue programming in Minecraft, look up LuaIDE on these forums, it's made by GravityScore and it really does make in-game editing nice, however if you have access to the Minecraft world data, definitely external editing with Sublime Text 2 and GravityScore's ComputerCraft plugin (also on the forums, search "sublime" in the utilities section) for it is very nice.

Playing on a server, I can't use Sublime, but LuaIDE looks nice. Thanks for the heads up!

[theoriginalbit]

CascadingDragon, on 04 September 2013 - 04:36 PM, said:

But... if you don't read documentation... how do you know if you are doing it right? Common sense must be worth a fortune by now.

I don't know, but someone once asked me a question about an API and my response was literally "did you even read the developer documentation?!" and their response was "there is documentation"... The link was directly above the DL link :/

[theoriginalbit]

bumping to notify of a BIG bugfix in the custom read function.

* Fixed bug with empty history tables being supplied causing crash
* Fixed bug with cursor being off the screen AFTER enter is pressed and causing first line printed to be missing

Also
+ Added ability to tell read to use pullEventRaw instead of pullEvent

Download link is the same, find it in OP @ Useful Code Snippets —> Custom Read —> Download

[theoriginalbit]

New! ccConfig v2.1

* New colour parser. The valid input of colours is now endless!

Thank you so much to LBPHacker for making this colour parser work so much better!

See OP for download link and developer documentation.

[theoriginalbit]

Major OP cleanup performed...

Should be easier to find my programs.

Also updated information on a few programs that I found were outdated.

[theoriginalbit]

New code snippet. "Peripheral search". Using this in a project with NeverCast, and its just too good not to share. See the OP for more details.

Edited by theoriginalbit, 15 November 2013 - 08:29 AM.

[theoriginalbit]

New code snippet. "Dynamic Function Invocation on Lua Objects". Made by Symmetryc and improved by myself, decided to share this as well as it is very useful. See OP for more details.

[Marikc0]

Does the turtle excavating program still work? I came back a short time later to find the turtles stopped with the ender chests a few blocks nearby each turtle.

[theoriginalbit]

Marikc0, on 22 November 2013 - 03:51 AM, said:

Does the turtle excavating program still work? I came back a short time later to find the turtles stopped with the ender chests a few blocks nearby each turtle.

Currently no, it works, and is more fuel efficient, but sadly there is the enderchest bug What I thought was an edge case seems to be occurring more often and honestly I forgot to fix it when I was told about it months ago. I'll have to fix it after my last exam for uni in 4 days.

Edited by theoriginalbit, 22 November 2013 - 04:25 AM.

[theoriginalbit]

Edited the custom read function to make use of the upcoming paste event, anyone using the pre-release let me know if you come across any bugs.

EDIT: Oh also, finally got a new web host, website is up, content will be not far off (link in my signature)

Edited by theoriginalbit, 04 February 2014 - 07:40 AM.

[theoriginalbit]

after helping surferpup quite a lot in Ask a Pro I've gone and updated the Coroutine-Management-System (CMS), its now smaller and less buggy (let me know if you do find any), see OP for download links.

[theoriginalbit]

New! ccConfig v3.0!

* Better colour parser (again). Less loops! Same value support;
* Minor efficiency improvements;
+ Config Objects are now better¹;

¹ Now uses my 'Dynamic Invocation on Lua Objects' snippet, meaning that the following function calling is supported: config.getString("foo"); or config.getString(config, "foo"); or config:getString("foo");

...more to come...

See OP for download link and developer documentation.

[TheOddByte]

Nice that you added that to the ccConfig API!
I have a small suggestion for your read function, The ability to write text when the text length is equal to zero, Kinda like in search bars if you know what I mean

[theoriginalbit]

Hellkid98, on 18 March 2014 - 04:26 PM, said:

I have a small suggestion for your read function, The ability to write text when the text length is equal to zero, Kinda like in search bars if you know what I mean

hmmm I have considered implementing placeholder text, the only problem I foresee with this is the obvious lack of a user being able to distinguish it when not on an advanced computer

[TheOddByte]

theoriginalbit, on 18 March 2014 - 11:34 PM, said:

hmmm I have considered implementing placeholder text, the only problem I foresee with this is the obvious lack of a user being able to distinguish it when not on an advanced computer

Hmm? How do you mean? And I hate it when I can't find the right words.. ( I'm talking about the word(s) placeholder text )
I created some code just to test to do this myself

This is result

Screenies


FYI, Advanced computers to the left & regular to the right

Code

local mRead = function( _color, _placeholder, _placeholder_color )
	local text, _x, _y = "", term.getCursorPos()
x, y = _x, _y

local function redraw( _num )
		if #text > 0 then
   local num = _num or 1
   term.setCursorPos( _x, _y )
			for i = 1, #text+num do
				term.write( " " )
			end
			term.setCursorPos( _x, _y )
pcall( term.setTextColor, _color )
			term.write( text )
			term.setCursorPos( x, y )
		else
			term.setCursorPos( _x, _y )
pcall( term.setTextColor, _placeholder_color )
			term.write( _placeholder )
			term.setCursorPos( _x, _y )
		end
end

	term.setCursorBlink( true )
	while true do
   redraw()
		local e = { os.pullEvent() }
		if e[1] == "char" then
   if #text == 0 then
   term.setCursorPos( _x, _y )
   for i = 1,#_placeholder do
   term.write( " " )
end
term.setCursorPos( _x, _y )
end
			text = text .. e[2]
x = x + 1
		elseif e[1] == "key" then

			if e[2] == 14 then
   if #text > 0 then
					text = text:sub( 1, #text - 1 )
   redraw( 2 )
   x = x - 1
end

			elseif e[2] == 28 then
				term.setCursorBlink( false )
				return text
			end
		end
	end
end

term.clear()
term.setCursorPos( 1, 1 )
term.write(" > " )
local inp = mRead( colors.white, "Search", colors.lightGray )
print("\nReturned: " .. inp )

This is just some shitty code I threw up, But it works for a simple example
I'm wondering what you mean with the user not being able to distinguish it when not on an advanced computer

Edited by Hellkid98, 19 March 2014 - 03:44 PM.

[theoriginalbit]

Hellkid98, on 19 March 2014 - 03:39 PM, said:

-snip-

What I mean is that the user may struggle to distinguish between real text and placeholder text when on a Normal computer... when on an advanced computer you can grey out the text, but that's not the case on a normal computer.

[Blue]

I love CCpresenter actually its one of my most favorite programs

[theoriginalbit]

Glass Systems, on 18 April 2014 - 03:46 PM, said:

I love CCpresenter actually its one of my most favorite programs

thanks, I'm glad that you like it, wasn't too sure if anyone really used it.

[koslas]

I am using the code you told me to use, and if someone presses an arrow key, it crashes saying
startup:155: attempt to get length of nil
Line 155 is of my program, is this line in your read function
elseif historyPos == #_history then

Edited by koslas, 20 August 2014 - 03:12 PM.

[theoriginalbit]

uh, are you sure you've not edited my code? the statement

elseif _history and code == keys.up or code == keys.down then

would prevent it from ever getting to the line you're saying is erroring.