The Jade 2025 release focuses on modernising the developer experience and helping you build faster, smarter, and more scalable applications.
The changes made to F11 is a step backwards and I'm not sure why these were not changed as an 'opt-in' rather than the default. I know there is a workaround to make it work like it did before but can we just change it back please.
Sam Stokell
Hi
I'll back Sam up here - any new functionality should be Opt-In and not Opt-Out.
And with users that have several environments that they go into on a regular basis this has caused a huge amount of time to Opt-Out in order to retain the way that it has always been.
I believe this new functionality was aimed at the ability to select an Attribute or Constant within the Class browser. I was able to do everything else that the new functionality provides prior to this change except for the direct selection of the Attribute or Constant. I also think that the behaviour between selecting a Method (or Routine) should be considered differently from the other SchemaEntity types.
I also don't like using the "Reuse Same Method Source Window for All" as it just adding clutter to my IDE view (and being very visual the colours really distract me) and, in most cases, I just want to see the single method source in full view.
For years, like several other's in our community, I have pressed F11 to view the full method source and, if necessary, then use the Methods | References if I need to do references to the methods. And I honestly don't think I've ever wanted to go directly to the Class Browser for a Method.
Please also note that the F12 behaviour on a method has also changed, yet this was not documented. When the Class Browser was open and a method selected, the F12 key opened up a method irrespective of where the cursor was in the method. However, now, if the cursor is on a method, then it will open up the method that the cursor is on, not the method that is selected in the browser.
Hi Sam,
Have you tried turning on "Reuse Same Method Source Window For All" on the Source Management tab of your user preferences?
This is a quicker way to get similar behaviour to pre 2025 releases, at least for method source navigation, and on a plus side as you navigate through multiple methods you end up with only one form to close when you want to return to your starting point as well as a "quasi call stack" in the top half of that form which allows you to quickly jump backwards and forwards through that stack of methods through which you have navigated.
I've had this reuse method source option enabled since it was first added to the JadePlatform and find it a much better way to work when navigating through several levels of method calls.
Cheers,
BeeJay.
Hi Charlie,
Thanks for following up. Here's what's actually changed with F11 in 2025 compared to 2022, and why it's a step backwards for us.
F11 on a method used to open the method straight into a Method Editor Window. In 2025 the default F11 now opens a Class Browser with the method selected instead, so you get an extra step before you're actually in the method source. This is the main pain point.
Shift+F11 no longer differentiates for methods. It behaves the same as F11 now, when previously it was expected to behave differently (open the Method Editor Window). That distinction has been lost.
Shift+F11 on primitive and type properties now takes an extra hop too. In 2022 this went straight to the Primitive Type Browser (or Class Browser of the type). In 2025 it instead opens the Class Browser where the property lives, with the property selected, so you have to navigate one more step to get to the type itself.
Double F11 isn't documented anywhere, and we believe it's just mimicking Shift+F11 behaviour, which adds to the confusion.
The workaround we've found is rebinding F11 to the new LegacyShowSymbolBehaviour action (Alt+F11 by default) in Preferences, Shortcut Keys, Editor category, which restores the old direct-to-editor behaviour. But given this was the default for the life of JADE up to 2022, we'd like it reverted to being the default again, with the new ShowSymbolInfo/OpenBrowserAndNavigateToRootDefinition behaviour available as an opt-in for anyone who prefers it.
Sam
Hi Sam,
Could you please let me know which of the F11 changes are causing issues for you? Is there a specific aspect of the new behaviour that you find less intuitive or less useful than the old (JADE 2022) behaviour? Any details you can provide will help me better understand your concerns.