Vote for your favorite Qlik product ideas and add your own suggestions.
Just lose this feature. One of the biggest pains. Just about every IDE gives the ability to turn this OFF.
Also, why default to CamelCase on keywords ??? Look awful and makes reading scripts a pain
Just turn it all off and let me do my work.
or at least not not trigger after hitting ';'
and maybe also not include unsupported features like inputfield
or unimplmented call structures...
I agree. PLEASE let me turn this off.
Thank you for your feedback on ways to improve our product. While this is something we understand would be useful, it's not on the short-term roadmap. Please continue to show your support for this idea.
Please, after one year... just let me turn off these "no"-Intellisense feature !!!
@pedrobergo - I feel your frustration on a daily basis. I love your avatar!
Seems like this would be a simple fix - I'm wearing out my escape key constantly exiting the Intellisense popups.
Sigh, I would love to be able to toggle the intellisense. I do like having it there but sometimes the help is not helpful.
Please make it optional, thx.
It would be fantastic to have the functionality to disable this.
It is lovely that Qlik is trying to enhance their product so it is more friendly to non-IT users, but for anyone with a dev background it is an absolute nightmare. While any load script code can be outsourced to notepad++ or other text editors, the intellisense popup in the expression editor is awful and painful to use.
Its not that the Intellisense is all that bad. The problem is it constantly pops up (even on something that doesn't make sense, like a ";") and when you try indent with tab, or try click enter for a new line, it automatically inputs the first item on the auto complete list. Just let the default of intellisense be blank so what I type is what I get as a first priority. If I see the option / autocomplete value I want, I'd rather click the down arrow and navigate to it.
That would be first prize, but Qlik, please just make an option to disable it for now. Surely this isn't too difficult to implement? Can we get this in the interim so we can code faster? You can refine it in 3 years in 3 years, its fine. But keep your consultants happy and working faster. This is such a time waster and every consultant can agree
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.