Toggle Wireframe (via CTRL 1 Pie Menu) is glitchy in the Zen Model viewport

[jonmoore1]

With Dara 2017.7.2, Toggle Wireframe behaves in an errant manner. It's hard to predict the behaviour but it seems to be connected to item selection (sometimes the toggle doesn't work at all, on other occasions it only toggles selected items).

Windows 10.

[adamohern]

It's probably not "errant" so much as just non-obvious due to the design of the commands in the ctrl-1 pie. In Zen, inactive meshes are not "same as active" or wireframe by default as they are in other parts of Modo, so what you are seeing is likely just background meshes not changing when the foreground mesh is changed.

Sent from my refrigerator console

On Jul 2, 2017, at 1:44 PM, jonmoore1 notifications@github.com wrote:

With Dara 2017.7.2, Toggle Wireframe behaves in an errant manner. It's hard to predict the behaviour but it seems to be connected to item selection (sometimes the toggle doesn't work at all, on other occasions it only toggles selected items).

Windows 10.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[jonmoore1]

With that being the case, I think artists would still find it useful to be able to disable Wireframes in an adhoc manner without having to resort to changing the Zen Model viewport to Zen Animate.

Zen is beginning to feel like a version of Modo within Modo and whilst most of the changes are positive it's in danger of losing some of it's "ZENness".

Breaking core Modo functionality/key bindings should only happen for good reason and preferably when a reasonable alternative is provided. Breaking the functionality of the CTRL's 1 to 6 Pie Menus is one of the areas that needs careful consideration IMHO (especially if it's a single item within a pie that gets broken).

I'm all for reasonable documented changes to key bindings as happens through the Zen preferences but care needs to be taken that you're not breaking core functionality without documenting it (or preferably providing an alternative to the broken functionality).

Much like Greg L, I've returned to using the standard Modo viewports but whilst utilising the key ZEN interaction models that won me over in the first place (V, G, middle mouse access to properties sheets, and K for tool properties). I'm not suggesting that others are reacting in a similar manner, but there is a fine line between feature enhancement and feature creep. Especially for a product that promises a stripped back user experience.

[adamohern]

Sometimes fewer words would get you further.

I will add it to the list.

Sent from my refrigerator console

On Jul 2, 2017, at 3:03 PM, jonmoore1 notifications@github.com wrote:

With that being the case, I think artists would still find it useful to be able to disable Wireframes in an adhoc manner without having to resort to changing the Zen Model viewport to Zen Animate.

Zen is beginning to feel like a version of Modo within Modo and whilst most of the changes are positive it's in danger of losing some of it's "ZENness".

Breaking core Modo functionality/key bindings should only happen for good reason and preferably when a reasonable alternative is provided. Breaking the functionality of the CTRL's 1 to 6 Pie Menus is one of the areas that needs careful consideration IMHO (especially if it's a single item within a pie that gets broken).

I'm all for reasonable documented changes to key bindings as happens through the Zen preferences but care needs to be taken that you're not breaking core functionality without documenting it (or preferably providing an alternative to the broken functionality).

Much like Greg L, I've returned to using the standard Modo viewports but whilst utilising the key ZEN interaction models that won me over in the first place (V, G, middle mouse access to properties sheets, and K for tool properties). I'm not suggesting that others are reacting in a similar manner, but there is a fine line between feature enhancement and feature creep. Especially for a product that promises a stripped back user experience.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[jonmoore1]

Seriously Adam, you shouldn't be so touchy about feedback (I don't think anything I wrote was rude or unreasonable anyway). I was simply attempting to provide detailed feedback and it touched on some other connected points as to the direction in which ZEN is developing.

It's just an opinion, you're free to ignore the bits you disagree with.

[adamohern]

No disagreement at all!

On Sun, Jul 2, 2017 at 3:19 PM, jonmoore1 notifications@github.com wrote:

Seriously Adam, you shouldn't be so touchy about feedback (I don't think anything I wrote was rude or unreasonable anyway). I was simply attempting to provide detailed feedback and it touched on some other connected points as to the direction in which ZEN is developing.

It's just an opinion, you're free to ignore the bits you disagree with.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/adamohern/mechanicalColor_Issue_Tracking/issues/195#issuecomment-312511444, or mute the thread https://github.com/notifications/unsubscribe-auth/AEFfL7oeXkoE8icY2PrufzUYSKF5RskVks5sJ-1GgaJpZM4OLpPs .

-- Adam O'Hern Mechanical Color LLC

(310) 692-4380

skype: adamohern hangouts: adam@mechanicalcolor.com linkedin: linkedin.com/in/adamohern

[adamohern]

Just tried to reproduce this, and it works predictably in both Zen and the default UI. It only changes the wireframe visibility state for active mesh items. As far as I can tell, this is just the way it works in all viewports, Zen or no.

[adamohern]

btw what's your skype or google address, @jonmoore1? Might be nice to voice chat sometime.

[jonmoore1]

That's odd ref the Wireframe toggle. On my install both active and inactive meshes have their wireframes disabled via the pie menu (maybe you have a custom tweak that's changing the behaviour). I work as standard with inactive same as active and only change from that for particular situations. That pie menu has always functioned for me in that manner as far back as I can remember.

As for Skype I only switch it on when I'm expecting a call. I'm a music producer/DJ as my main gig and get inundated with fan/spam across Soundcloud/Facebook etc, so I've banned live messaging apps from all of my connected hardware. Drastic measure I know, but it's the only way I can get anything done! :)

Anyway be great to have a chat. My Skype is connected to my music moniker - leftsidewobble@live.com - let me know when you want a natter by email and I'll be sure to switch my Skype on.

[adamohern]

"Same as active" is disabled by default in modo. I know this because I reset my preferences at least ten times a day :D

So that's not a tweak on my part, but yours, my friend ;)

Let's do catch up sometime. Are you in Germany or something?

Adam

On Tue, Jul 11, 2017 at 2:46 PM, jonmoore1 notifications@github.com wrote:

That's odd ref the Wireframe toggle. On my install both active and inactive meshes have their wireframes disabled via the pie menu (maybe you have a custom tweak that's changing the behaviour). I work as standard with inactive same as active and only change from that for particular situations. That pie menu has always functioned for me in that manner as far back as I can remember.

As for Skype I only switch it on when I'm expecting a call. I'm a music producer/DJ as my main gig and get inundated with fan/spam across Soundcloud/Facebook etc, so I've banned live messaging apps from all of my connected hardware. Drastic measure I know, but it's the only way I can get anything done! :)

Anyway be great to have a chat. My Skype is connected to my music moniker

• leftsidewobble@live.com - let me know when you want a natter by email and I'll be sure to switch my Skype on.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/adamohern/mechanicalColor_Issue_Tracking/issues/195#issuecomment-314581757, or mute the thread https://github.com/notifications/unsubscribe-auth/AEFfL_2qXsPIy7QMzYs4cot64xVMs6oqks5sM-0xgaJpZM4OLpPs .

-- Adam O'Hern Mechanical Color LLC

(310) 692-4380

skype: adamohern hangouts: adam@mechanicalcolor.com linkedin: linkedin.com/in/adamohern

[jonmoore1]

Definitely need a good old fashioned voice call as we're talking cross wires again. I set my preference to 'same as active' as standard and with that preference set, the pie menu disables all wireframes not just the active mesh. :)

I'm a Brit and contactable pretty much anytime within reason.

[adamohern]

Hangouts: adam.ohern@gmail.com Skype: adamohern

On Tue, Jul 11, 2017 at 6:09 PM, jonmoore1 notifications@github.com wrote:

Definitely need a good old fashioned voice call as we're talking cross wires again. I set my preference to 'same as active' as standard and with that preference set, the pie menu disables all wireframes not just the active mesh. :)

I'm a Brit and contactable pretty much anytime within reason.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/adamohern/mechanicalColor_Issue_Tracking/issues/195#issuecomment-314586592, or mute the thread https://github.com/notifications/unsubscribe-auth/AEFfLxQEfI9MLaiIqteiU1_WOBsi7Ohpks5sM_KWgaJpZM4OLpPs .

-- Adam O'Hern Mechanical Color LLC

(310) 692-4380

skype: adamohern hangouts: adam@mechanicalcolor.com linkedin: linkedin.com/in/adamohern