From david.thompson at kitware.com Tue Mar 21 15:27:12 2017 From: david.thompson at kitware.com (David Thompson) Date: Tue, 21 Mar 2017 15:27:12 -0400 Subject: [Cmb-users] Image-based tests on dashboards Message-ID: <40D90B51-8BC5-49E7-B19A-B1D8B1CBA716@kitware.com> Hi all, I talked to Cory about the issues SMTK+CMB are having with retina displays. 1. The MR Sean McBride has put forth ( https://gitlab.kitware.com/vtk/vtk/merge_requests/2567 ) only solves some of the issues people are having. Sean does not have a retina display to test with. 2. As we suspected, VTK uses vtkCocoaRenderWindow while ParaView uses QVTKWidget (the latter is aware of retina displays) but there are still issues that appear to be related to vtkWindowToImageFilter and/or offscreen rendering of test images. This is why ParaView tests fail in one mode (image is correct size but viewport parameters appear to be incorrect; too large by a factor of 2) while VTK tests fail in another (image size is incorrect, too small by half). This may also be confounded by some Apple APIs reporting/accepting sizes in points with others in pixels. 3. Since it doesn't appear that everything will be fixed in the next day or two unless Cory takes ownership (which he is avoiding :-), it might be best to disable image tests on talos and other retina-display machines. David From bob.obara at kitware.com Fri Mar 24 13:52:10 2017 From: bob.obara at kitware.com (Bob Obara) Date: Fri, 24 Mar 2017 13:52:10 -0400 Subject: [Cmb-users] Assigning Random Colors Message-ID: Hi All, We are in the process of improving the color support in CMB. The following is the proposed implementation. The new assign color operator allows the user to assign a single color to a selected set of model entities or iterate through a color pallet (assigning different colors to the selected entities as shown below: One suggestion I have is to remove the change defaults label since this could be a little confusion. Especially since default in " inherited default? means something completely different (basically to remove the explicit color from the selected entities and inherit color from the model?s default colors (vertex, edge, face, volume color). Another possible improvement would be to be able to select a category of model entities (like apply to all edges) instead of heaving to select them individually. Please let me know what you think. Bob Robert M. O'Bara, MEng. Assistant Director of Scientific Computing Kitware Inc. 28 Corporate Drive Suite 101 Clifton Park, NY 12065 Phone: (518) 881- 4931 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-03-24 at 1.35.49 PMEDT.png Type: image/png Size: 52886 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-03-24 at 1.39.22 PMEDT.png Type: image/png Size: 49579 bytes Desc: not available URL: From david.thompson at kitware.com Fri Mar 24 15:42:19 2017 From: david.thompson at kitware.com (David Thompson) Date: Fri, 24 Mar 2017 15:42:19 -0400 Subject: [Cmb-users] Assigning Random Colors In-Reply-To: References: Message-ID: <130C3E38-AC22-4B2B-8F9A-8DB45F307B5B@kitware.com> Hi all, > ... > One suggestion I have is to remove the change defaults label since this could be a little confusion. Especially since default in " inherited default? means something completely different (basically to remove the explicit color from the selected entities and inherit color from the model?s default colors (vertex, edge, face, volume color). The current [SMTK MR 473](https://gitlab.kitware.com/cmb/smtk/merge_requests/473) uses the label "inherited default", but I would like to change it to an icon (a circle with a slash through it) to match what Haocheng's working on for the tree view. That should help make things clear, although I agree that "change defaults:" label is confusing. > Another possible improvement would be to be able to select a category of model entities (like apply to all edges) instead of heaving to select them individually. That would be nice, especially if Steve gets us a bunch of snazzy, consistent icons. David From bob.obara at kitware.com Fri Mar 24 16:30:41 2017 From: bob.obara at kitware.com (Bob Obara) Date: Fri, 24 Mar 2017 16:30:41 -0400 Subject: [Cmb-users] Color Support Part 2 References: Message-ID: Hi All, As hinted in my previous email, we are going support inherited color support. For example if you want to have all your surfaces colored white and your edges colored blue - you will be able to select the edges node in the model tree and set its color to blue - as a result, all edges will be by default blue. If you then select edge 3 and set it to yellow you will have all your edges but edge 3 blue and edge 3 will be yellow - if you then change the edges node color to say red - all edges but edge 3 will be red and edge 3 will remain yellow. The issue this brings up is how to easily identify to the user that a model entity has an explicit color or is inheriting the color from the model tree. Below are two possible solutions: 1. Change the shape of the ?color swatch" associated with the model entity - in this case a rounded color swatch indicates that the entity is using an inherited color (in this case white) and a square shape indicates that it has an explicit color 2. keep the shape of the color swatch the same and use a hash pattern to indicate the color is inherited - a variation of this could be is to have just the icon (no border) to indicate that the color is inherited. Comments? Bob Robert M. O'Bara, MEng. Assistant Director of Scientific Computing Kitware Inc. 28 Corporate Drive Suite 101 Clifton Park, NY 12065 Phone: (518) 881- 4931 > > -- > Best regards > Haocheng > > Haocheng LIU > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4421 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test2D_circle-rec.png Type: image/png Size: 65315 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: test2D_dash-rec.png Type: image/png Size: 63396 bytes Desc: not available URL: From david.thompson at kitware.com Fri Mar 24 16:39:53 2017 From: david.thompson at kitware.com (David Thompson) Date: Fri, 24 Mar 2017 16:39:53 -0400 Subject: [Cmb-users] [Smtk-developers] Color Support Part 2 In-Reply-To: References: Message-ID: <54D91459-618D-4DF0-997B-745605BD927D@kitware.com> Hi Bob, > ... > Below are two possible solutions: > > 1. Change the shape of the ?color swatch" associated with the model entity - in this case a rounded color swatch indicates that the entity is using an inherited color (in this case white) and a square shape indicates that it has an explicit color > > 2. keep the shape of the color swatch the same and use a hash pattern to indicate the color is inherited - a variation of this could be is to have just the icon (no border) to indicate that the color is inherited. > > Comments? How about the attached? (Whether the swatch is square or round, a red slash over a white background indicates color is not set and thus inherited?) This is used by lots of other programs, so people understand what it means. David -------------- next part -------------- A non-text attachment was scrubbed... Name: assign-colors.pdf Type: application/pdf Size: 9983 bytes Desc: not available URL: From haocheng.liu at kitware.com Fri Mar 24 16:46:05 2017 From: haocheng.liu at kitware.com (Haocheng Liu) Date: Fri, 24 Mar 2017 16:46:05 -0400 Subject: [Cmb-users] [Smtk-developers] Color Support Part 2 In-Reply-To: <54D91459-618D-4DF0-997B-745605BD927D@kitware.com> References: <54D91459-618D-4DF0-997B-745605BD927D@kitware.com> Message-ID: Hi David, On Fri, Mar 24, 2017 at 4:39 PM, David Thompson wrote: > Hi Bob, > > > ... > > Below are two possible solutions: > > > > 1. Change the shape of the ?color swatch" associated with the model > entity - in this case a rounded color swatch indicates that the entity is > using an inherited color (in this case white) and a square shape indicates > that it has an explicit color > > > > 2. keep the shape of the color swatch the same and use a hash pattern > to indicate the color is inherited - a variation of this could be is to > have just the icon (no border) to indicate that the color is inherited. > > > > Comments? > > How about the attached? (Whether the swatch is square or round, a red > slash over a white background indicates color is not set and thus > inherited?) This is used by lots of other programs, so people understand > what it means. > I love your idea, the only concern I have is that since now we've already using a red X to indicating visibility is off, would a red slash be too strong? Ex (X / ). May be a 2px gray slash? > David > > _______________________________________________ > Smtk-developers mailing list > Smtk-developers at smtk.org > http://public.kitware.com/mailman/listinfo/smtk-developers > > -- Best regards Haocheng Haocheng LIU Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4421 <(518)%20881-4421> -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Fri Mar 24 16:54:25 2017 From: david.thompson at kitware.com (David Thompson) Date: Fri, 24 Mar 2017 16:54:25 -0400 Subject: [Cmb-users] [Smtk-developers] Color Support Part 2 In-Reply-To: References: <54D91459-618D-4DF0-997B-745605BD927D@kitware.com> Message-ID: <3D928A2D-79D3-4D78-8408-B392CEA7FEBA@kitware.com> Hi Haocheng, > ... the only concern I have is that since now we've already using a red X to indicating visibility is off, would a red slash be too strong? I would like to see us start using the font-awesome icons for visibility: http://fontawesome.io/icon/eye/ http://fontawesome.io/icon/eye-slash/ David From bob.obara at kitware.com Fri Mar 24 17:44:48 2017 From: bob.obara at kitware.com (Bob Obara) Date: Fri, 24 Mar 2017 17:44:48 -0400 Subject: [Cmb-users] [Smtk-developers] Color Support Part 2 In-Reply-To: <3D928A2D-79D3-4D78-8408-B392CEA7FEBA@kitware.com> References: <54D91459-618D-4DF0-997B-745605BD927D@kitware.com> <3D928A2D-79D3-4D78-8408-B392CEA7FEBA@kitware.com> Message-ID: <56007337-CCE2-4525-ACD0-7D19DF6B77A4@kitware.com> There are a new set of icons we will be using for CMB 5 (and invisible is not longer an eye with an x through it) - the reason I?m holding off is to make the two UI visually different so we know what version we are dealing with - especially since 4.x will be maintained between 6 to 12 months after 4.1 is released. Bob Robert M. O'Bara, MEng. Assistant Director of Scientific Computing Kitware Inc. 28 Corporate Drive Suite 101 Clifton Park, NY 12065 Phone: (518) 881- 4931 > On Mar 24, 2017, at 4:54 PMEDT, David Thompson wrote: > > Hi Haocheng, > >> ... the only concern I have is that since now we've already using a red X to indicating visibility is off, would a red slash be too strong? > > I would like to see us start using the font-awesome icons for visibility: > > http://fontawesome.io/icon/eye/ > http://fontawesome.io/icon/eye-slash/ > > David -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Fri Mar 31 13:41:53 2017 From: david.thompson at kitware.com (David Thompson) Date: Fri, 31 Mar 2017 13:41:53 -0400 Subject: [Cmb-users] Breaking SMTK change Message-ID: <76A6C4C5-B965-483E-91AD-78F0AA26B6A2@kitware.com> Hi all, I've merged a change that renames some common SMTK classes (SMTK MR 488); CMB and related builds will be broken for a short while until [CMB MR 342]() (and some others) are tested and merged. Class name changes: smtk::io::ExportJSON => smtk::io::SaveJSON smtk::io::ImportJSON => smtk::io::LoadJSON Operator name changes: export smtk model => save smtk model import smtk model => load smtk model David [CMB MR 342]: https://gitlab.kitware.com/cmb/cmb/merge_requests/342