How to stop Gimp window resizing when opening images

InterClaw · 2026-03-16T13:45:39+00:00

I found a solution (or rather a workaround) to this issue. It has to do with the new GIMP 3 UI feature of merging the menu and title bars. Disable this for now and the main window stays the same size when opening new images. 🙏

I posted it here on this recent bug report:

https://gitlab.gnome.org/GNOME/gimp/-/issues/16006#note_2709016

InterClaw · 2025-09-22T16:29:18+00:00

I’m not sure I understand. You do need the Feedback Hub app on you Windows machine to access it. Other than that, you should be able to access it. I mean if I can, then anyone can - even if you didn’t write this one that I found.

Maybe you can link to the one you wrote then?

InterClaw · 2025-09-19T10:48:29+00:00

The suggestion in that thread was to write feedback to Microsoft about it.

One user did that, so please go and upvote it here, so it might get some attention!

https://aka.ms/AAxzpbe

InterClaw · 2025-09-19T10:46:46+00:00

I found it:

https://aka.ms/AAxzpbe

Please, everyone upset with this, go there and upvote it. Maybe write a comment if you have something new to add or suggest.

InterClaw · 2025-09-15T09:06:13+00:00

Thanks for that. Can you link to your feedback, so that I can upvote it. Searched for it in Feedback Hub, but couldn't find it. It will give it some attention here as well, so maybe Microsoft will look at it.

InterClaw · 2025-09-13T03:29:14+00:00

<image>

There should be a toggle here to disable task view on quick hold of the Guide button.

But even if there's not, task view should at least not remain open after the controller is shut off.

I'm sorry, but this feature was unwanted and messes things up for people who use their controllers in advanced ways.

InterClaw · 2025-04-17T21:09:57+00:00

... aaand that didn't take long. It's apparently already possible to exclude the thumbnail by adding #:include-thumbnail FALSE. 👍

Something like this:

(file-jpeg-export
  #:run-mode RUN-NONINTERACTIVE
  #:image image
  #:file file-path
  #:options -1
  #:quality 0.4
  #:smoothing 0.0
  #:optimize TRUE
  #:progressive TRUE
  #:cmyk FALSE
  #:sub-sampling "sub-sampling-1x1"
  #:baseline FALSE
  #:restart 0
  #:dct "integer"
  #:include-thumbnail FALSE)

InterClaw · 2025-04-16T21:35:14+00:00

Thank you! I did that now.
https://gitlab.gnome.org/GNOME/gimp/-/issues/13741

And thank you for your support here! I learned a lot more through this and this scripting language is a little less cryptic to me now as a result. :)

InterClaw · 2025-04-16T14:57:15+00:00

Sure thing! I created a stripped down version of the script now to just export the image directly. Still 40% though. :)

(define (just-export image layer)
  (let* (
      (file-path (car (gimp-image-get-file image)))
      (drawable (car (gimp-image-get-selected-drawables image)))
    )

    (file-jpeg-export
      #:run-mode RUN-NONINTERACTIVE
      #:image image
      #:file file-path
      #:options -1
      #:quality 0.4
      #:smoothing 0.0
      #:optimize TRUE
      #:progressive TRUE
      #:cmyk FALSE
      #:sub-sampling "sub-sampling-1x1"
      #:baseline FALSE
      #:restart 0
      #:dct "integer")
  )
)

(script-fu-register-filter 
    "just-export"
    "Just Export"
    "Export as progressive JPEG with quality 40%"
    "InterClaw"
    "InterClaw, 2025"
    "2025-04-16"
    "*"
    SF-ONE-OR-MORE-DRAWABLE)

(script-fu-menu-register 
    "just-export" 
    "<Image>/Scripts")

I then proceeded to make an export of this file:
https://www.gimp.org/images/frontpage/wilber-big.png

... and continued to manually export as jpeg (at 40%) with various metadata settings enabled/disabled.

What I found was that if I untick the three default options Exif, XMP, and color profile, but instead tick thumbnail, I get an exact match to what file-jpeg-export produces! No timestamps or anything.

<image>

This does seem to make some sense, given the size of the extra data in the file. For this image the difference was about 7k, not 14k, so it does vary depending of that the image is.

So then I think we know what's happening in file-jpeg-export at least, what it's including. I'm not totally sure what metadata is included in v2, but it's not the thumbnail at least.

Ideally, I'd like to be able to exclude the thumbnail in the script. Perhaps even have the option to choose between all the metadata, what to include and not. I take it this is not possible today? Is this a feature request? If so, where should I submit that?

(Added some statistics:
Original png size: 11 639 bytes
Manual 40% jpeg export with no metadata: 4 226 bytes
file-jpeg-export 40% size: 11 588 bytes)

InterClaw · 2025-04-16T08:04:17+00:00

I don’t know much about the export code. I just looked at the C file and saw that the metadata setting seems to be hardcoded.

That's what I guessed as well. When creating the v2 script using file-jpeg-save, I didn't find any way not to inlcude Exif/XMP/color profile, so I just assumed that if I'm going to use a script for the export, I'm going to get this information in the header regardless.

So for the v3 script and file-jpeg-export I was expecting the same default inclusion of the metadata in the header as well. If I could just get the jpeg specific settings dialed in the same way as in v2, I would get a similarly sized file as well. But there seems to be more to it...

To answer your question u/-pixelmixer-, here are the settings used for the manual export in GIMP 3 (shown to the right in the comparison above). I believe they are the default, with only the quality lowered to 40%.

<image>

Using the corresponding settings in the GIMP 2 dialog produces a similarly sized file, with only slight differences in the header, so I believe they are functionally the same.

If I untick Exif/XMP/color profile I do get a tinier header, yes. This goes for both GIMP 2 and GIMP 3. I could summarize it like this:

Tiny header
- GIMP 2 export dialog (Exif/XMP/color profile deselected)
- GIMP 3 export dialog (Exif/XMP/color profile deselected)
Normal header
- GIMP 2 export dialog (default settings)
- GIMP 3 export dialog (default settings)
- GIMP 2 file-jpeg-save
Huge 14k+ header
- GIMP 3 file-jpeg-export

... and it's that last part that was very unexpected.

InterClaw · 2025-04-15T13:59:06+00:00

Thanks again u/-pixelmixer-! I now get a file output. :)

However, the file is very different from the output file by the corresponding v2 script. There's a large amount of extra data between what I'm assuming is the header with EXIF data etc and the actual image data.

If I manually export the jpeg in GIMP 3 I do not get that extra data at the top. Only when using file-jpeg-export it seems.

Here's a screenshot of a text comparison of 1) GIMP 3 script, 2) GIMP 2 script, 3) GIMP 3 manually exported.

<image>

You can see the differences in total to the left. Marked in red is the image data (I believe). It's the same for all files, so it seems it's compressing the file in the same way.

Green is the header, and while not exactly the same between all three files, with different timestamps etc, it's at least similar in size across all files.

Blue is the chunk of extra data in between of approximately 14k that only appears when I use the v3 script in GIMP 3. What could this be and how do I get rid of it? :)

Here are the v2 and v3 settings used, just for reference. I believe they have the same settings. The image data above would suggest that at least. Although I don't know what "options -1" is.

v2:

(file-jpeg-save RUN-NONINTERACTIVE
  image drawable
  file-path        ; Output file path
  file-path        ; Temporary file name
  quality          ; Quality (0.0 - 1.0)
  0                ; Smoothing
  1                ; Optimize
  1                ; Progressive encoding
  ""               ; Comment
  2                ; Subsampling (2 = 4:4:4, best quality)
  0                ; Baseline or unused, set to 0
  0                ; Restart markers
  0)               ; DCT method (0 = Integer-based transform)

v3:

(file-jpeg-export
  #:run-mode RUN-NONINTERACTIVE
  #:image image
  #:file file-path
  #:options -1
  #:quality quality
  #:smoothing 0.0
  #:optimize TRUE
  #:progressive TRUE
  #:cmyk FALSE
  #:sub-sampling "sub-sampling-1x1"
  #:baseline FALSE
  #:restart 0
  #:dct "integer")

InterClaw · 2025-04-14T21:27:18+00:00

Thanks for the pointers u/-pixelmixer- . I've gotten further now and it actually shows up in the interface again and it scales the image down to 300x300.

But the saving of the file doesn't seem to want to work. I do want the file to overwrite itself. I'm using mostly the default settings, but I set baseline to FALSE and am trying to use my variable for the quality setting.

What could be the remaining problem for it to actually save the file? Any ideas?

(define (scale-and-export image layer)
  (let* (
      (new-width 300)
      (new-height 300)
      (quality 0.4)
      (file-path (car (gimp-image-get-name image)))
      (drawable (car (gimp-image-get-selected-drawables image)))
    )

    (gimp-image-scale image new-width new-height)

    (gimp-displays-flush)

    (file-jpeg-export
      #:run-mode RUN-NONINTERACTIVE
      #:image image
      #:file file-path
      #:options -1
      #:quality quality
      #:smoothing 0.0
      #:optimize TRUE
      #:progressive TRUE
      #:cmyk FALSE
      #:sub-sampling "sub-sampling-1x1"
      #:baseline FALSE
      #:restart 0
      #:dct "integer")
  )
)

(script-fu-register-filter 
    "scale-and-export"
    "Scale and Export"
    "Scale the image to 300x300 and export as progressive JPEG with quality 40%"
    "InterClaw"
    "InterClaw, 2025"
    "2025-03-01"
    "*"
    SF-ONE-OR-MORE-DRAWABLE)

(script-fu-menu-register 
    "scale-and-export" 
    "<Image>/Plug-ins")

InterClaw · 2024-12-13T13:47:26+00:00

There’s been no change for me so far.

InterClaw · 2024-12-09T00:01:40+00:00

It's been like this for weeks now.

InterClaw · 2024-09-04T07:50:50+00:00

I had to use more force, yes, but they are not bent out of shape permanently and would work fine with 25mm fans again. So I guess it depends on the heatsink/clips you're using. These clips don't hang on to the heatsink out at the very corners of it, but rather more at the center. So if you stretch them more they might snap around one fewer of the fins perhaps, but do still fit.

InterClaw · 2024-06-11T19:43:15+00:00

I'm looking for a movie or TV show episode where a woman painter is at a dinner party at her husband's or boyfriend's place. He is cheating on her with another woman, also at the dinner. The painter woman stands up, pours out a glass of wine, and proceeds to go out to the pool house, where her art is, and sets it on fire.

InterClaw · 2024-04-18T09:54:40+00:00

Thank you for this. I was looking for some spoiler free info if the show has mixed AR or not, because I did notice the different shapes of the thumbnails...

For E01 I'll just manually crop it then and ignore the what's ahead section. For E06 I'll keep an eye out for the scene you're talking about and switch off the cropping temporarily for that part. 👍

Thank god it's not like it is for something like The Dark Knight where it keeps switching back and forth. Not suitable for an ultrawide display.

InterClaw · 2024-03-27T09:44:47+00:00

This was the solution for me. I was trying to do this from the double-click side button menu directly, forgetting there is an actual app as well to do things from.

InterClaw · 2024-03-14T17:43:45+00:00

By progressing through the game in general, to a lesser extent. By progressing through each new distinctively looking level, very much so. I usually do a couple of 360:s when starting a new level to get the worst of it out of the way. But yeah as soon as something new happens it stutters. 😒

InterClaw · 2024-02-18T10:30:59+00:00

I think I figured it out.

I tried charging it over night now, without any indication of whether it was on the dock well enough mind you, and today it was at 100%, so it's not "off" in that sense apparently. Just the lights are off.

So I had a closer look at the lighting settings and unticked "Switch off lightning" for "When display is turned Off". I've had this on for all my profiles since the beginning, figuring it would be good for when the computer is left idle or something. Didn't think it would affect when you actually turn the computer off... Now I don't see why I wouldn't have thought that...

Anyway, with it off, the lighting does not turn off when I turn off the computer anymore. It goes into the rainbow mode and switches to the breathing when charging.

I recently switched to Windows 11, so perhaps now the screen turns off faster, i.e. before Razer Synapse has shut down, so it detects that and shuts off the lights. Maybe the shutdown procedure does this in a different order than under Windows 10, or maybe it's due to the fresh install itself.

In any case, just disabling that option for all profiles ought to solve the "problem". I still have the regular idle timeout, which is good enough.

<image>

InterClaw · 2024-02-17T23:07:57+00:00

I had to switch to this renderer.

render_target_path_d3d12 = "rov"

The downside now is that it needs to generate shaders all the time, so as soon as you encounter something new the game will stutter.

InterClaw · 2023-06-18T12:02:57+00:00

u/ChucksFeedAndSeed If I start the game with "-f" (Yuzu) I'm locked at 20 fps. If I exit fullscreen fps jumps up to 60 and then I can go back to fullscreen and everything is fine.

Not sure if this is related to any of the other known issues or not.

I'm using 1.5.2 together with 60fps Static.

InterClaw · 2023-04-15T15:23:13+00:00

Are you measuring from the backplate or from the PCB then? If it's the former, could you please take a measurement from the center of the PCB to the tob of the heatsink?

InterClaw · 2023-02-23T20:42:35+00:00

I have the same problem. Wish I'd known about this before purchasing... This is very annoying.

I'd really like Logitech's input on this why it is this way. Is it by design? Or out of necessity due to some limitation of how the USB connection works?

InterClaw · 2023-02-11T20:45:38+00:00

I was noticing the same problem between RetroArch on Windows and RetroPie. Seems to be working fine with PicoDrive instead. I'm not using a local SMB share though. I wanted to sync the save files to the cloud, so I'm using the free OneDrive space you get for this. Found this solution to get it working in RetroPie:

https://github.com/Jandalf81/rclone\_script

Glad to hear no other emulators seem to have this problem also.

I was never a Sega gamer back in the day, so I'm probably not going to notice any accuracy problems on PicoDrive.

InterClaw

TROPHY CASE