chroma-2d / chroma Goto Github PK

nice if it's compatible with love2d image font format

i mean how do you UI without allowing custom cursors

probably related to owner handle being null at the time of windowproperties creation

framework doesn't force the windows console to recognize ansi codes, make fix

how the heck are you supposed to make a game without fast camera things dude

When opening a file from a different folder with a Chroma-based application, Chroma will create a Content folder in the directory of the file that is being opened, rather than the executable it's being opened with.

i dont feel confident with audio system implementation. might need redesign

not sure why, discord screen sharing is the only thing that messes rendering system up, might be directly related to SDL_gpu itself. might have to see if native examples from SDL_gpu have the same issues

current implementation of the native library loader works only on windows - on linux and friends it assumes the libraries are provided by the system - and extracts files to load them from user's temp directory. not ideal. either provide a mechanism to change that behavior or rely completely on native binaries provided by us

right now chroma works perfectly fine, assuming the user doesn't provide invalid data... HOWEVER i am not sure what are the places that are missing the error handling. find those holes and plug them

so is measurement of different rectangles, redesign that stuff

right now anything can change for any reason, if people are to take this piece of shit framework seriously it needs API definition

could help people avoid bullshit even faster

for whatever reason. however, i've noticed that visual studio is capable of handling dropped text just fine, perhaps it's an SDL-specific issue or i'm missing something windows-specific, as X11 can handle text drag&drop just fine

known issue, fuck knows what causes it, disable joystick and gamepad modules for the time being if it causes issues

jesus h. christ cookie you completely forgot about the fact that games use sound omg get it working before alpha hits the store

right now they take up the same amount of space when embedded and extracted, clogging up the Chroma.Natives.dll

a natural next step and possibly the last feature for the natives library would be to compress natives to reduce the file size.

fuck off with this template

issue: no docs.

what broke
[replace with actual description of the bug please]

how can the dev break it
Steps to reproduce the behavior:

1. [...]
2. [...]
3. etc

what should actually happen instead of y'know... breaking
[replace with some explanation of what did you expect to happen]

got any screenshots?
[no can has pix? remove the paragraph. otherwise post bug related pix]

environment (complete the following):

• OS and version: [e.g. Windows 10/Linux Mint (kernel 2.6.27)]
• GPU: [e.g. Intel HD Graphics 4000]

additional context? remarks?
[post some remarks if you got them, otherwise remove paragraph]

right now theres support for ps4, xbox and nintendo controllers and some barebones support for extensibility, but there is no actual way for people to provide the drivers out-of-engine if they want to

I personally cannot find a use case for it, but some online research suggests it's a feature worth looking into

Especially for multiplayer scenarios it'd be nice to have a property that counts the amount of connected controllers. Currently this can be worked around by creating a counter in the game class and incrementing/decrementing it in the ControllerConnected() and ControllerDisconnected() methods respectively.

not really a pressing issue but it's misleading and causes confusion

When running this code:

context.RenderTo(FrameTarget, () =>
            {
                context.Clear(Color.Red);
                context.Rectangle(ShapeMode.Fill, Vector2.Zero, 100, 200, Color.Aqua);
            });
            FrameTarget.Flush();

            int[] PixelArray = new int[FrameTarget.Width * FrameTarget.Height];
            for (int y = 0; y < FrameTarget.Height; y++)
            {
                for (int x = 0; x < FrameTarget.Width; x++)
                {
                    PixelArray.Push((int)FrameTarget.GetPixel(x, y).PackedValue);
                }
            }

(Array.Push is an extension method)

PixelArray ends up being filled with 0s, instead of the expected red background with aqua rectangle.

If I get a pixel from an RGB image and try to set that color to a pixel in a RGBA image, everything breaks, the colors and positions are wack.

Cookie, pls fix.

e.g. controller subsystem not telling the user they're stupid for setting deadzones for nonexistant controllers. directly ties into #18, after the logging gets unfucked and actually useful

maybe something like a transform stack could be possible

add some primitive z-order batching

time to actually make some feature usage examples so people can finally know how to start doing things!

there is no way to conveniently load content nor a way for people to write their own content providers

chroma needs shaders to even consider itself a "good" framework. make it happen

requires investigation, temporary workaround: extract the damn things to /usr/lib.

no way to do that currently, about time window class got some love again

the general idea is that extensions should be able to load natives in the same fashion chroma core does - need to figure out a standardized system and the built-in native bootstrapper could be a good foundation for the system

because of course they would.

initial crash report suggests sdl_gpu might be at fault?

---
Initializing SDL2 core...
[10:42:47 INF] [GraphicsManager] GraphicsManager initializing...
[10:42:47 INF] [GraphicsManager]  Registered renderers:
[10:42:47 INF] [GraphicsManager]   OpenGL 3 (3.2)
[10:42:47 INF] [GraphicsManager]  Available displays:
[10:42:47 INF] [GraphicsManager]   0: 1792x1120@60Hz
[10:42:47 INF] [Window] Selecting best renderer: OpenGL 3
libfreetype.so not found. Will try to register first...
libfreetype.so is not available. Moving onto next on the list...
freetype.dll not found. Will try to register first...
freetype.dll is not available. Moving onto next on the list...
libpng warning: iCCP: known incorrect sRGB profile
dotnet(82884,0x119aa1dc0) malloc: *** error for object 0x10f0d0010: pointer being freed was not allocated
dotnet(82884,0x119aa1dc0) malloc: *** set a breakpoint in malloc_error_break to debug
[1]    82884 abort      dotnet PixelShaders.dll

SDL_gpu bindings we're using are not compliant with the version of SDL_gpu we're using, it's quite critical to fix it before - or during - alpha period

It would be nice to have a function to call (like love.event.quit() in the love2d framework) that can quit/shutdown the game, especially since the standard windows X button isn't available in fullscreen.

In order to have Chroma not break when multiple instances are started, add timestamps to the names of log files to take care of exceptions raised due to the log file already being in use by another process.

A seperate option to set an FPS goal for a game, so FPS aren't linked to either maximum or monitor refresh rate

not sure if it makes sense to support 32 bits at this point in time... the sooner it's dropped the better i suppose?

general:

• right now the buildscripts keep the mentality of mvp, they will need a refactor once stabilized

osx:

• freetype doesnt link correctly
• sdl_sound and sdl_nmix rpath is dealt with using a post-install_name_tool treatment, perhaps cmakelists tweaks can fix this

might be worth logging that shit upon crashing

need people who had money to burn on bullshit apple hardware so that i can test changes i made to chroma, currently only linux and windows have reasonable amount of testing done

While maybe slightly limited in usability, in some instances it could be nice to have seperate timers running on different frequencies to update game status. While this is technically possible in it's current state, being able to simply do something along the lines of this would be pretty cool:

new UpdateTimer(100, () => {
    // some code that's called 100 times per second
}).Start();

because of course how else are you going to build games without it