Immediate-Mode-UI / Immediate-Mode-UI/Nuklear

Windowless/Infinite Canvas?

Open
#221 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
11.4k
Forks
686
Avg merge
4d 1h
Merged PRs (30d)
3

Description

Hello. I'm interested in using this library to drive some of the UI elements in my system, but I see that all elements must be enclosed in an outer window--or at least this is the sense I get from the examples. Is there a way to make specific windows invisible containers, and in addition, make their size infinite? For example, I'd like to build the UI in world space, and using the node editor example, I should be able to move individual nodes around and wire them wherever I'd like. Would any of this be possible with a few modifications?

I think this could be solved somewhat by allowing the user to specify a per-window style.

EDIT: I do see this [code](https://github.com/Immediate-Mode-UI/Nuklear/blob/ed45455c5d0922e0252675e1e263ff9292c67fd6/src/nuklear_style.c#L677), but I'm not sure if this is something I could use before nk_begin to make the outer window invisible.

EDIT 2: It doesn't seem to do anything at all.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the node editor example and inspect how its windows are created around nk_begin. Read the referenced styling code in src/nuklear_style.c and compare it with the reported behavior when styling is applied before nk_begin. Done means establishing whether invisible, unbounded containers and per-window styles are supported, or defining the implementation scope needed for them.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.