HyperMesh 2019 Assembly View

That is an inovation of a certain altair's developer /emoticons/default_sad.png' srcset='/emoticons/sad@2x.png 2x' title=':(' width='20' />

Thanks tinh,

I had feared as much, but hopeful that there was a checkbox lying around somewhere

Yes, you can right click on model view and a menu item will lead you to a dialog where you can tick on a check box to show assemblies

That's the configuration browser isn't it? 

So that allows me to see / hide assemblies within the model view, but not the ability to expand assemblies within the model view

Yes could you try it?

That is an inovation of a certain altair's developer /emoticons/default_sad.png' srcset='/emoticons/sad@2x.png 2x' title=':(' width='20' />

Yes, this is an 'idiot' feature of version 2019

Hey Tinh, 

Tried that, and it doesn't do as we want I'm afraid. 

Another little thing I've just noticed. Everytime you go to the 'Assembly Viewer', it switches the mesh view to 'By Assem', which is rather annoying...

Hi

When you enter the dialog 'browser cinfiguration', did you see any check box named 'Assembly Hierarchy'?

Or you just see 'Assembly'?

Sorry to ask too detail because I don't have hm2019.

Dear All,

Please check below video to gain benefit, if you use the Part-Browser instead of assemblies.

Unable to find an attachment - read this blog

Hi Rahul, 

Thank you for the video, I learnt things that I wasn't expecting.

But the problem still stands - I can't open the part browser in the other side, as we have our utility menu there. 
The Assemblies don't expand in the Model Browser

The Part Assemblies don't expand in the Model Browser. 

The solution of opening another view on the right task bar just won't work for what we do. 

@tinh - Enitities - Assemblies

Hi @ezzymn,

You can disable auto color by entity type in the Browser Configuration dialog.  Uncheck 'Autocolor visualization mode' under Local Options.

It is worth noting that Assembly View of Model browser shows only Assemblies and Components, so it is not possible to interact with entities such as Groups, Properties and Materials.  In Part browser, dedicated columns show you the Component, Property and Material associated with the Part.  See the image below:

<?xml version="1.0" encoding="UTF-8"?>

Since Parts may not be relevant to your workflow, feel free to contact me via DM so I can learn more about your use case and offer additional assistance. 

Cheers,

Joe

 

 

@tinh - Enitities - Assemblies

I thought so.

Could you please open command window (menu Views>command window) and then enter below command:

set ::env(HMBR_CONTENT_HIDE_ASSEMBLYHIERARCHY_FOLDER)

and then take a screenshot?

I want to see the settings on hm2019

Hi @ezzymn

I seem to find out where the settings can be customized.

It's exactly stored in below files:

<install dir>/hm/scripts/br/views/model/regular/

Please copy the folder 'regular' and zip it then post it here. I will modify settings and send back to you.

Don't modify it by yourself because it's easy to be fault.

Hi @tinh, 

set ::env(HMBR_CONTENT_HIDE_ASSEMBLYHIERARCHY_FOLDER)

can't read '::env(HMBR_CONTENT_HIDE_ASSEMBLYHIERARCHY_FOLDER)': no such variable

I feel like the functionality might be removed, but I appreciate you having a look. I've tried the crude attempt to copy over the 2017 files, but that segmentation faulted. 

Many Thanks

Eric 

Unable to find an attachment - read this blog

@ezzymn, 

As you have correctly deduced, there is no option to show the Assembly hierarchy in 2019.  Depending on the version of 2019 you are using, I can provide a patch that brings back legacy behavior - let me know if you are interested.  As mentioned in my previous post, I am still keen to meet to discuss our the paradigms and workflows we have in 2019.

As a FYI, legacy behavior will return in 2020.  Additionally, Part hierarchy has never been shown in Model View, though this may change in the future.

Hi @tinh, 

 

set ::env(HMBR_CONTENT_HIDE_ASSEMBLYHIERARCHY_FOLDER)

can't read '::env(HMBR_CONTENT_HIDE_ASSEMBLYHIERARCHY_FOLDER)': no such variable

 

I feel like the functionality might be removed, but I appreciate you having a look. I've tried the crude attempt to copy over the 2017 files, but that segmentation faulted. 

 

 

Many Thanks

Eric 

Hello

I modify some things

Please copy these modified files and overwrite the old ones

If something's wrong, simply backup original files and let me know issues

Unable to find an attachment - read this blog

@tinh, Thank you I'll try and find some time today to try it. 

@joek, Sorry I haven't been ignoring you. I'll give this try from tinh a go, and if that doesn't work then a patch would be much appreciated

Hi @tinh, it works ! Thank you!  /emoticons/default_tongue.png' srcset='/emoticons/tongue@2x.png 2x' title=':P' width='20' />

Hi @tinh, in 'Assemblies view' I can create Assembly/Component within each Assembly:

But with 'Model view' (your modified version) I can not do that (maybe the same issue in initial version):

Do you think it's possible to customize this context menu by adding 'Create ...' ?

Thanks,

Yes, I do.

I will try hooking the menu. Just need a little time to find where it is.

@joekI know you guys don't like to discuss product road maps on a forum like this, but will be there be another major dot release of 2019 HW suite (like 2019.2) before arrival of 2020 release (if we go by 2019 release time frame, it could happen almost 5-6 months in to next year)? There are lot of bugs and features missing, especially in HWX. I realize not all can be added or rectified but I am hoping for another major dot release to make HWX little more usable until 2020 release.

Thanks...

@joekI know you guys don't like to discuss product road maps on a forum like this, but will be there be another major dot release of 2019 HW suite (like 2019.2) before arrival of 2020 release (if we go by 2019 release time frame, it could happen almost 5-6 months in to next year)? There 

I deem persons before become HM developers should be HM users, so they could upgrade software better. Anyway it's a really good software because we can do almost things by Tcl /emoticons/default_wink.png' srcset='/emoticons/wink@2x.png 2x' title=';)' width='20' />

 

I deem persons before become HM developers should be HM users, ..../emoticons/default_wink.png' srcset='/emoticons/wink@2x.png 2x' title=';)' width='20' />

Yes, it's the ideal case. But in reality, that is not always true.

The 'Model view' of 2019.0 & 2019.1 (with useless Assembly tree)  is a typical example of developers who don't take care of what users want.

Yes, I do.

I will try hooking the menu. Just need a little time to find where it is.

Hi Mr. @Q.Nguyen-Dai

I seem to find it in hm2017

I don't have hm2019, could you please zip folder <install_dir>/hm/scripts/br  and post here.

In your gmail box :-)

/emoticons/default_smile.png' srcset='/emoticons/smile@2x.png 2x' title=':)' width='20' /> it is quite similar to hm2017

I am sure that context menu settings of modelview are stored in .../br/views/common/menucreate.xml

There are 3 menu items existing in that file: Assembly, Component, Multibody

Same as hm2017

Could you try closing HM, delete hmsettings.tcl , hmmenu.set then open it again.

Other tests:

1) right click on a white space to see full menu 'Create', are there Assembly, Component, Multibody in the menu?

2) check if it is invisible by enter to cmd window:

::hmbr::createentity::isVisible Assemblies content ::hmbr::createentity

above should return 'true'

If it returns 'false', we will debug it later.

Before enter the command, pls left click on an assembly on modelview.

Hi,

I think I found it.

In file .../br/common/operations/createentity.tcl

Please open it and go to line 70:

if { $types == 'Assemblies' && $view == 'assemhierarchy' } {

Please change it to be same as hm2017:

if { $types == 'Assemblies' } {

In hm2019 the line indicates that only assemblyview will show menu items Assembly, Component, Multibody

Wow, wonderful!

Thank you!

@tinh : Could you do the same customization for Hyperview? Thanks