Gimp 2.99.2 – GTK3 user interface toolkit

Non-destructive adjustment laters are pretty much must-have for a image editing software for it to be taken seriously. It’s something the GIMP devs should be focusing on, not something that a random person on the internet does on their free time. Especially considering it has been a well requested feature for over 10 years.

Ps. you’re not going to get anyone to commit anything with that kind of message. You’re just driving people away from oss.

cycloptic wrote at 2020-11-07 00:11:56:

Most of the current developers _are_ random people on the internet who decided to contribute to it in their free time. If you have noticed, repeatedly asking for a feature when it's already on the roadmap as a high priority item and has been there for some years also does not help the feature get implemented any faster.

xvilka wrote at 2020-11-07 02:12:37:

They just should have done what Krita did - gather money, hire developers full time.

cycloptic wrote at 2020-11-07 02:53:39:

That requires administrative staff to run the fundraiser, handle the accounting, do the hiring...

boogies wrote at 2020-11-07 03:03:27:

GIMP does theoretically have indirect access to administrative staff from the FSF through GNU, I think?

cycloptic wrote at 2020-11-07 03:17:24:

Well, a few things. It would be GNOME Foundation, but historically they have existed mostly to coordinate volunteers and have been reluctant to hire developers because of that. (It creates conflicts of interest) In general, the people who are good at fundraising are already heavily in demand and they know it.

Plus, the lead developer(s) would have to commit to increased management responsibilities in order for it to happen, and they don't seem to be willing to for various reasons.

prokoudine wrote at 2020-11-07 02:57:32:

Yes, let's add non-destructive editing on top of horrible design decisions, unmaintained UI toolkit with a crapton of bugs, semi-working graphic tablets support, barely working custom HiDPI support etc. What a splendid idea you got there :)

boogies wrote at 2020-11-07 03:01:29:

TFA lists improvements to graphics tablet support, HiDPI support, and — in the title itself — switching to a more maintained UI toolkit.

zeotroph wrote at 2020-11-06 21:42:01:

What is it with the simplified Gtk file dialogs?

Whenever I use one I am instantly annoyed because I get the impression that some UI-concept from MacOS was badly copied, but is a mismatch for arguably more poweruser-centric Linux user base. Once I discovered that Ctrl-L can bring up the url/file path I found it at least usable, but still not pleasant.

Am I using it wrong? Can I change the default system wide somehow? Is there a design document which can finally convince me that this is generally a good idea, just not for me?

Also, some Gtk apps had/have tearable menus, a shame these went out of fashion. Is there something fundamentally wrong with that, too, or can this be enable globally for Gtk, and maybe even Qt apps?

blibble wrote at 2020-11-06 22:14:04:

you can change it system-wide... but there's a bug which means it constantly gets reset

the most annoying thing about the dialogs is if you type a filename in: instead of selecting the file with that name it starts doing a recursive search...

no-one has EVER wanted to do that

jl6 wrote at 2020-11-06 22:19:52:

This is rapidly becoming GNOME’s most famous bug. The developers still claim it’s working as intended.

apricot wrote at 2020-11-07 01:54:02:

GNOME suddenly changing things for the worse, breaking muscle memory and making previously easy things difficult or impossible, while tone-deaf developers intone the "it's not broken, your workflow's broken" mantra in the background, has become a regular thing. It's like living in hurricane country and accepting you'll need to replace the windows from time to time.

I really wish they'd stop doing this, though.

cycloptic wrote at 2020-11-07 03:01:00:

Have you tried either GNOME Classic or MATE? It seems like a difficult ask to request that developers stop trying new things.

pmontra wrote at 2020-11-06 22:30:16:

That's why I'm using Nemo as file manager in Ubuntu. Unfortunately the files dialog is still Nautilus but it's okish there, given I don't have to do much when picking a file or deciding where to save it.

bhrgunatha wrote at 2020-11-07 02:57:07:

The file save dialog is the worst UI I have to fight with daily. It's such a seriously badly designed piece of UX.

Is there a simple way to save a file to a parent folder in the UI without using Ctrl+L? Other than select the grandparent, and from there select the parent?

opan wrote at 2020-11-07 04:54:45:

In the filename box, press enter to save to the dir you're viewing rather than selecting one deeper.

bhrgunatha wrote at 2020-11-07 05:11:10:

Thank you very much. Something that genuinely makes my computer use more tolerable.

flobosg wrote at 2020-11-07 01:12:12:

There's an issue asking for an icon view with thumbnails in the GTK file picker. The discussion has been ongoing for _sixteen_ years:

https://gitlab.gnome.org/GNOME/gtk/-/issues/233

JaggedJax wrote at 2020-11-06 21:46:06:

Thank you for the Ctrl+L trick! This has been killing me for ages.

BuildTheRobots wrote at 2020-11-06 23:42:11:

> Once I discovered that Ctrl-L can bring up the url/file path I found it at least usable.

This seems to be the same shortcut on Gnome and Windows, so I'm curious where it comes from.

mseepgood wrote at 2020-11-06 23:56:11:

> I'm curious where it comes from.

Web browsers. Ctrl-L = focus location bar since at least Netscape Navigator.

aloisdg wrote at 2020-11-07 00:16:28:

I didnt know about ctrl+l. I use Alt+D all the time.

maxerickson wrote at 2020-11-06 23:59:58:

Netscape Navigator on Mac used it in 1999:

https://www.w3.org/WAI/UA/netscape-keyboard.html

I don't have a thought of where to check next. It could originate there, as a mnemonic for command+link.

patrec wrote at 2020-11-07 00:16:56:

> a mismatch for arguably more poweruser-centric Linux user base.

Uhm, to the best of my knowledge the macOS file dialogue is _far_ more powerful than anything the various linux toolkits offer.

zapzupnz wrote at 2020-11-07 05:13:37:

Yes, they’re talking about how the GNOME one is poorly designed, not the macOS one.

3np wrote at 2020-11-07 01:28:10:

Which is to their point.

formerly_proven wrote at 2020-11-06 20:39:48:

The Gimp devs taking nine years to port from Gimp Toolkit 2 to Gimp Toolkit 3 kinda invalidates all claims about porting between Qt versions being too hard, doesn't it?

jononor wrote at 2020-11-06 21:00:06:

A major reason for not shipping GTK3 port, which was largely completed a long time ago, is that GIMP 2.x has a stable plugins API and GTK2+ is exposed in said API. At the same time there has been other major revamps of the API with changing image processing layer to use GEGL. It was decided to release both breaking changes as GIMP 3.x, instead of breaking first the one, then the other.

jandrese wrote at 2020-11-06 21:00:47:

The port from GTK2 to GTK3 isn't even that hard in my experience. It's a lot of typing but for the most part stuff works the same with a few exceptions (like tooltips).

It's kind of important too because bugs in Gtk2 aren't getting fixed anymore. I ran into DBUS related issue with Gtk2 and ScrolledWindows in Ubuntu 20 and the dev response was basically "ew, gross, I'm not touching that". Fixing it required me to rewrite the app to use Gtk3 instead.

Iwan-Zotow wrote at 2020-11-06 21:15:55:

No, there are a lot of breaking changes beyond 2->3 transition. Basically, everything had changed: toolkit, extensions, styling, icons, theming

Devs wanted to do it all at once

asutekku wrote at 2020-11-06 23:34:14:

Still should not take nine years, even if it is an oss project.

brnt wrote at 2020-11-06 21:10:27:

Is there any technical merit for Gtk at this point?

rebeccaskinner wrote at 2020-11-06 21:19:45:

Maybe it's just familiarity, or I'm out of touch since it's been a few years since I was really evaluating the options, but I find GTK much nicer to work with than Qt. It seems to do better with language bindings too. GTK being a C API seems to make it a lot easier to auto-generate bindings for any language with an FFI. Qt, being both primarily a C++ API, and also with the custom preprocessor and signal/slot nonsense seems like it's much harder to make sensible bindings for.

matthiasv wrote at 2020-11-06 22:55:24:

> GTK being a C API seems to make it a lot easier to auto-generate bindings for any language with an FFI.

Not only that but as outlined in that article, GObject introspection allows easy integration with most popular dynamic languages (most importantly JS and Python) without the need for specific bindings.

CameronNemo wrote at 2020-11-07 03:30:39:

JS and Python are the best Qt bindings, though.

GObject helps out with other languages like Rust and Lua.

billfruit wrote at 2020-11-07 03:38:39:

QT python bindings were rather confusing with multiple libraries and basically very poor documentation when I checked a couple of years ago.

Not to mention QTs java binding also was not a good story.

intrepidhero wrote at 2020-11-07 04:03:13:

Python + Qt got waaay better with the release of Qt 5. It's called wither "Qt for Python" or PySide2. I dunno why it has two names but the docs are fantastic.

https://doc.qt.io/qtforpython/contents.html

m4rtink wrote at 2020-11-07 04:07:50:

There could be a licensing merit if the unclear and unfavorable situation about licensing and availability of new Qt releases continues to deteriorate.

pjmlp wrote at 2020-11-06 21:13:42:

I guess being the one that is more GNU/Linux oriented, so that is what most managed languages frameworks bind to (Swing, SWT, GtkSharp, Gtk-rs, Gtkmm, PyGtk,...), specially because of GObject it is relatively easy to generate bindings.

billfruit wrote at 2020-11-07 03:36:28:

May be that it is at least allows one to write code in c/c++, rather than the "moc" macro language system used by QT.

bitwize wrote at 2020-11-06 20:48:37:

GTK hasn't been the Gimp Toolkit in years. It's much more the GNOME Toolkit these days.

baybal2 wrote at 2020-11-06 22:28:04:

Yes, siding with you on this.

Biggest fault of the Gtk/GNOME ecosystem these days is a small bunch of atrociously toxic people centering around RedHat shouting "Nobody besides me works on this, and that! So sit tightly, and shut up with your feedback!," while completely forgetting that it was them who scared off, and trolled out most normal people out of the GNOME community, including some of the best devs they had.

cycloptic wrote at 2020-11-06 23:13:51:

Can you elaborate on this? Who was scared off, and how/why was this done?

zozbot234 wrote at 2020-11-07 00:13:57:

There is a lengthy history of general toxicity, gatekeeping attitudes and the like in the Gnome dev community, dating back to the early 2.x days. This extensive comment

https://dot.kde.org/comment/60560#comment-60560

dates back to 2003, and back then RedHat wasn't even heavily involved in development (the major corporate sponsors back then were Eazel and Ximian, which are basically unheard of today) but clearly the overall attitude has not changed much since then.

cycloptic wrote at 2020-11-07 00:58:03:

That appears to be a completely out-of-context comment about GNOME made on a KDE blog for unclear reasons. But anyway, I looked through most of the links in that comment and I'm not entirely sure what you're referring to. There are some heated arguments around technical issues in those mailing list posts, but there are also many positive comments such as this:

>If anything, we have to turn the GNOME community around and make this community a tolerant community, and a community of love. I have to say that I am surprised by how well the gnome-love mailing list has taken of, and surprised to see various newcomers to the platform actually writing code and becoming productive.

Also, that was quite a long time ago (some posts are from earlier than 2003) and most of those people involved in those threads don't appear to be associated with the project anymore. It certainly seems like they were able to work out some of their process issues in the last 17 years seeing as how the bonobo/orbit parts were dropped entirely.

xalava wrote at 2020-11-06 20:30:20:

Just on time for GTK 4. Pretty ironic considering that GTK stands for Gimp ToolKit.

CameronNemo wrote at 2020-11-06 22:40:33:

And Inkscape only updated to 3 earlier this year. I wish the GTK devs would realize that these applications are the life blood of their toolkit. Calculators, calendars, and even mail apps can be popped out easy peasy when they need to be. Applications like GIMP, Inkscape, and Ardour take years to become usable and competitive.

lmedinas wrote at 2020-11-07 00:46:11:

this is problem #1 of Linux Desktop. Toolkits and Libraries constantly changing and reinventing the wheel. Actually a big part of developing an GTK App is actually catching up with the API changes. As a proof of this see the early how-tos of GTK 3.0 and 3.2 and see the recent ones and see how much it changed.

There were plenty of apps changing from GTK to Qt awhile ago i suspect GTK4 will be the next. As for Gimp and Inkscape it will probably take another decade to catch up.

2Gkashmiri wrote at 2020-11-07 05:42:39:

Call me a noob but why should this problem exist even today ? Why are APIs such grossly incompatible with previous gens such that a complete overwrite is necessary?

tripa wrote at 2020-11-06 20:28:13:

I wasn't too happy when my distro upgraded from 2.8 to 2.10. The new icon set for the toolbox may be more trendy, but I have a _much_ harder time recognizing/understanding which is which not they're all monochrome.

Glad to see HiDPI come up.

reidrac wrote at 2020-11-06 20:41:16:

You can change that on the settings. I know because I had the same problem and you can choose a more familiar iconset.

Dahoon wrote at 2020-11-06 21:13:42:

>You can change that on the settings.

Always a valid reply in Linux discussions.

kzrdude wrote at 2020-11-06 23:53:30:

Though not always in GNOME discussions j/k

zozbot234 wrote at 2020-11-07 00:35:04:

"You can change that in dconf. Though maybe there is a tweak for it. Or perhaps it's a behavior you can script in gnome-shell."

kelnos wrote at 2020-11-07 02:25:22:

More like "you can change that in dconf, but there's a bug[0] that makes it reset every time you restart the application".

[0] _sotto voce_ "that we're probably never going to fix"

Shared404 wrote at 2020-11-06 23:24:52:

To be fair, that's part of why I use Linux :)

MildlySerious wrote at 2020-11-06 21:01:27:

The silver lining to that is that I ended up using shortcuts that I never bothered memorizing before.

kzrdude wrote at 2020-11-06 23:54:07:

I'm so poisoned by election news that I read "Nate Silver" in your comment.

Kjeldahl wrote at 2020-11-06 20:33:39:

Yeah, except I guess 98% of HiDPI users are on MacOS, a platform they are currently unable to create builds for.

mixmastamyk wrote at 2020-11-06 21:18:23:

It's 2020. I've been sitting in front of two 4k monitors for perhaps five years now, under Ubuntu Mate. Every month or so an HN comment implies it doesn't work. ;-)

btashton wrote at 2020-11-07 02:36:17:

So many years of people telling me that my exact setup does not work, yet here I am not remembering the last time I had an issue with displays on Linux. It has even gotten _better_ since I moved to Wayland which I am also told does not work.

tripa wrote at 2020-11-06 20:43:24:

So I am the 2%. Glad anyway :)

dubcanada wrote at 2020-11-06 23:22:07:

Ya there certainly isn’t and hidpi windows or Mac users

solarkraft wrote at 2020-11-06 23:17:05:

Hello from the 2%.

ravenstine wrote at 2020-11-06 20:43:39:

Plugins now possible with Python 3, _JavaScript_, Lua, and Vala

This is a game changer for me. I could use Python, but I'm a full time JavaScript developer and I'm just not the biggest fan of Python in the world. But if I could script in Gimp using JavaScript... that'd be sick!

xvilka wrote at 2020-11-07 02:19:05:

Never understood why do they need Vala in 2020? They could have focused on improving Rust integration and writing some applications in it.

moonchild wrote at 2020-11-07 04:09:35:

Vala is pretty much the official gtk language (insofar as there is one), and remains actively developed. Not sure what the problem is.

iso8859-1 wrote at 2020-11-06 21:12:16:

A lot of GNOME is written in JavaScript now, this is just GIMP catching up to that ecosystem.

xvilka wrote at 2020-11-07 02:20:27:

I hope they will get rid of it eventually like they got rid of C#/Mono applications.

pjmlp wrote at 2020-11-06 21:14:46:

Which is why I eventually switched to XFCE. GJS use is quite noticeable.

jamesgeck0 wrote at 2020-11-06 21:56:37:

IIRC, the optimization benchmarks Canonical did have indicated that JS hasn't been the issue in most of the Gnome performance issues they've worked on.

pjmlp wrote at 2020-11-06 22:36:28:

Well,

https://feaneron.com/2018/04/20/the-infamous-gnome-shell-mem...

kzrdude wrote at 2020-11-06 23:55:32:

Took a decade to get there. Yes, some of us didn't follow gnome through this time.

nikodunk wrote at 2020-11-06 20:41:17:

Damn! That looks a so much better than the GTK2 2.10 version. And better Wayland & HiDPI support – thank the stars.

terramex wrote at 2020-11-06 20:56:23:

Wow, that splash screen is so bad that it wraps around the scale and is actually amazing. I admire not trying to compete with Adobe's colorful, highly polished but extremely boring splash screens.

themodelplumber wrote at 2020-11-06 21:15:51:

I think this has been the tradition with GIMP dev version splash screens. They are really tongue-in-cheek. It'll change...

kzrdude wrote at 2020-11-06 23:56:02:

dev version splash screen, it's for fun.

ohazi wrote at 2020-11-06 20:29:10:

Does anyone know if those hideous GTK3 title bars are rendered by the client (GIMP), or is the person taking the screenshot just using GNOME?

klodolph wrote at 2020-11-06 20:39:57:

The title bars look identical to everything else on my Gnome 3 system.

ohazi wrote at 2020-11-06 20:49:00:

Right, and I'm running XFCE with a different theme, or i3 without any titlebars, and every GTK3 app that uses client-side window decorations looks out of place.

I'm not running Gnome 3, I don't ever intend to run Gnome 3, and GTK shouldn't poison the last 15 years of GTK applications to try to bump up the Gnome 3 adoption numbers by attrition.

It's petty and obnoxious.

cycloptic wrote at 2020-11-06 21:28:18:

The titlebars are a design choice made by the app developer, not by GNOME. At least in the sense that it's only part of GNOME's design guidelines, app developers using GTK don't have to follow it if they don't want. There are various ways you can configure/modify a GTK app to hide the titlebars and attempt to use server-side decorations. But either way you are faced with the choice of potentially hiding important functionality if the app developer has decided to put buttons in the titlebar, or having two titlebars like with this patch:

https://github.com/PCMan/gtk3-nocsd

heavyset_go wrote at 2020-11-06 20:50:03:

They really need to get around to either adopting the Glimpse[1] name, or dropping their current one for something else.

The project's name makes it hard to recommend it in a professional context even when it would get the job done well.

[1]

https://glimpse-editor.org/

bogwog wrote at 2020-11-06 21:14:39:

Did these people seriously fork GIMP just so they can change the name?! I didn't even know anyone cared about that.

I've been using GIMP for many years (since at least 2008) and have heard _many_ valid and not very valid complaints, but never anything about the name being offensive.

GIMP has a lot of problems hurting its adoption in professional settings, but the name is hardly one of them. Creating a fork just for that is bike-shedding to the extreme.

mixmastamyk wrote at 2020-11-06 21:22:01:

We've used it in visual fx houses since 1998, no one ever mentioned the name. Many folks don't even know the word, it's British I think.

hda2 wrote at 2020-11-07 01:36:20:

Likewise. We've been using it in our company in a professional context for years. Coworkers who were introduced to it for the first time have never commented on or were offended by the name. Not a single one.

To those who keep complaining about the name: Do you think git's name should also be changed?

russholmes wrote at 2020-11-06 22:51:21:

It is an unpleasant slur both in UK and US English.

https://dictionary.cambridge.org/dictionary/english/gimp

kzrdude wrote at 2020-11-07 00:00:12:

(I'm not a native speaker) It seems like it's really a kind of cruel joke of an acronym, and those of us who don't recognize it just get the worst of both worlds - a bad name and no joke.

romanoderoma wrote at 2020-11-06 23:13:38:

Scala means ladder in Italian and Sega means handjob

The French Word fiche means casino token and has been popularized by American Casinos and movies, yet in Italian it reads fike and it's a quite vulgar slur which literally means vaginas but it's used to say "nice looking girls"

It's the plural of fica, which sounds exactly like the Swedish fika, that means coffee break

You can imagine how that sound for an Italian to be offered a fika

Lumia means prostitute in Spanish

BTW a preservative in French is a condom...

The world does not speak English as a native language

Edit: but, as usual, judging from the immediate downvote Americans won't accept that they are only 5% of the World population...

bhrgunatha wrote at 2020-11-07 02:43:16:

> Lumia means prostitute in Spanish

I had a few Spanish friends while I lived in Australia who found The Mitsubishi Pajero hilarious.

It seems really odd to me that it's still named that considering that Spanish is so widely spoken.

https://translate.google.com/?hl=en#view=home&op=translate&s...

m4rtink wrote at 2020-11-07 04:15:46:

Do not ever try to say you are going to _search_ something or _someone_ in Polish if there are any Czech speakers nearby - the results might be surprising.

kelnos wrote at 2020-11-07 04:04:54:

The open source world, by and large, uses English as its lingua franca. Of course we're well aware that sometimes commonplace words in one language can mean something offensive in another language.

But I think it highly likely that the original developers of the GIMP knew exactly what it meant in English and probably chose the name _because_ of its English meaning, as a joke that may have been funny in geek circles back then, but now we realize is just in poor taste. (I will give them the benefit of the doubt and assume they were probably more targeting the sexual connotations of "gimp" and weren't making fun of physically disabled people.)

The downvotes are likely because it seems like you have an axe to grind about English being the de facto common language of the internet, not because people think you don't have a good point to make or because of some silly nationalistic reason.

zapzupnz wrote at 2020-11-07 05:21:29:

I’m down voting because of that very reason, yes. And the needless edits to complain about the down votes; this isn’t reddit.

mackrevinack wrote at 2020-11-07 00:35:12:

offence has nothing to do with it for me. there's just a pretty good chance i will start being called the "gimp" around the office if i ever suggested it for something, so i never have

Kye wrote at 2020-11-06 21:27:51:

GIMP devs and fans for 24 years when people bring the name up: "If you don't like the name, fork it."

What's the actual problem here?

sigzero wrote at 2020-11-06 21:41:32:

Only a "woke" one really.

Kye wrote at 2020-11-06 21:45:39:

I know what each of these words mean individually but I have no idea what you're trying to say.

a1369209993 wrote at 2020-11-07 05:43:19:

"Woke" is a colloquialism roughly analogous to "politically correct", not literally "awake" as in "woke up"; what they're trying to say (I assume, I'm not them or psychic) is that the problem is purely one of people manufacturing outrage over something innocuous, similar to eg, people claiming that using the standard Lena image for image compression examples is sexism.

Errsher wrote at 2020-11-06 21:05:13:

Do you work with a bunch of children?

srslygetalife wrote at 2020-11-06 21:58:42:

Or what? A special SJW forces squad will be sent to harass developers team and do some hostile takeover of project because some group wrongly believes they're morally allowed to do so?

I knew at least one lunatic person will bring this "_problematic_" issue of Gimp name that nobody else gives flying fckgw about.

romanoderoma wrote at 2020-11-06 23:02:31:

Right

Because windows, word, pages, apple, oracle, chrome, snort, evil-mode, mongodb, cockroachdb (etc. etc.) are all great names that make you think of real professionals at work that infact failed because they are childish

dheera wrote at 2020-11-07 00:28:19:

What is with this mess?

flatpak remote-add --user flathub-beta 
    https://flathub.org/beta-repo/flathub-beta.flatpakrepo

    flatpak make-current --user org.gimp.GIMP beta
    flatpak make-current --user org.gimp.GIMP stable

Why isn't it just

sudo apt-add-repository ppa:gimp/unstable
    sudo apt update && sudo apt install gimp

? Or:

wget https://gimp.org/releases/gimp-2.99beta.deb
    sudo dpkg -i gimp-2.99beta.deb

?

teddyfrozevelt wrote at 2020-11-07 02:28:13:

Installing it through Flatpak here is actually fewer commands than your apt example.

You just run this to add the repository,

flatpak remote-add --user flathub-beta

https://flathub.org/beta-repo/flathub-beta.flatpakrepo

Then this to install it

flatpak install --user flathub-beta org.gimp.GIMP

The next two commands let you switch between the beta and stable branches, which is something apt can't do.

jorvi wrote at 2020-11-06 21:30:40:

Only half on topic, but I wish GIMP garnered the same amount of industry support that Blender has. It has the bones to be great, it just needs a lot of UI and UX polish, and in open source those things always seem to attract the least passion (which is okay! if people work on something for free and of their own accord, they can pick whatever they want to work on). If some serious industry dough was being poured into GIMP, they could pay people to work on the less-fun bits.

Tbh they also should ditch the NIH attitude. Yes, sometimes Photoshop's behaviour or keybinds are more convoluted than GIMP's, but people have Photoshop's quirks ingrained and making the transition easier is what counts. Blender has an amazing 'industry keybinds' option.

billfruit wrote at 2020-11-07 03:46:14:

Photoshop is also not a great example of a well designed UI, and needing to replicate many of its idiosyncrasies in GIMP is pointless perhaps.

I learned GIMP first and got very used to its MDI interface, later on using Photoshop I found PS not as comfortable or easy to do the things I wanted to do.

tim44 wrote at 2020-11-06 23:03:02:

Yeah I agree about the keybinds. With blender, something as simple as left clicking to select objects can make a huge impact learning and using software when you don't have to reset your brain constantly. It can be tough to have like 3 different sets of keys used to navigate different 3d viewports.

Shared404 wrote at 2020-11-06 23:28:52:

I also like the way that on first run Blender will let you select the keybindings that you want to use.

That seems like a good compromise to me.

progman32 wrote at 2020-11-06 23:46:37:

FreeCAD also has several options for 3d navigation bindings. Really helped smooth the transition.

kzrdude wrote at 2020-11-07 00:01:10:

Isn't it more likely that Krita captures that?

m4rtink wrote at 2020-11-07 04:12:12:

Yeah - as with Blender or Libre Office of FreeCad I'm not sure more than one big pro-like open source project can be sustained.

And it seems Krita is moving in the right Blender-like direction to do just that.

snvzz wrote at 2020-11-06 20:44:53:

Why would they do this switch on a minor version number release?

Florin_Andrei wrote at 2020-11-06 20:49:02:

The N.99 pattern is usually meant to be "pre-release of (N+1).0".

And this is a development release anyway. Stable is still 2.10

snvzz wrote at 2020-11-06 20:52:41:

Oh, I see. Not sure where I got the idea I was running 2.99.1.