Recent content by Tichij

try to beautify this example: create or replace view test_view as with function fd (p_datum in date) return varchar2 is begin return to_char(p_datum,'DD-MM-YYYY'); end fd; select fd(sysdate) datum from dual; At least I get "PL/SQL Beautifier could not parse text" error when try.

Hi Marco, Today I remembered this discussion in beta forum... 3 versions have already been released, almost 7 years have passed, after it... Maybe there’s a chance to see it in the patch release of 16 version?.. Thanks

This has been fixed in 16.0.2.2153, thanks!

I checked. Unfortunately, but still exists in 16.0.2.2150 :( However, I am pleased that this (and once again about font sizes) problem has been solved :)

Unfortunately, but still not fixed in 16.0.1...

Unfortunately, but still exists in 16.0.1...

This has been fixed in 16.0.1, thanks!

This time about font size in "Text" tab of Large Data Editor. If I understand correctly, the font face ant size from "Editor" font settings should be used here (in my case: Consolas, 10). If formatted text is opening (with applying syntax highlighting), e.g. XML, we have text in correct size...

I think I've found another oddity of PLSD 16. Actually, I spoted it in the beta stage, but I didn't have time to describe it, besides, I thought maybe someone else would describe it. Prerequisites. Two displays: one with display scale of 125% (main), second with display scale of 100%...

Yes, as already written by vlevi, Program Window tabs affected only

There are no error messages during startup. Both screenshots are made with identical appearance settings: "Light style" -> . If choosing an any different style, everything becomes correct. But with style all renders faster...

In ver. 15 active tab was in white, inactive - in grey. In ver. 16 both are in grey. How to distinguish which of them is active?

@Marco, I do not recall any communication from your side about service contract being „split into a cheaper "support contract" product and an explicit "version upgrade" product“. Could you provide a link or something where that was announced before? When in April we renewed our annual contract...

I have the same error too. We have valid support contract till 2027... :(

This has been solved in beta 5, thanks!