GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — `surface` methods get too much use, move into the API · Issue #53 · processing/processing4

surface methods get too much use, move into the API #53

New issue
Copy link
New issue
Copy link
Closed
Closed
surface methods get too much use, move into the API#53
Copy link

Description

@processing-bot
processing-bot
opened on Jan 19, 2020
Issue body actions

Created by: benfry

We've been surprised at how much frame.setResizable() and frame.setTitle() and others are being used, and we should make them into real API.

The switch from frame to surface between 2.x and 3.x was bumpier as a result.

Need to clean this up and get better behaviors for all of them:

  • setSize() is erratic across renderers
  • setResizable() can we make this a one-time operation in settings()?
  • setTitle() is often used to output the fps of an app (a terrible idea, but there we are) so needs to happen at any time (or limited to settings() to prevent that usage)

Activity

  1. processing-bot commented on Jan 21, 2020

    @processing-bot
    processing-bot
    on Jan 21, 2020
    CollaboratorAuthor
    More actions

    Created by: knupel

    Hi, @benfry what you mean by move surface.setSize() in API. If this option is choice. There will be no more possibility to use it in code ? or you mean create a specific Processing methode to call it ? like surface.setSize() became simply setSize() I hope you think about this lastoption, because like you have wrote I use a lot surface.setSize() and surface.setTitle() in my code. By the way congratulation for the time you take to keep Processing up to date with @sampottinger.

  2. processing-bot commented on Jan 21, 2020

    @processing-bot
    processing-bot
    on Jan 21, 2020
    CollaboratorAuthor
    More actions

    Created by: benfry

    @StanLepunK No, the opposite of that. They were left in the surface class because they weren't expected to be used much. Because they get used a lot, we should make them more official than having to introduce this weird surface thing to everyday users, i.e just resize() instead of surface.setSize() or something like that.

  3. processing-bot commented on Jan 22, 2020

    @processing-bot
    processing-bot
    on Jan 22, 2020
    CollaboratorAuthor
    More actions

    Created by: knupel

    @benfry "ouf", like will said french guy like me. But I see there is already method public void setSize(int wide, int high) in public class PSurfaceAWT extends PSurfaceNone I never use it, it don't work ? I ask because here i'm at this time I cannot use Processing :( If something must be coded, this class is it a place to do ?

  4. processing-bot commented on Mar 3, 2022

    @processing-bot
    processing-bot
    on Mar 3, 2022
    CollaboratorAuthor
    More actions

    Created by: github-actions[bot]

    This issue has been automatically locked. To avoid confusion with reports that have already been resolved, closed issues are automatically locked 30 days after the last comment. Please open a new issue for related bugs.

  5. processing-bot
    closed this as completedon Aug 19, 2024
  6. github-actions
    locked as resolved and limited conversation to collaborators on Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.