topic Re: Is it possible to keep the script window always open ? in QlikView

Is it possible to keep the script window always open ?

El_Davidus — Wed, 29 Jan 2020 14:28:45 GMT

During the code development it would be better if I could reload my code and keep the script window open. At the same time it would have to allow me to change or creat objects on my dashboard. Is this possible ?

Re: Is it possible to keep the script window always open ?

petter — Wed, 29 Jan 2020 14:56:18 GMT

In QlikView you can't. Unless you externalize the script by using

$(include=....\application-load-script-01.qvs);

$(must_include= .... );

So you can keep your script in a text editor like Notepad++, Atom, Sublime or the text editor of your choice...

Re: Is it possible to keep the script window always open ?

El_Davidus — Thu, 30 Jan 2020 11:08:34 GMT

Could you show me an example of how to do that ? Thank you.

Re: Is it possible to keep the script window always open ?

petter — Thu, 30 Jan 2020 13:11:38 GMT

If this is your load script - copy all of this into a text file named ExternalScriptExample.qvs:

Copy all of your load script into a file named the same as your application with a .qvs extension

Just have this single line in you load script that will read all of the load script text in from the external file:

Put this single line into your load script

Then your final environment will look like this:

This should be your environment

Obviously the left lower window will only show each time you hit the reload button on your toolbar in QlikView.

So you can at all times have both the UI and the load script open simultanously.

Re: Is it possible to keep the script window always open ?

petter — Thu, 30 Jan 2020 13:13:19 GMT

BTW - if you want QlikView syntax highlighting as you can see above in Notepad++ you can find the recipe for doing it here:

https://github.com/MattFryer/Qlik-Notepad-plus-plus/releases/tag/v2.6

Re: Is it possible to keep the script window always open ?

petter — Thu, 30 Jan 2020 13:30:51 GMT

A different approach could be to separate the UI from the data model and link the two by using a BINARY load in the UI load script:

1) App1_Data_Model.qvw
Only contains a load script and no user interface for the final application.

2) App2_UI.qvw
Only contains the UI and have a single load script statement that does a BINARY on the qvw-file of the Data Model.

You will have to start the QlikView Windows application twice with the two qvws so the load script of the Data Model won't block access to the UI. You will have to press reload twice to get updated data into the UI. First in the Data Model and after that has finished the reload of the UI. That way you won't have to use an external text-editor / IDE.

It will look something like this: