Bug - font color invalid

[Hilarion]

I set my PL/SQL Developer (v 10.0.2) to use non-default font and background colors. I prefer black background with bright font (Lime) instead of standard black on white.
Unfortunately "DBMS Scheduler" window uses black font in some places regardless of my settings, so I get black font on black background.

I just noticed one more thing which may be or may be not related to the problem above:
In Tools > Preferences > User Interface > Fonts > Editor there's "Main Font..." button which allows setting a font that affects many PL/SQL Developer interface aspects (definitely not only Editor windows) that among others allows selecting font colour. That setting is not preserved (always reverts to black). Maybe this is intended behaviour (that this option should only allow font typeface change, not the colour) but in that case it's slightly misleading.

I work on Windows 7 64-bit (all available patches installed) with UAC turned on (but PL/SQL Developer settings are stored in my profile, so file access rights should not be an issue and I did not notice any problems with other program settings not being preserved).

Edit:
The black font colour use in "DBMS Scheduler" window changes in different window work mode, eg. when adding new job, more fields use black font colour than when we only view an existing job data.

 

[Marco Kalter]

We'll check it out.

 

[Hilarion]

Changelog for version 10.0.3 suggests that the problem is fixed.
It seems so, but apparently something went wrong with that fix and introduced much worse problem (or at least I did not observe it in previous versions).

The main DBMS Scheduler window opens OK and I can browse (expand and collapse) it's object list tree without problems.
Selecting existing objects by left-clicking them in the tree seems to work OK (but it seems to work a bit slower than before for some object types, eg. jobs).
Right clicking a tree node and selecting "New" works OK too (canceling out of such window is a bit sluggish thou).
The problem is when you use main Objects window to view or edit an existing scheduler object when you did not open any DBMS Scheduler windows before (in current PL/SQL Developer session or even in current DB connection). This action takes a lot of time. Much more than I remember from previous versions. During that time PL/SQL Developer is unresponsive.

 

[Marco Kalter]

Response is instantaneous when I try this. To obtain some more diagnostic information, can you modify the shortcut and add the DebugSQL parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" DebugSQL

Reproduce the problem and send me the debug.txt file that is generated in the PL/SQL Developer directory or in the %APPDATA%\PLSQL Developer directory (e.g. C:\Users\\AppData\Roaming\PLSQL Developer).

 

[Hilarion]

OK. I did some playing around and it looks like I was wrong.
What has changed since last PL/SQL Developer version is that some of our DBMS scheduler jobs got very much job runs and it seems that when you view a job properties, the whole job runs history gets loaded which takes a lot of time for a job that's set to run every minute and is there for almost a month.
My bad. Not a bug. I'll have to see why is this data not getting purged as it's supposed to.
Yet still it'd be nice if those "Run details" and "Logs" tabs got populated on tab selection and/or with some default filtering (like only last few days) and/or load paging (like in SQL Window results).