Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`image()` does not match Processing API

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust

Research direction

Start by locating the current image() entry point in libprocessing or mewnala and inspect how images are currently loaded and drawn. Compare that behavior with the linked Processing API references; done means loadImage(path) loads an Image and image(img, x, y, [w, h]) draws it with the requested sizing forms.

Written by the indexing model from the issue text.

Description

In libprocessing / mewnala, image() is used to load an image:

def image(self, /, file: str) -> Image: ...

In Processing, image() displays an image, while loading is done with loadImage().

Processing behavior
PImage img = loadImage("image.png");
image(img, x, y);
Expected
  • loadImage(path) -> Image for loading
  • image(img, x, y, [w, h]) for drawing
See also
Dominant language
Rust
Stars
69
Forks
14
Avg merge
15d 22h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

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 processing/libprocessing

All issues in processing/libprocessing

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.