Show webdialog quicker?

Aerilius

If you do heavy calculations, then the webdialog freezes or doesn't update. In one of my plugins I wanted to display a waiting animation with execute_script and then loop over thousands of entities. When I paused ruby with sleep(5), it didn't help, it worked only with:
webdlg.execute_script("startProcess()") UI.start_timer(0.1, false){self.process()}

Chris Fullmer

I don't understand what that self.process in the block does.

But I tried to implement it and no luck.

Oh well, if I don't close it, then it will eventually load the image once SU has completed loading all the other scripts. Then the user will have to close the splash screen themselves.

driven

how about writing the image file in a .set_html.
AdamB does it in Goldilocks .rb and it's doing other stuff at the same time

john

jolran

A long shot. Saw something like this earlier today..

One cannot use a body onload? Like <body onload="jsFunction()">.
A <div> in the <body> with an ID.

Then a jsfunction in the script tag that grabs the div's ID and set the HTML inside?

Excuse my interuption, just wondering about this as well..

Chris Fullmer

OK, Aerilius got me on the right track, just took a little digging around on my part.

Here is what is working for me (sorry it looks hard to read in this little code box. Its only 4 lines of code, much of it being my html string.):

	splash_path = File.join( Install.base_path, "assets")
	@@splash_wd = UI;;WebDialog.new("MyProgram", true, "my_splash", 800, 600, 200, 200, true);
	UI.start_timer(0.1, false){@@splash_wd.show;@@splash_wd.set_html "<html><body><img border='0' src='#{splash_path}/logo_image.jpg' alt='Pulpit rock' width='800' height='600' /></body></html>"}
	UI.start_timer(2, false){@@splash_wd.close}

I open the webdialog, and set_html within the UI_time procedure. That is all it takes to get it to completely show everything. Then I use another timer to close the window after the splash has been on for a little while.

I'm guessing I don't even need to pass the html in as a string. It will probably load the file this way as well. i'll test.

Thanks everyone!

driven

chris, is it meant to work on macs?

Chris Fullmer

ok, even a little cleaner. This way I can use set_file to set a file to point to, instead of an html string.

	splash_path = File.join( Install.base_path, "assets", "splash.html")
	@@splash_wd = UI;;WebDialog.new("MultiFlux", true, "multiflux_splash", 800, 600, 200, 200, true);
	@@splash_wd.set_file splash_path
	UI.start_timer(0.1, false){@@splash_wd.show;}
	UI.start_timer(3, false){@@splash_wd.close}

It is just the webdlg.show that needs to inside the UI.start_timer procedure. Now it all loads and displays as desired.

Chris Fullmer

At this point, no unfortunately. It is not a Mac plugin. HOWEVER, I'm trying hard to mac it close to MAC friendly so we can get it up and running on Mac's someday.

Are all the methods I've used so far Mac friendly?

thomthom

@chris fullmer said:

Are all the methods I've used so far Mac friendly?

If you want the WebDialog to stay on top of the SketchUp window you want to use .show_modal under OSX. Under OSX that method doesn't produce a modal window like under Windows.

driven

and .set_html has a problem with local files... john

Chris Fullmer

Oh, ok. I'll put in the set_modal for future use. And I'll stick with my .set_file method then. Its cleaner in my ruby code and there is no reason at this point to load the html as a string.

Thanks guys!,

Chris

driven

it all works on the mac with set file.

Dan Rathbun

@chris fullmer said:

Oh, ok. I'll put in the set_modal for future use.

But not on PC...

   splash_path = File.join( Install.base_path, "assets", "splash.html")
   @@splash_wd = UI;;WebDialog.new("MultiFlux", true, "multiflux_splash", 800, 600, 200, 200, true);
   @@splash_wd.set_file splash_path
   UI.start_timer(0.1, false){
     RUBY_PLATFORM =~ /(darwin)/ ? @@splash_wd.show_modal() ; @@splash_wd.show();
   }
   UI.start_timer(3, false){@@splash_wd.close}

Chris Fullmer

Interesting, I would have just put it as modal for both. Modal just means it stays on top of all windows?

thomthom

@chris fullmer said:

Interesting, I would have just put it as modal for both. Modal just means it stays on top of all windows?

No - in the Windows world it means that the child window blocks any interaction in the parent window while it is open. It also means that .show_modal doesn't return until the webdialog is closed. (Like UI.inputbox - where you continue with the code after you prompted the user.)

But it's under OSX where the scheme suddenly change. Not use if it's a platform quick, or just an SU OSX quirk, but suddenly the window does not stay on top when using .show and .show_modal means "stay on top of parent" instead of actually being modal. It's an annoying difference as the behaviour displayed under OSX does not correspond to what the method name implies.

Modal window - Wikipedia

(en.wikipedia.org)