script window show-hide

Edpa

Hi!

When you work with the script dialog box, the work in the DAZ is blocked until you close the script or hide the window.
When the script window is hidden (but not closed), then you can work in the DAZ. OK.
Does anyone know how to call the dialog window back  from the DAZ -  dialog.hide() =>dialog.show()  .
Buttons, keys and so on ... I know now the option with a timer only. 

Richard Haseltine

Rob goes into some detail here https://www.daz3d.com/forums/discussion/comment/657812/#Comment_657812 , see also https://www.daz3d.com/forums/discussion/65903 and https://www.daz3d.com/forums/discussion/82326 . Do note the warnings, however.

Edpa

Richard Haseltine, thanks.  I'll see this 

Edpa

It's strange that I didn't see it :)

My question this is the answer.  To use show () instead exec()   and welcome to DAZ panes.

mod=new DzDialog ()mod.show()//We can continue to work in DAZ

Do note the warnings, however.

OK,we will be more careful :)

But how return to the script after  hide()- I now do not know  yet:))

Edpa

It's strange, but if you write in the script " var mod = new DzDialog ()"  , the window will not open.

Chohole

Rob says

Don't use DzWidget::show()/DzWidget::hide(), use DzDialog::exec() and test its return value (e.g., http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/general_ui/simple_dialog/start) to know whether or not to then access the values of child widgets (which you should be storing in their own uniquely named variables) in the dialog.
 

Edpa

 I wrote  variable "mod" in one case, in another "var mod"  ( variable declaration). 

I get different results in both cases

mod=new DzDialog ()

...

 var mod=new DzDialog ()

 

Chohole

You need to understand some of the language basics ( http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/language_reference/start ). In particular, in you need to understand variable declaration and scope ( http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/language_reference/declarations/start )
---
The sample linked in the post immediately above this post is extremely simple, yet it shows how to perform several of the tasks you need. It shows: 1) how to limit the scope of your variables, 2) how to create a dialog, 3) how to add child widgets to that dialog, 4) how to cause that dialog to be presented to the user, 5) how to test whether the user accepted or rejected the dialog, and 6) how to access said child widget after the dialog has been accepted (or rejected for that matter) and use its value.
---
The links up-thread provide some detail around modeless (non-modal) dialogs, why they don't really work in this environment and why they are categorically not supported.

Edpa

You need to understand some of the language basics 

I can not go to all your links now. Message "Oops, something went wrong..." :) But my thanks

Chohole

hmm   lets try to get the links again  
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/language_reference/start
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/language_reference/declarations/start

Something went wrong with my copy/pasting methinkest.

Edpa

Yes, now it's fine :)

RajDarge

I know this is an old thread. I am also new to DazScript and even Javascript. But the var or lack thereof is just referencing that the variable is now global?  I tried the keyword "global" that javascript has, it doesn't seem to work (nor does "let" but "const" seems to work.) 

Also while have someones ear do the "hello = () =>"  and the spread functions work in the particular version of QTscript that DZ4.12 has?

I am trying to create my own panel of commonly used functions, but for that It would need to be modless. Clearly this is an unwanted end as it created pointless loop. 
I don't even really need this functionality I just wanted a window open so I could hit various buttons when I chose to run scripts without "file-> load script -> directory acess -> execute"

I think there is a way of attaching a script to a key shortcut, but usually I forget which keys are which, so a visual interface is what I need.