The engine by default owns few layers which includes the GUI Layer. The GUI Layer creates the necessary initialization and specifications required for having a working GUI system setup!

Since, the GUI layer is guaranteed to be the first created layer in layer stack (so far the Application creates it), it should also be the first updated layer (basically any layer created by the engine itself, should be updated earlier than the other layers).

auto& gameLayer = new GameLayer(...);
auto& gameXXXLayer = new GameXXXLayer(...);

hyp::Application app(...); // the GUI Layer had been created and added internally
app.pushLayer(gameLayer);
app.pushLayer(gameXXXLayer);

Since the layer stack is updated this way:

gameXXXLayer.update(...);
gameLayer.update(...);
//guiLayer.update(...);

Technically this is right, as it's doing what a stack does best! But logically the GUI Layer supersedes the other layers (and more layers could also exists in this manner), and should be updated first.

It's this issue of being updated last, that makes the editor-layer event blocking wrong!

Script Reference

Hyper is still a work-in-progress engine at this time. The scripting system is in its alpha stage, and changes might happen without order; however, this guide remains viable for the scripting basics of the engine.

To attach a script to an entity, create a .lua

-- Player.lua
local Player = {}

return Player

The script must return a table. It is used to access other parts of the system. A script file has three primary methods.

-- called once, when the script was loaded
function Player:init()
end

-- called for every frame
function Player:update(dt)
end

-- called when the scene ends
function Player:destroy()
end

the init and destroy methods can be omitted, but the update method is required and compulsory; In other words, there should be no script file if there's no update method.

How to interact with the entity's component

Each script is attached to an entity, as a component. An entity can have many elements, and by default has an ID, tag and transform component. Presumably, these components are always existing for an entity.

Here's how we can interact with components from the script:

function Player:init()
  self.velocity = 10
  transform = self.owner:get(self.id(), Transform)
  print(transform.position)
  print(transform.scale)
  print(transform.rotation)
end

function Player:update(dt)
  transform = self.owner:get(self.id(), Transform)
  transform.position.x = transform.position.x + self.velocity * dt -- continue moving to the right
end

self.owner: The S in ECS. It's an interface to the scene's registry where entities and their components are managed. It provides methods such as has, get, valid, remove, clear and emplace. These methods take two parameters, an entity ID, and the component type.
self.id: The script's entity ID.

Available Components:

• IDComponent
• TagComponent
• Transform
• SpriteComponent
• CircleComponent
• TextComponent

reference /hyper/src/scene/components.hpp to see the component structures

when I was trying to render this text: "Hello\tWorld", the "World" was not rendered, just the "Hello" part.

seems like is not supported

This should reproduce the bug:

// equivalent to nullptr
hyp::Ref<hyp::Texture2D> texture;

hyp::Renderer2D::drawQuad(transform, texture, 1.f, glm::vec4(1.0));

Potential reason:
The renderer is not checking if the passed texture is empty or not. crashes because it was trying to bind to an invalid texture, (opengl's side)

          Hyper hasn't been tested on other platforms. But, the goal is for the engine not to be platform-specific. To achieve this, we use libraries/packages that are not platform-specific. Development is actively happening on Windows, and the application is not expected to run on other platforms successfully.

Originally posted by @coderoyalty in #23 (comment)

File dialogs are only available for windows.

It'll be cumbersome to write codes for all platforms... best to use a package that already abstracts this..

class GameLayer: public Layer {
 ...
}

//... in layer::onUpdate method
{
  std::cout << dt << std::endl;
}

output (may vary):

1854532.50
//...

every other value looks great for a delta-time

This was marked as a TODO flag in the renderer code, but it'll be great to have it as an issue (so we don't forget)