• 0 Posts
  • 79 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle

  • That is definitely a helpful alternative. Thank you. :)

    On a side-note, one rather annoying thing I noticed back in the 2.x days was the inability to set [TAB] as part of a keyboard shortcut (ideally, for switching image tabs). According to this SE thread, it’s because of the inherent limitations of GTK2—the [TAB] key is “reserved for the GTK library”. However, the thread also said (second comment) that

    What really should happen is that the Ctrk-tab is used in a tabbed display to navigate the tabs. Note that Gimp currently uses the obsolete GTK2. Things could be better wit the GTK3 that will be used in Gimp 3.0.

    Are you aware if things are indeed any better now that GIMP uses GTK3? Because unless I’m doing it wrong, it still doesn’t seem to let me select the [TAB] key in the Keyboard Shortcuts window.


  • You’re welcome - I hope you have a good time with it!

    I appreciate that. Thank you.

    If you have pasted an image but not yet made any selections on it then I would have thought that there is no selection to crop to yet.

    Only if you press ctrl-v while having no canvas open. But, if you have a canvas open already, and the canvas is bigger than the image is, you’d want to crop to selection which would get rid of all the extra canvas around the actual image.

    Although, looking back at Edit 1, yeah I should’ve been more specific. That’s on me. Apologies, I have rephrased. :)

     


    Edit 1:

    Also, I realize I got a little heated with Edit 1 & 2. I do apologize if I came across as rude. Again, I have very little but respect for the people who work on this, and believe in the project. Unfortunately, it does have quite a ways to go; but hopefully with the work that has been with the 3.0 backend overhaul those other things can come sooner than what has come before. :)


  • I appreciate your insights in the matter, and with 3.0 here I may have to give GIMP another try!

    I heard 3.0 came out today but I haven’t quite gotten around to trying it out. (I just got home recently, so…) I think I’ll go do that now! :)

     


    Edit:

    Sigh… Yeah it definitely still needs improvements.

    If I copy/paste an image onto a blank canvas (where the canvas is bigger than the pasted image), then press Shift-Ctrl-X to crop to selection; it doesn’t work.

    So I look it up and find that the Crop to Selection option is located under the Image tab. Okay, so I click Image and go to click Crop to Selection. It’s greyed out.

    I go to find out why, and according to the Documentation, it is greyed out if “there is no selection for the image”.

    The Crop to Selection command crops only the active layer to the boundary of the selection by removing any strips at the edge whose contents are all completely unselected. Areas which are partially selected (for example, by feathering) are not cropped. If there is no selection for the image, the menu entry is insensitive and grayed out.

    Why it doesn’t automatically treat copy/pasted layers as selections is beyond me. Most other paint software (even MS Paint!) does this. It’s basic design nowadays.

    Just why? Why does GIMP have to hurt me like this? T_T

     

    Edit 2:

    And it needs to have Lanczos interpolation available for resizing. At present, it only has Linear, Cubic, NoHalo, and LoHalo, whatever the hell those last two are as I’ve never heard of them before.


  • GIMP 3.0 brings non-destructive editing.

    Ah, that is good news! I actually heard about that but kinda forgot, so thanks for reminding me.

    It looks like the UI is going to be pretty similar for the time being

    Balls.

    but the developers have set up dedicated groups to work on it.

    Well there’s that at least. It seriously needs a tune-up in that department.

    I’m probably one of the rare people who is used to it/likes it as it is and doesn’t really want to re-learn it if it changes but anything that helps new people get involved and feel positive using and improving GIMP is welcome in my book.

    I appreciate your candor and your position. I know it must have been many hours of struggle to figure everything out to the degree you have. But as you said, this would help new blood get in the door. After all, sure, overcoming a program’s overly obtuse UI & UX is definitely a thing to be proud of, but frankly it shouldn’t be that obtuse in the first place. Very few people have, or even should be expected to have, the patience to struggle for a half-hour (or more!) to figure out things that in most other programs can be done in seconds. (This isn’t an exaggeration; I’ve had to do this, and only because other programs on Linux were no better.)

    On the surface it might look like all that has happened in 3.0 is the introduction of Layer Effects but my understanding is that the whole thing has been re-written to make it easier and faster to make future progress with it. Hopefully this will be a reboot for GIMP!

    This is good to know! I’m frustrated with GIMP but I still love the ideas it represents, and am hoping it improves to be able to meet the expectations users want to have of it!

    to rotate a layer press Shift+R

    You are a goddamned saint.



  • Exactly.

    And even with the stuff it can do takes 10x longer to do than with most other raster editing software because the UI and UX is so darn convoluted. Like, seriously, I want to like GIMP, but frankly I and most people in fact ain’t gonna spend 10 minutes trying to figure out how to rotate a layer. Lol.

    Frankly, at this point, I just wish Paint.\NET was able to be run on Linux, but I believe it still uses some Windows-specific components—can’t remember what they are—that can’t quite yet be replicated properly using Mono. (Might be some Windows-specific DLLs? Idk.)



  • This is good news. There are a lot of great FOSS alternatives on Linux, but raster editing is one of the last few blind spots, I’ve found.

    • Krita is designed more for painting,
    • MyPaint also seems designed more for digital artwork (and, perhaps just in my experience, but it also seemed rather unstable and kept crashing)
    • KolourPaint is very barebones (seems to be much more a replacement to MS Paint than anything else, so can’t really blame it for that)
    • Inkscape is a vector editor. 'Nuff said.
    • Pinta is the closest to Paint.\NET you’re gonna get on Linux, except it’s based on before the latter went closed-source (bastard…) and as such it’s not as feature-complete as Paint.\NET is.

    GIMP, meanwhile, doesn’t even have nondestructive editing and also can’t draw basic shapes (like squares, cylinders, etc.), can’t seemingly rotate layers without opening the [floating RMB menu] > Layer > Transform > Arbitrary Rotation dialog window, and good GOD the floating menus can go fuck themselves. How I hate the floating menus. Did I mention the floating menus suck? Not sure if I mentioned that.

    Anyway, this switch to 3.0 is really needed and I’m genuinely excited to see the changes it brings, to the UI and the UX in particular.

    Just a shame that they’re switching over to GTK3 when most other developers seem to be transitioning to GTK4.








  • Sorry, I may need to edit my original comment. I didn’t intend to imply that it’s bad. It’s not that great, but it’s not necessarily bad, to be fair. It’s just…meh. And honestly, I imagine that’s largely due to the fact that unlike the big name keyboard app makers, a lot of FOSS keyboards—Heliboard naturally being one of them—don’t track everything under the sun. Which is a good thing and something I like, make no mistake. The unfortunate downside of that is it’s also not quite as accurate, simply due to it not having as many data points.

    This is not something I blame it for, but at the same time I was hoping perhaps another keyboard might have a prediction system different enough to be slightly better. Then again, I’m no expert on keyboard prediction systems so I probably should’ve kept my mouth shut in the first place. So apologies for that. :/

    I feel autocorrect in general has gotten worse in the last decade or so. One problem I noticed, for example, that I’ve faced in other FOSS keyboards, not just in Heliboard, is that compared to ten years ago or so, there is a LOT more instances of autocorrect not catching absolute gibberish (like I get a couple letters off and it doesn’t catch it) or I’m one letter off of a very common word (like 1 key to the left or right) and it corrects it to something wildly different.

    Maybe I’m just misremembering (after all, human memory is hardly ever reliable), but I feel it was a LOT better around the Jellybean era (for Android).

    (Side note: this is all Android-specific; I have never owned any iOS device.)