SketchUp 2016 is here....

[Mike Amos]

Quite calm mate, nil desperandum. What you said was that I can and I was pointing out that I can't. There are a few issues where this program is slower than v 2015 like when copying and pasting, this leads me to conclude v 2016 is in a state of flux and needs a maintainence release. I have however, not had a single bugsplat but that will no doubt happen down the line.

[Mike Amos]

I have now uninstalled v 2016, sick of the program not behaving properly and reducing the things I do to, no you cannot do that. Not seen the like on any other version.

[pbacot]

Anyone have anything they LIKE about 2016?

[Box]

@pbacot said:

Anyone have anything they LIKE about 2016?

Runs like a dream, like the new features, have yet to have a bug splat, much faster than 2015, better resolution on the hi def screen....................

[otb designworks]

Small Dimensions and context menu layer designation in Layout get big thumbs up from me.

[Garry K]

SU 2016 is the best version since Trimble took over Sketchup. I'd been working with SU8 - now Su 2016

[cotty]

@pbacot said:

Anyone have anything they LIKE about 2016?

The improved inference system e.g.

[pmolson]

I like that within a few hours I did not even notice a difference from previous version. The improvements are seamless enough that I do not trip over them doing my day to day work.

I like it!

[miggy]

@kaas said:

@miggy said:

...
I have a script that manipulates very many (20-30+) Google Earth terrain groups written back in SUv8...

My script copies and explodes lots of groups & components. I do see a positive difference in V16 and opening / closing the outliner doesn't make any real difference.

Maybe your v8 code hasn't been optimized? You do make use of
model.start_operation("name of operation",true)?
the true flag here disables the UI which could make you code run faster. Just a thought.

Thanks so much kaas for getting me to re-examine my scripts.
I have always used start_operation with disable_ui, but I have always believed that disable_ui didn't do anything useful - this because I have view.refresh in most of my loops!
Because the scripts are long-running, they would seem to be dead without view.refresh, especially because, most often, I also get the Windows 'not responding' in the title bar.
So, all said, a basic misunderstanding of view.refresh overriding disable_ui...

To clarify this for myself, I've written a test script and a mini model to test against.
It has really cleared out any doubts or misunderstandings I have had.
If anybody is interested I have attached both script and test model.
Any further clarifications on my comments below are truly welcomed - sorry if any of them seem obvious to others, but these were grey areas for me...

Also, if anybody has found a way to get Ruby/Sketchup to 'talk' to Windows and tell it that "I am busy so please don't lock out my status bar and console", I am very interested.
I have tried using threads as well as Win32 calls to various PeekMessage, GetMessage, etc., but to no avail, so far, ... the only thing that works is UI.messagebox, but that is a useless solution for long running (20-40 minutes) analysis scripts...

The net clarifications, for me, that came out of this script revisit and testing are:

1. The Layers window is never updated whilst a script is running - regardless of start_operation or value of disable_ui.
2. view.refresh overrides disable_ui.
3. view.refresh is required if the model view-port needs to 'move' during processing.
4. disable_ui doesdisable Outliner updates as well - good-bye attempts to automatically close it via script
5. status bar and console are notaffected by disable_ui
6. window 'not responding' doeslock status bar & console, but does not affect view.refresh

---

test_disable_ui.rb

---

test_disable_ui.skp

[Garry K]

Magnus

I always set disable_ui to true.
Some of my longer running scripts are still usually under a minute.
Regardless - inside the loop I do
Sketchup::set_status_text("Cabinet: #{count}", SB_PROMPT )

If you don't have a loop that provides a predetermined level of activity then you can use a timer and have that timer update the status. Say every 10 to 30 seconds. The status could show elapsed time and some form of guess to how far you are through the script.

[driven]

@miggy, run the gif to see how things differ on a mac...

and maybe move to the developer forum for further discussions...

john

[pipingguy]

I need to reiterate.......the software needs to be revised so the materials palette pops open when the paint tool is activated - like it used to do.