Discussions
Categories
- 384.6K All Categories
- 2.5K Data
- 556 Big Data Appliance
- 1.9K Data Science
- 451.4K Databases
- 222.1K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 32 Multilingual Engine
- 562 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 561 SQLcl
- 4K SQL Developer Data Modeler
- 187.5K SQL & PL/SQL
- 21.4K SQL Developer
- 296.9K Development
- 1 Application Development
- 18 Developer Projects
- 140 Programming Languages
- 293.6K Development Tools
- 112 DevOps
- 3.1K QA/Testing
- 646.2K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 193 Java Community Process
- 106 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 21 Java Essentials
- 167 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 206 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 537 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 178 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 236 Portuguese
"Turning Wheel" when accessing something
Answers
-
Nice catch. It was drawing a single frame of the busy animation when the timer ran out even if the task was finished. It won't be doing that any more. -Brian.
-
Oh, that's cool. At least, no flickering! Were the increased delays (see previous post) also due to that? Can I get a patched .jar to test it out before release, as an exception?
-
Ok so I've been using EA2 for a few weeks now and my conclusion is that I absolutely need to disable this feature. It pops when it shouldn't, sometimes for a fraction of a second. Also, it makes SQL Developer unusable in terminal server, since it's very graphic/bandwidth intensive (this is my biggest beef).
Will we be able to disable it in the final release ? If not we will have to keep the devs on 4.0 or switch them back to our previous tool.
Except for that, we really like this version though, so keep up the good work !
Thanks !
-
Ok, 4.1.0 fixed at least one thing: it doesn't flicker anymore. That said, I still don't understand how is it that "UI is inaccessible" yet it's possible to fully interact with the editor UI using keyboard, even while busy indicator is on. Are you absolutely sure that showing busy indicator on and off doesn't take MORE time than actual task sql developer is performing? Because it really feels like that, currently. Like the indicator is required to stay on for at least one second, even if the task is already finished.
Actually, like @2752746, I still want an option to disable it.
-
please start your own new thread, provide a test case