Manual in-game resizing

Open
#91 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Review issue #90 and the XML resLoc/modid behavior first. Define how additive GUI scale, single-element size overrides, anchoring, and automatic root-view selection should work, then verify the design covers all UIs and the listed fullscreen and resizable-element cases.

Written by the indexing model from the issue text.

Description

Addendum to #90
Should be on xml resLoc + modid basis
Allow for all UIs:

  • override gui-scale additively, eg. vanilla settings is 2x, but user would like to have 4x

Allow for single primary resizable element:

  • override gui size additively, eg. xml size is 320x240, but user would like to have 320x480
  • override gui size anchor, ie. xml size (now) or screen size (fullscreen window type without scaling) - effectively enabling UI to follow screen resolution
  • should be automatic or UIs having only one resizable element at root view (list or zoomdrag only?)
Dominant language
Java
Stars
6
Forks
21
Avg merge
10d 13h
Merged PRs (30d)
1

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.

More from ldtteam/BlockUI

All issues in ldtteam/BlockUI

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.