Opened 12 years ago

Closed 43 hours ago

Last modified 43 hours ago

#4262 closed enhancement (fixed)

Window position and size should be made persistent (easy)

Reported by: laplace Owned by: nobody
Priority: normal Milestone: R1/beta3
Component: Preferences/Printers Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description


Change History (8)

comment:1 by laplace, 11 years ago

Owner: changed from julun to laplace
Status: newassigned

comment:2 by humdinger, 9 years ago

Owner: changed from laplace to nobody

comment:3 by waddlesplash, 2 years ago

Milestone: R1Unscheduled

comment:4 by diver, 2 years ago

Summary: Window position and size should be made persistentWindow position and size should be made persistent (easy)

comment:5 by sushilhub, 2 years ago

I would like to work on this ticket

comment:6 by refaqtor, 2 days ago

Sorry if I stepped on anyone's toes. I could see in the source that this hadn't been addressed.

I chose to fix and submit a patch for it, which, I believe, is accepted https://review.haiku-os.org/plugins/gitiles/haiku/+/cd4d0790b51dfa8b7f0b1a39efc999ffe28e7e55

I only just created account here, and don't seem to be able to make changes on ticket. I guess there is a process to change the state accordingly. Also, I don't know if this page gets updated dynamically, or needs this ticket removed from suggestions: https://dev.haiku-os.org/wiki/EasyTasks

comment:7 by pulkomandy, 43 hours ago

Milestone: UnscheduledR1/beta3
Resolution: fixed
Status: assignedclosed

Patch applied in hrev55047, thanks!

The "easy tasks" page is generated dynamically from all open tickets containing "(easy)" in their name, so there is nothing special to do.

The default permissions on the bugtracker are limited (unfortunately we had people trying to move their favorite tickets to the next milestone or things like that), but if you submit enough patches and other useful contributions, we can upgrade your account to grant some extra permissions to allow you editing of tickets (including assigning them to yourself, and closing them). Until then, the person doing the review and merge will do that.

As for the review process, since no one is perfect, I prefer to give some time to other people to have a look before I merge things. This is why I voted +2 yesterday but merged the change only today (after doing some extra style fixes I had not seen during the first review).

comment:8 by refaqtor, 43 hours ago

All entirely understandable and perfectly sensible. I appreciate that a history of quality contributions are the deciding factors to increasing responsibility.

Note: See TracTickets for help on using tickets.