798 replies to this topic

[Konlab]

Event system is gone? I saw the sourcecode on the pacman youtube video (Im pro in pausing videos at the right moment) + the sfx editors WOW

[Creator]

The event system is not gone.

[MKlegoman357]

The event system isn't gone. But, (I think) you can now do:

local event, b = os.pullEvent("key", "char")

For specific events only. Also, there's 'keyboard' API there's a keyboard device:

local keyboard = device.get("keyboard")

...

if keyboard.getKey(keys.up) then
  -- go up
elseif keyboard.getKey(keys.down) then
  -- go down
elseif ...

Edited by MKlegoman357, 13 October 2015 - 03:23 PM.

[Creator]

The second way is actually better in my opinion.

Also, will we have the same fs api?

[MKlegoman357]

There's 'lua.unserialize()' now, probably instead of textutils API. Also, there's a 'device' API which works similarly to the peripheral API, but instead you get more of the hardware stuff, like:

local gpu = device.get("gpu")
local keyboard = device.get("keyboard")
local speaker = device.get("speaker")

gpu has different functions for maps and images and it can (or must) draw to an image:

gpu.setTarget(window.getImage())

Looks like the 'window' API has replaced the 'term' API.

local screenWidth, screenHeight = window.getSize()

window.setFullscreen(true/false) --# (?) hides/shows the top bar (multishell tabs)

Speaker (unconfirmed documentation):

speaker.play(parameters : table, channel : number)

parameters = {
  volume : number;
  attack : number;
  sustain : number;
  decay : number;
  frequency : number;
  frequencySlide : number;
  frequencyAccel/frequencyAcceleration : number;
  vibratoDepth : number;
  vibratoFrequency : number;
}

The speaker probably has different set of channels and you can only play one sound on one channel at a time, but this is only speculation.

More info might be coming later..

Creator, on 13 October 2015 - 03:28 PM, said:

Also, will we have the same fs api?

Probably, but it will use the more Lua OOP standard way:

CraftOS 2.0:
file:close()

CraftOS 1.x:
file.close()

[MKlegoman357]

Then there's color mapping, which might be the "pallet" thing Dan was showing us before. You can do:

gpu.setColorMapping(colors.white, colors.blue)

And it will probably (?) make so that when you write the color white it will be displayed as blue. Also, you can reset the color right after you draw the changes:

gpu.resetColorMapping(colors.white)

There's also text writing capabilities:

gpu.drawText(x : number, y : number, text : string)

...

gpu.drawText(0, 0, "Hello World!")

--# writes 'Hello World!' on the top-left corner of the screen.

You can also set a global image offset:

gpu.setOffset(offsetX : number, offsetY : number)

which will simply "move" the resulting image by as much as you specify. Default is x=0 and y=0, which is "no offset".

[Lyqyd]

If Dan doesn't create a new forums for it elsewhere (which is possible, of course), I'd imagine a separate category would be used (like the category for the site discussion sections at the bottom), as the new game would benefit from having its own bugs, suggestions, and program sections. This is speculation, I haven't heard anything more than you guys have.

[oeed]

MKlegoman357, on 13 October 2015 - 03:52 PM, said:

-snip-

Did you see what the pixel drawing functions, as in those to draw induvidual pixels over text, were?

[Bomb Bloke]

MKlegoman357, on 13 October 2015 - 03:36 PM, said:

Creator, on 13 October 2015 - 03:28 PM, said:

Also, will we have the same fs api?

Probably, but it will use the more Lua OOP standard way:

CraftOS 2.0:
file:close()

CraftOS 1.x:
file.close()

Not sure I can see the point of having fs.open()'s handles work like that, given that they'd then be the same as io.open()'s handles.

MKlegoman357, on 13 October 2015 - 03:52 PM, said:

Then there's color mapping, which might be the "pallet" thing Dan was showing us before. You can do:

gpu.setColorMapping(colors.white, colors.blue)

And it will probably (?) make so that when you write the color white it will be displayed as blue. Also, you can reset the color right after you draw the changes:

gpu.resetColorMapping(colors.white)

Assuming it is related to Dan's palette-altering video, you probably wouldn't want to reset "right after": doing so would revert pixels already on-screen, removing the point of remapping in the first place.

(If you don't get what I mean, watch the lower left corner of the video while he tweaks the sliders.)

[MKlegoman357]

Bomb Bloke, on 14 October 2015 - 01:31 AM, said:

Assuming it is related to Dan's palette-altering video, you probably wouldn't want to reset "right after": doing so would revert pixels already on-screen, removing the point of remapping in the first place.

(If you don't get what I mean, watch the lower left corner of the video while he tweaks the sliders.)

That's the interestig part. The functions I showed were called almost at the same time. The colors were remapped, text was drawn and the colors were reset right after.

[Bomb Bloke]

I wonder if he's using it like we use term.setTextColour() now?

[Waitdev_]

hmm... pixels are 8x8 (pretty sure), and we need to get prepared.
let's center something.

txt = "Hello World!"
w,h = window.getSize() --or term?
window.setCursorPos((w/2)-((#txt*8)/2))
write(txt)

shouldn't be that hard...

[Waitdev_]

speaking of text, i noticed this.
https://twitter.com/...071645708120065

@DanTwoHundread, on 14 October 2015 - 09:49 AM, said:

Tips for writing Unicode-aware Lua code: Lua does not have a string type, it has an "array of bytes" type called "string".

unicode fonts confirmed.

[Creator]

Wait_, on 14 October 2015 - 09:53 AM, said:

speaking of text, i noticed this.
https://twitter.com/...071645708120065

@DanTwoHundread, on 14 October 2015 - 09:49 AM, said:

Tips for writing Unicode-aware Lua code: Lua does not have a string type, it has an "array of bytes" type called "string".

unicode fonts confirmed.

Finally I can write texts in Bulgarian. That will be so useful with the large Bulgarian audience on the forums.

[LeDark Lua]

Wait_, on 14 October 2015 - 05:43 AM, said:

hmm... pixels are 8x8 (pretty sure), and we need to get prepared.
let's center something.

txt = "Hello World!"
w,h = window.getSize() --or term?
window.setCursorPos((w/2)-((#txt*8)/2))
write(txt)

shouldn't be that hard...

*ehm* Wait_, if Dan added like: font.getWidth() or graphics.getFontWidth() or someting then there could be font scaling.

EDIT: and we could get the size of the font easily.

Edited by LeDark Lua, 14 October 2015 - 12:49 PM.

[CraftedCart]

Hex Editors?
https://twitter.com/...370715660099588



Also zoom buttons (or tab management) in the top right?

So what would hex editors be used for?

Edited by CraftedCart, 14 October 2015 - 07:19 PM.

[H4X0RZ]

CraftedCart, on 14 October 2015 - 07:18 PM, said:

Hex Editors?
https://twitter.com/...370715660099588



Also zoom buttons in the top right?

So what would hex editors be used for?

Hopefully this also means that the binary bug has been fixed.

[MKlegoman357]

Here's what it says in the hex editor:

image format=1 width=13 height=12
      2      
      2      
    22222    
   2ff2ff2   
  2fffffff2  
2 2ff0f0ff2 2
2222fffff2222
2222222222222
2 21ff7ff12 2
  22ff7ff22  
 2 2ff7ff2 2 
    22222    

EDIT: here's what it produces with paintutils in CC 1.74:

Edited by MKlegoman357, 14 October 2015 - 07:34 PM.

[oeed]

Not as good, although very understandable news:

"Ok, focus for the time being is back to @redirectiongame. Finances are such that I can't have two projects in development limbo at a time!"

[CaosTECH]

Whats that supposed to be? From the code it looked like a spaceship, but now it just looks plain creepy

oeed, on 14 October 2015 - 08:42 PM, said:

Not as good, although very understandable news:

"Ok, focus for the time being is back to @redirectiongame. Finances are such that I can't have two projects in development limbo at a time!"

I have been waiting to ask this question... why does redirection cost money? If we can play it for free on CC?

Edited by ArchTyler, 14 October 2015 - 08:54 PM.