From adsiwalkar at cdac.in Tue Jul 11 04:23:11 2017 From: adsiwalkar at cdac.in (adsiwalkar) Date: Tue, 11 Jul 2017 13:53:11 +0530 (IST) Subject: [Paraview-developers] Regarding to customize Paraview Message-ID: <761268190.458.1499761391640.JavaMail.open-xchange@webmail.cdac.in> Dear sir, I tried to customize paraview , I download the source code and tried to build it on Centos but I got the error 1 "Unable to find load file ParviewQt " and 2 "Unknown cmake command pv_find_package_qt I unable to solve this issue even I install Qt5.9.1 but still I got the same error. Please also Let me know How to 1. Add new menus /filter or hide existing menus/filters 2. Add custom GUI by adding or removing existing functionalities Thanks and regard Ashish siwalkar ------------------------------------------------------------------------------------------------------------------------------- [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Jul 11 10:46:25 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 11 Jul 2017 10:46:25 -0400 Subject: [Paraview-developers] Regarding to customize Paraview In-Reply-To: <761268190.458.1499761391640.JavaMail.open-xchange@webmail.cdac.in> References: <761268190.458.1499761391640.JavaMail.open-xchange@webmail.cdac.in> Message-ID: Ashish, Can you post the full error and information about the stage when you encounter it? Is that the first error message you're seeing? What version of ParaView source have you downloaded and how? On Tue, Jul 11, 2017 at 4:23 AM, adsiwalkar wrote: > Dear sir, > I tried to customize paraview , I download the source code and tried to > build it on *Centos* but I got the error > > 1 "Unable to find load file ParviewQt " and > 2 "Unknown cmake command pv_find_package_qt > > I unable to solve this issue even I install Qt5.9.1 but still I got the > same error. > Please also Let me know > > How to > > 1. Add new menus /filter or hide existing menus/filters > 2. Add custom GUI by adding or removing existing functionalities > > Thanks and regard > Ashish siwalkar > > > > ------------------------------------------------------------ > ------------------------------------------------------------------- > [ C-DAC is on Social-Media too. Kindly follow us at: > Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] > > This e-mail is for the sole use of the intended recipient(s) and may > contain confidential and privileged information. If you are not the > intended recipient, please contact the sender by reply e-mail and destroy > all copies and the original message. Any unauthorized review, use, > disclosure, dissemination, forwarding, printing or copying of this email > is strictly prohibited and appropriate legal action will be taken. > ------------------------------------------------------------ > ------------------------------------------------------------------- > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Tue Jul 18 09:36:00 2017 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Tue, 18 Jul 2017 09:36:00 -0400 Subject: [Paraview-developers] Partial Dashboard results Message-ID: Hi all, There are a lot of partial results from the dashboards last night where builds were interrupted. This is because we had severe thunderstorms go through and the power flickered a few times. Apparently we have some dead UPS batteries and a couple of dashboard machines that aren't on a UPS. Buildbot should reschedule the interrupted builds, but just be aware that there may be partial results on CDash for your branches that will never complete. Shawn -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Jul 18 11:49:27 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 18 Jul 2017 10:49:27 -0500 Subject: [Paraview-developers] Partial Dashboard results In-Reply-To: References: Message-ID: Shawn, It looks like vall is still down. Thanks, Cory On Tue, Jul 18, 2017 at 8:36 AM, Shawn Waldon wrote: > Hi all, > > There are a lot of partial results from the dashboards last night where > builds were interrupted. This is because we had severe thunderstorms go > through and the power flickered a few times. Apparently we have some dead > UPS batteries and a couple of dashboard machines that aren't on a UPS. > Buildbot should reschedule the interrupted builds, but just be aware that > there may be partial results on CDash for your branches that will never > complete. > > Shawn > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From amine.aboufirass at gmail.com Sat Jul 22 02:02:52 2017 From: amine.aboufirass at gmail.com (Amine Aboufirass) Date: Sat, 22 Jul 2017 08:02:52 +0200 Subject: [Paraview-developers] Control paraview interactively using IDLE? Message-ID: I am trying to control Paraview interactively using IDLE. This would involve sending commands from IDLE and seeing the changes occur in Paraview. I would rather not use the in-Paraview python shell. So far, I have succeeded in importing the Paraview modules (simple, servermanager?etc) from IDLE. However the commands sent do not reflect in Paraview. For instance: >>> from paraview.simple import *>>> cone = Cone()>>> Show()>>> Render() does indeed create a cone. However the cone is output to a new, independent OpenGL window, and not the Paraview GUI. Is it possible to control Paraview interactively using IDLE? If so how to accomplish this? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Sat Jul 22 09:44:01 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Sat, 22 Jul 2017 09:44:01 -0400 Subject: [Paraview-developers] Control paraview interactively using IDLE? In-Reply-To: References: Message-ID: Amine, As far as I am aware, I'm afraid that you will not be able to control the paraview UI from an external Python. The ParaView GUI owns its internal Python environment, and the Python environment (including the paraview.simple module) does not have a direct reference to the ParaView GUI side of things. It may appear that you are controlling the GUI via Python in ParaView's Python console, but that happens indirectly. Your Python script change objects in ParaView, but the UI changes you see are the result of observers in the UI listening for updates to ParaView's state and updating themselves based on the new values. The Python script does not control the UI elements directly. The reason you see a separate render window is because running pure Python scripts through pvpython or pvbatch, which are basically Python executables with some additional path information, is explicitly supported - the lone window appears when rendering commands are issued in the script. What you have done with an external (and compatible) Python is also supported, but it does not let you invoke the GUI application, let alone control it. Hope that helps, Cory On Sat, Jul 22, 2017 at 2:02 AM, Amine Aboufirass wrote: > I am trying to control Paraview interactively using IDLE. This would involve > sending commands from IDLE and seeing the changes occur in Paraview. I would > rather not use the in-Paraview python shell. > > So far, I have succeeded in importing the Paraview modules (simple, > servermanager?etc) from IDLE. However the commands sent do not reflect in > Paraview. For instance: > >>>> from paraview.simple import * >>>> cone = Cone() >>>> Show() >>>> Render() > > does indeed create a cone. However the cone is output to a new, independent > OpenGL window, and not the Paraview GUI. > > Is it possible to control Paraview interactively using IDLE? If so how to > accomplish this? Thanks > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From sebastien.jourdain at kitware.com Mon Jul 24 16:45:46 2017 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Mon, 24 Jul 2017 14:45:46 -0600 Subject: [Paraview-developers] pvserver with multiple clients In-Reply-To: References: Message-ID: I'm not seeing where you configure a server to allow several clients to connect? Maybe I'm missing the question or the problem as once the script is done, the client should disconnect from its server and properly exit like you seems to describe. Seb On Wed, Jun 28, 2017 at 4:52 PM, Gr?gory Zaccaro wrote: > I'm trying to run a pvserver(Paraview 5.3) with multiple clients. > I have a little problem when running the server. > > Here is how I launch locally all the processes on a .bat file : > start mpiexec.exe -np 1 pvserver.exe --server-port=11111 > start mpiexec.exe -np 1 pvserver.exe --server-port=11112 > start pvbatch.exe script_box.py DESKTOP-HAFBULV 11111 > start pvbatch.exe script_box.py DESKTOP-HAFBULV 11112 > > With "script_box.py" doing the connection and some stuff : > from paraview.simple import * > import sys > > server_name = sys.argv[1] > server_port = int(sys.argv[2]) > > connection = servermanager.Connect(server_name, server_port) > > servermanager.LoadPlugin('...') > > # create a new 'Box' > # create a new 'Triangulate' > # create a new 'Clean' > ... > > Whenever a client gets connected, the script is executed but the server > exits immediately after that, > the problem is that all the others clients lose connections and the server > disconnect. > > I don't call servermanager.Disconnect() and I tried to run pvserver with > --multi-clients but it has no effect, > > Is there is any specific way to manage multiple connections with a > pvserver ? > > Any help would be appreciated ! > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Jul 27 08:47:27 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 27 Jul 2017 08:47:27 -0400 Subject: [Paraview-developers] Using "fusion" style on OsX by default Message-ID: Folks, I wanted to see what people thought about using the "fusion" style (same in Linux) on OsX instead of the current OsX style used by Qt. Attached are screenshots compare the two styles on a Mac. As you can see, "fusion" is more compact with more well aligned widgets. The Properties panel on both has been resized horizontally so that it is as minimum size possible before a horizontal scrollbar shows up. Note how wide it has to be with macOS style as against Fusion. Utkarsh -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-07-27 at 8.37.08 AM.png Type: image/png Size: 1193466 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: EditGridAxesDialog.png Type: image/png Size: 527443 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SettingsDialog.png Type: image/png Size: 831563 bytes Desc: not available URL: From andy.bauer at kitware.com Thu Jul 27 09:45:14 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 27 Jul 2017 09:45:14 -0400 Subject: [Paraview-developers] Using "fusion" style on OsX by default In-Reply-To: References: Message-ID: I like the Fusion style a bit better. I think it would be a good idea to get input from somebody with poor vision. On Thu, Jul 27, 2017 at 8:47 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Folks, > > I wanted to see what people thought about using the "fusion" style (same > in Linux) on OsX instead of the current OsX style used by Qt. Attached are > screenshots compare the two styles on a Mac. > > As you can see, "fusion" is more compact with more well aligned widgets. > The Properties panel on both has been resized horizontally so that it is as > minimum size possible before a horizontal scrollbar shows up. Note how wide > it has to be with macOS style as against Fusion. > > Utkarsh > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Jul 27 12:32:17 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 27 Jul 2017 12:32:17 -0400 Subject: [Paraview-developers] ParaView 5.4.1-RC2 available for download Message-ID: On behalf of the ParaView development team, I am happy to announce that ParaView 5.4.1-RC2 is available for download. Binaries and source code are available from www.paraview.org/download Note that ParaView 5.4.1-RC1 had a critical bug that was identified and resolved internally before binaries and source code were made available for download, so we have skipped straight to RC2. The 5.4.1-RC2 bug fix release addresses a number of problems, including: * The black render window observed on some systems when FXAA was enabled or an object's opacity was less than 1 has been fixed. * Field output for cells with non-straight edges has been corrected. * Derivatives for quadratic triangles are now computed correctly. * A bug that occurred when generating a Catalyst script with no images output has been fixed. * A problem with writing animations as AVIs was fixed. * Logic in the CGNS reader was updated to correctly read all solution nodes for each centering type when FlowSolutionPointers are missing. * Fixed crash in CGNS reader when moving forward in time. * Fixed problem with long-running animations not advancing past a certain number of time steps. * Resolved issue where changing one file path in the state file loader "Choose File Names" dialog also changed the file paths of other files with the same type. * Addressed problem with enumerated property dependencies in ParaViewWeb. * Added ability to change the font size in the ParaView user interface. * Fixed BoxLib3D file reader. * State files now properly support files with relative paths. * Removed inappropriate scalar bar scaling when saving large screen shots. Please report any problems you find with this release candidate on the mailing list or on the bug tracker at https://gitlab.kitware.com/paraview/paraview/issues - Cory -- Cory Quammen Staff R&D Engineer Kitware, Inc. From wascott at sandia.gov Thu Jul 27 13:06:10 2017 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 27 Jul 2017 17:06:10 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style on OsX by default In-Reply-To: References: Message-ID: <646e80ed857c451094b71ad39e6554de@ES01AMSNLNT.srn.sandia.gov> Assuming fusion is on the right side, I also like that better. What is important is that the fonts aren?t decreasing in size. Ditto the icons. We are just tightening up empty space. My $0.02 Alan From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Andy Bauer Sent: Thursday, July 27, 2017 7:45 AM To: Ayachit, Utkarsh (External Contacts) Cc: ParaView Developers Subject: [EXTERNAL] Re: [Paraview-developers] Using "fusion" style on OsX by default I like the Fusion style a bit better. I think it would be a good idea to get input from somebody with poor vision. On Thu, Jul 27, 2017 at 8:47 AM, Utkarsh Ayachit > wrote: Folks, I wanted to see what people thought about using the "fusion" style (same in Linux) on OsX instead of the current OsX style used by Qt. Attached are screenshots compare the two styles on a Mac. As you can see, "fusion" is more compact with more well aligned widgets. The Properties panel on both has been resized horizontally so that it is as minimum size possible before a horizontal scrollbar shows up. Note how wide it has to be with macOS style as against Fusion. Utkarsh _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Jul 27 13:14:24 2017 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 27 Jul 2017 17:14:24 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style on OsX by default In-Reply-To: <646e80ed857c451094b71ad39e6554de@ES01AMSNLNT.srn.sandia.gov> References: <646e80ed857c451094b71ad39e6554de@ES01AMSNLNT.srn.sandia.gov> Message-ID: I agree that I like the fusion style better for the same reason as Alan. In fact, I remember complaining several years ago about how much space was introduced into the GUI during some library update or another. My only reservation is that the tighter style might be more off-putting to new users (exaggerates the airplane-cockpit syndrome). However, the current GUI for the Windows executable looks just as tight, and that does not seem to be an issue. (According to download counts, windows users outnumber Mac and Linux by a large margin.) -Ken From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Scott, W Alan Sent: Thursday, July 27, 2017 11:06 AM To: Bauer, Andy (External Contacts) ; Ayachit, Utkarsh (External Contacts) Cc: ParaView Developers Subject: Re: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style on OsX by default Assuming fusion is on the right side, I also like that better. What is important is that the fonts aren?t decreasing in size. Ditto the icons. We are just tightening up empty space. My $0.02 Alan From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Andy Bauer Sent: Thursday, July 27, 2017 7:45 AM To: Ayachit, Utkarsh (External Contacts) > Cc: ParaView Developers > Subject: [EXTERNAL] Re: [Paraview-developers] Using "fusion" style on OsX by default I like the Fusion style a bit better. I think it would be a good idea to get input from somebody with poor vision. On Thu, Jul 27, 2017 at 8:47 AM, Utkarsh Ayachit > wrote: Folks, I wanted to see what people thought about using the "fusion" style (same in Linux) on OsX instead of the current OsX style used by Qt. Attached are screenshots compare the two styles on a Mac. As you can see, "fusion" is more compact with more well aligned widgets. The Properties panel on both has been resized horizontally so that it is as minimum size possible before a horizontal scrollbar shows up. Note how wide it has to be with macOS style as against Fusion. Utkarsh _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Jul 27 13:42:32 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 27 Jul 2017 13:42:32 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style on OsX by default In-Reply-To: References: <646e80ed857c451094b71ad39e6554de@ES01AMSNLNT.srn.sandia.gov> Message-ID: Cool. Let's sleep on it for a day or two and if no new objections surface, we can choose to make the change. We can of course have an option to change it back in Settings too, but feel it might be an overkill since who'd actually change it. On Thu, Jul 27, 2017 at 1:14 PM, Moreland, Kenneth wrote: > I agree that I like the fusion style better for the same reason as Alan. In > fact, I remember complaining several years ago about how much space was > introduced into the GUI during some library update or another. > > > > My only reservation is that the tighter style might be more off-putting to > new users (exaggerates the airplane-cockpit syndrome). However, the current > GUI for the Windows executable looks just as tight, and that does not seem > to be an issue. (According to download counts, windows users outnumber Mac > and Linux by a large margin.) > > > > -Ken > > > > From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] > On Behalf Of Scott, W Alan > Sent: Thursday, July 27, 2017 11:06 AM > To: Bauer, Andy (External Contacts) ; Ayachit, > Utkarsh (External Contacts) > Cc: ParaView Developers > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style on > OsX by default > > > > Assuming fusion is on the right side, I also like that better. What is > important is that the fonts aren?t decreasing in size. Ditto the icons. We > are just tightening up empty space. > > > > My $0.02 > > > > Alan > > > > From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] > On Behalf Of Andy Bauer > Sent: Thursday, July 27, 2017 7:45 AM > To: Ayachit, Utkarsh (External Contacts) > Cc: ParaView Developers > Subject: [EXTERNAL] Re: [Paraview-developers] Using "fusion" style on OsX by > default > > > > I like the Fusion style a bit better. I think it would be a good idea to get > input from somebody with poor vision. > > > > On Thu, Jul 27, 2017 at 8:47 AM, Utkarsh Ayachit > wrote: > > Folks, > > > > I wanted to see what people thought about using the "fusion" style (same in > Linux) on OsX instead of the current OsX style used by Qt. Attached are > screenshots compare the two styles on a Mac. > > > > As you can see, "fusion" is more compact with more well aligned widgets. The > Properties panel on both has been resized horizontally so that it is as > minimum size possible before a horizontal scrollbar shows up. Note how wide > it has to be with macOS style as against Fusion. > > > > Utkarsh > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > From andy.bauer at kitware.com Thu Jul 27 13:44:34 2017 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 27 Jul 2017 13:44:34 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style on OsX by default In-Reply-To: References: <646e80ed857c451094b71ad39e6554de@ES01AMSNLNT.srn.sandia.gov> Message-ID: Yeah, I don't think we need another option for changing this. On Thu, Jul 27, 2017 at 1:42 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > Cool. Let's sleep on it for a day or two and if no new objections > surface, we can choose to make the change. We can of course have an > option to change it back in Settings too, but feel it might be an > overkill since who'd actually change it. > > > > On Thu, Jul 27, 2017 at 1:14 PM, Moreland, Kenneth > wrote: > > I agree that I like the fusion style better for the same reason as Alan. > In > > fact, I remember complaining several years ago about how much space was > > introduced into the GUI during some library update or another. > > > > > > > > My only reservation is that the tighter style might be more off-putting > to > > new users (exaggerates the airplane-cockpit syndrome). However, the > current > > GUI for the Windows executable looks just as tight, and that does not > seem > > to be an issue. (According to download counts, windows users outnumber > Mac > > and Linux by a large margin.) > > > > > > > > -Ken > > > > > > > > From: Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] > > On Behalf Of Scott, W Alan > > Sent: Thursday, July 27, 2017 11:06 AM > > To: Bauer, Andy (External Contacts) ; Ayachit, > > Utkarsh (External Contacts) > > Cc: ParaView Developers > > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style on > > OsX by default > > > > > > > > Assuming fusion is on the right side, I also like that better. What is > > important is that the fonts aren?t decreasing in size. Ditto the > icons. We > > are just tightening up empty space. > > > > > > > > My $0.02 > > > > > > > > Alan > > > > > > > > From: Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] > > On Behalf Of Andy Bauer > > Sent: Thursday, July 27, 2017 7:45 AM > > To: Ayachit, Utkarsh (External Contacts) > > Cc: ParaView Developers > > Subject: [EXTERNAL] Re: [Paraview-developers] Using "fusion" style on > OsX by > > default > > > > > > > > I like the Fusion style a bit better. I think it would be a good idea to > get > > input from somebody with poor vision. > > > > > > > > On Thu, Jul 27, 2017 at 8:47 AM, Utkarsh Ayachit > > wrote: > > > > Folks, > > > > > > > > I wanted to see what people thought about using the "fusion" style (same > in > > Linux) on OsX instead of the current OsX style used by Qt. Attached are > > screenshots compare the two styles on a Mac. > > > > > > > > As you can see, "fusion" is more compact with more well aligned widgets. > The > > Properties panel on both has been resized horizontally so that it is as > > minimum size possible before a horizontal scrollbar shows up. Note how > wide > > it has to be with macOS style as against Fusion. > > > > > > > > Utkarsh > > > > > > > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aron.helser at kitware.com Thu Jul 27 14:12:18 2017 From: aron.helser at kitware.com (Aron Helser) Date: Thu, 27 Jul 2017 14:12:18 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style on OsX by default In-Reply-To: References: <646e80ed857c451094b71ad39e6554de@ES01AMSNLNT.srn.sandia.gov> Message-ID: I'd like to bring up that this change is going against current design trends - i.e. towards 'flat' designs, with cleaner, less cluttered UI elements. It's why things take up more space. Utkarsh, I'd encourage you to run those screenshots by our website designer, and see what reaction you get. What I see - switching to the older buttons with drop shadows that mimic a 'physical' button makes the UI look it's age. That being said, as a engineer I really don't mind what it looks like as long as I can get it to do what I want, so I can see why you are interested in the change. Regards, Aron On Thu, Jul 27, 2017 at 1:44 PM, Andy Bauer wrote: > Yeah, I don't think we need another option for changing this. > > On Thu, Jul 27, 2017 at 1:42 PM, Utkarsh Ayachit < > utkarsh.ayachit at kitware.com> wrote: > >> Cool. Let's sleep on it for a day or two and if no new objections >> surface, we can choose to make the change. We can of course have an >> option to change it back in Settings too, but feel it might be an >> overkill since who'd actually change it. >> >> >> >> On Thu, Jul 27, 2017 at 1:14 PM, Moreland, Kenneth >> wrote: >> > I agree that I like the fusion style better for the same reason as >> Alan. In >> > fact, I remember complaining several years ago about how much space was >> > introduced into the GUI during some library update or another. >> > >> > >> > >> > My only reservation is that the tighter style might be more off-putting >> to >> > new users (exaggerates the airplane-cockpit syndrome). However, the >> current >> > GUI for the Windows executable looks just as tight, and that does not >> seem >> > to be an issue. (According to download counts, windows users outnumber >> Mac >> > and Linux by a large margin.) >> > >> > >> > >> > -Ken >> > >> > >> > >> > From: Paraview-developers [mailto:paraview-developers-bo >> unces at paraview.org] >> > On Behalf Of Scott, W Alan >> > Sent: Thursday, July 27, 2017 11:06 AM >> > To: Bauer, Andy (External Contacts) ; Ayachit, >> > Utkarsh (External Contacts) >> > Cc: ParaView Developers >> > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style >> on >> > OsX by default >> > >> > >> > >> > Assuming fusion is on the right side, I also like that better. What is >> > important is that the fonts aren?t decreasing in size. Ditto the >> icons. We >> > are just tightening up empty space. >> > >> > >> > >> > My $0.02 >> > >> > >> > >> > Alan >> > >> > >> > >> > From: Paraview-developers [mailto:paraview-developers-bo >> unces at paraview.org] >> > On Behalf Of Andy Bauer >> > Sent: Thursday, July 27, 2017 7:45 AM >> > To: Ayachit, Utkarsh (External Contacts) >> > Cc: ParaView Developers >> > Subject: [EXTERNAL] Re: [Paraview-developers] Using "fusion" style on >> OsX by >> > default >> > >> > >> > >> > I like the Fusion style a bit better. I think it would be a good idea >> to get >> > input from somebody with poor vision. >> > >> > >> > >> > On Thu, Jul 27, 2017 at 8:47 AM, Utkarsh Ayachit >> > wrote: >> > >> > Folks, >> > >> > >> > >> > I wanted to see what people thought about using the "fusion" style >> (same in >> > Linux) on OsX instead of the current OsX style used by Qt. Attached are >> > screenshots compare the two styles on a Mac. >> > >> > >> > >> > As you can see, "fusion" is more compact with more well aligned >> widgets. The >> > Properties panel on both has been resized horizontally so that it is as >> > minimum size possible before a horizontal scrollbar shows up. Note how >> wide >> > it has to be with macOS style as against Fusion. >> > >> > >> > >> > Utkarsh >> > >> > >> > >> > >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Search the list archives at: >> > http://markmail.org/search/?q=Paraview-developers >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> > >> > >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Jul 27 14:39:48 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 27 Jul 2017 14:39:48 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style on OsX by default In-Reply-To: References: <646e80ed857c451094b71ad39e6554de@ES01AMSNLNT.srn.sandia.gov> Message-ID: With regards to layout and spacing, that could be tightened up in the current style with Mac-specific margins in the proxy property widget, no? With regards to the overall aesthetic, it looks like I am in the minority, but I don't like the Fusion style on Mac. I love it on Linux, but not on a Mac. There was a time in the past when Apple strived to have a uniform look and feel across applications, and while that hasn't been the case even for Apple applications for quite a few years, I still like the idea. The Mac style in Qt has never been a perfect match for native macOS applications, but it is a reasonable facsimile in a lot of ways. Switching to Fusion completely abandons attempts to fit in with other macOS applications. So partly for nostalgia reasons, partly for a bias for consistency in the (Mac) universe, and partly for wanting to avoid startling new users a bit less with a different style, I prefer the current style. I think we should consult with the ParaView users mailing list to get more user feedback, not just developer feedback. Thanks, Cory On Thu, Jul 27, 2017 at 2:12 PM, Aron Helser wrote: > I'd like to bring up that this change is going against current design trends > - i.e. towards 'flat' designs, with cleaner, less cluttered UI elements. > > It's why things take up more space. Utkarsh, I'd encourage you to run those > screenshots by our website designer, and see what reaction you get. > > What I see - switching to the older buttons with drop shadows that mimic a > 'physical' button makes the UI look it's age. > > That being said, as a engineer I really don't mind what it looks like as > long as I can get it to do what I want, so I can see why you are interested > in the change. > > Regards, > Aron > > On Thu, Jul 27, 2017 at 1:44 PM, Andy Bauer wrote: >> >> Yeah, I don't think we need another option for changing this. >> >> On Thu, Jul 27, 2017 at 1:42 PM, Utkarsh Ayachit >> wrote: >>> >>> Cool. Let's sleep on it for a day or two and if no new objections >>> surface, we can choose to make the change. We can of course have an >>> option to change it back in Settings too, but feel it might be an >>> overkill since who'd actually change it. >>> >>> >>> >>> On Thu, Jul 27, 2017 at 1:14 PM, Moreland, Kenneth >>> wrote: >>> > I agree that I like the fusion style better for the same reason as >>> > Alan. In >>> > fact, I remember complaining several years ago about how much space was >>> > introduced into the GUI during some library update or another. >>> > >>> > >>> > >>> > My only reservation is that the tighter style might be more off-putting >>> > to >>> > new users (exaggerates the airplane-cockpit syndrome). However, the >>> > current >>> > GUI for the Windows executable looks just as tight, and that does not >>> > seem >>> > to be an issue. (According to download counts, windows users outnumber >>> > Mac >>> > and Linux by a large margin.) >>> > >>> > >>> > >>> > -Ken >>> > >>> > >>> > >>> > From: Paraview-developers >>> > [mailto:paraview-developers-bounces at paraview.org] >>> > On Behalf Of Scott, W Alan >>> > Sent: Thursday, July 27, 2017 11:06 AM >>> > To: Bauer, Andy (External Contacts) ; Ayachit, >>> > Utkarsh (External Contacts) >>> > Cc: ParaView Developers >>> > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style >>> > on >>> > OsX by default >>> > >>> > >>> > >>> > Assuming fusion is on the right side, I also like that better. What is >>> > important is that the fonts aren?t decreasing in size. Ditto the >>> > icons. We >>> > are just tightening up empty space. >>> > >>> > >>> > >>> > My $0.02 >>> > >>> > >>> > >>> > Alan >>> > >>> > >>> > >>> > From: Paraview-developers >>> > [mailto:paraview-developers-bounces at paraview.org] >>> > On Behalf Of Andy Bauer >>> > Sent: Thursday, July 27, 2017 7:45 AM >>> > To: Ayachit, Utkarsh (External Contacts) >>> > Cc: ParaView Developers >>> > Subject: [EXTERNAL] Re: [Paraview-developers] Using "fusion" style on >>> > OsX by >>> > default >>> > >>> > >>> > >>> > I like the Fusion style a bit better. I think it would be a good idea >>> > to get >>> > input from somebody with poor vision. >>> > >>> > >>> > >>> > On Thu, Jul 27, 2017 at 8:47 AM, Utkarsh Ayachit >>> > wrote: >>> > >>> > Folks, >>> > >>> > >>> > >>> > I wanted to see what people thought about using the "fusion" style >>> > (same in >>> > Linux) on OsX instead of the current OsX style used by Qt. Attached are >>> > screenshots compare the two styles on a Mac. >>> > >>> > >>> > >>> > As you can see, "fusion" is more compact with more well aligned >>> > widgets. The >>> > Properties panel on both has been resized horizontally so that it is as >>> > minimum size possible before a horizontal scrollbar shows up. Note how >>> > wide >>> > it has to be with macOS style as against Fusion. >>> > >>> > >>> > >>> > Utkarsh >>> > >>> > >>> > >>> > >>> > >>> > >>> > _______________________________________________ >>> > Powered by www.kitware.com >>> > >>> > Visit other Kitware open-source projects at >>> > http://www.kitware.com/opensource/opensource.html >>> > >>> > Search the list archives at: >>> > http://markmail.org/search/?q=Paraview-developers >>> > >>> > Follow this link to subscribe/unsubscribe: >>> > http://public.kitware.com/mailman/listinfo/paraview-developers >>> > >>> > >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From marcus.hanwell at kitware.com Thu Jul 27 14:54:23 2017 From: marcus.hanwell at kitware.com (Marcus D. Hanwell) Date: Thu, 27 Jul 2017 14:54:23 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style on OsX by default In-Reply-To: References: <646e80ed857c451094b71ad39e6554de@ES01AMSNLNT.srn.sandia.gov> Message-ID: Not really a Mac person, but I prefer the Mac style and would tighten up the borders which Qt seemed to make overly large in Qt 5 (they were never as bad in 4). The buttons look dated to me, and I prefer the flatter style. The modern KDE plasma desktop on Linux has moved away from the Fusion type style too I think, and it isn't even what I am used to on Linux. On Thu, Jul 27, 2017 at 2:39 PM, Cory Quammen wrote: > With regards to layout and spacing, that could be tightened up in the > current style with Mac-specific margins in the proxy property widget, > no? > > With regards to the overall aesthetic, it looks like I am in the > minority, but I don't like the Fusion style on Mac. I love it on > Linux, but not on a Mac. > > There was a time in the past when Apple strived to have a uniform look > and feel across applications, and while that hasn't been the case even > for Apple applications for quite a few years, I still like the idea. > The Mac style in Qt has never been a perfect match for native macOS > applications, but it is a reasonable facsimile in a lot of ways. > Switching to Fusion completely abandons attempts to fit in with other > macOS applications. So partly for nostalgia reasons, partly for a bias > for consistency in the (Mac) universe, and partly for wanting to avoid > startling new users a bit less with a different style, I prefer the > current style. > > I think we should consult with the ParaView users mailing list to get > more user feedback, not just developer feedback. > > Thanks, > Cory > > > On Thu, Jul 27, 2017 at 2:12 PM, Aron Helser wrote: >> I'd like to bring up that this change is going against current design trends >> - i.e. towards 'flat' designs, with cleaner, less cluttered UI elements. >> >> It's why things take up more space. Utkarsh, I'd encourage you to run those >> screenshots by our website designer, and see what reaction you get. >> >> What I see - switching to the older buttons with drop shadows that mimic a >> 'physical' button makes the UI look it's age. >> >> That being said, as a engineer I really don't mind what it looks like as >> long as I can get it to do what I want, so I can see why you are interested >> in the change. >> >> Regards, >> Aron >> >> On Thu, Jul 27, 2017 at 1:44 PM, Andy Bauer wrote: >>> >>> Yeah, I don't think we need another option for changing this. >>> >>> On Thu, Jul 27, 2017 at 1:42 PM, Utkarsh Ayachit >>> wrote: >>>> >>>> Cool. Let's sleep on it for a day or two and if no new objections >>>> surface, we can choose to make the change. We can of course have an >>>> option to change it back in Settings too, but feel it might be an >>>> overkill since who'd actually change it. >>>> >>>> >>>> >>>> On Thu, Jul 27, 2017 at 1:14 PM, Moreland, Kenneth >>>> wrote: >>>> > I agree that I like the fusion style better for the same reason as >>>> > Alan. In >>>> > fact, I remember complaining several years ago about how much space was >>>> > introduced into the GUI during some library update or another. >>>> > >>>> > >>>> > >>>> > My only reservation is that the tighter style might be more off-putting >>>> > to >>>> > new users (exaggerates the airplane-cockpit syndrome). However, the >>>> > current >>>> > GUI for the Windows executable looks just as tight, and that does not >>>> > seem >>>> > to be an issue. (According to download counts, windows users outnumber >>>> > Mac >>>> > and Linux by a large margin.) >>>> > >>>> > >>>> > >>>> > -Ken >>>> > >>>> > >>>> > >>>> > From: Paraview-developers >>>> > [mailto:paraview-developers-bounces at paraview.org] >>>> > On Behalf Of Scott, W Alan >>>> > Sent: Thursday, July 27, 2017 11:06 AM >>>> > To: Bauer, Andy (External Contacts) ; Ayachit, >>>> > Utkarsh (External Contacts) >>>> > Cc: ParaView Developers >>>> > Subject: Re: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style >>>> > on >>>> > OsX by default >>>> > >>>> > >>>> > >>>> > Assuming fusion is on the right side, I also like that better. What is >>>> > important is that the fonts aren?t decreasing in size. Ditto the >>>> > icons. We >>>> > are just tightening up empty space. >>>> > >>>> > >>>> > >>>> > My $0.02 >>>> > >>>> > >>>> > >>>> > Alan >>>> > >>>> > >>>> > >>>> > From: Paraview-developers >>>> > [mailto:paraview-developers-bounces at paraview.org] >>>> > On Behalf Of Andy Bauer >>>> > Sent: Thursday, July 27, 2017 7:45 AM >>>> > To: Ayachit, Utkarsh (External Contacts) >>>> > Cc: ParaView Developers >>>> > Subject: [EXTERNAL] Re: [Paraview-developers] Using "fusion" style on >>>> > OsX by >>>> > default >>>> > >>>> > >>>> > >>>> > I like the Fusion style a bit better. I think it would be a good idea >>>> > to get >>>> > input from somebody with poor vision. >>>> > >>>> > >>>> > >>>> > On Thu, Jul 27, 2017 at 8:47 AM, Utkarsh Ayachit >>>> > wrote: >>>> > >>>> > Folks, >>>> > >>>> > >>>> > >>>> > I wanted to see what people thought about using the "fusion" style >>>> > (same in >>>> > Linux) on OsX instead of the current OsX style used by Qt. Attached are >>>> > screenshots compare the two styles on a Mac. >>>> > >>>> > >>>> > >>>> > As you can see, "fusion" is more compact with more well aligned >>>> > widgets. The >>>> > Properties panel on both has been resized horizontally so that it is as >>>> > minimum size possible before a horizontal scrollbar shows up. Note how >>>> > wide >>>> > it has to be with macOS style as against Fusion. >>>> > >>>> > >>>> > >>>> > Utkarsh >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > _______________________________________________ >>>> > Powered by www.kitware.com >>>> > >>>> > Visit other Kitware open-source projects at >>>> > http://www.kitware.com/opensource/opensource.html >>>> > >>>> > Search the list archives at: >>>> > http://markmail.org/search/?q=Paraview-developers >>>> > >>>> > Follow this link to subscribe/unsubscribe: >>>> > http://public.kitware.com/mailman/listinfo/paraview-developers >>>> > >>>> > >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview-developers >>> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers From utkarsh.ayachit at kitware.com Thu Jul 27 16:54:04 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 27 Jul 2017 16:54:04 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style on OsX by default In-Reply-To: References: <646e80ed857c451094b71ad39e6554de@ES01AMSNLNT.srn.sandia.gov> Message-ID: I think I am going to defer to people who use ParaView on Mac (looking at you, Cory :) ) to investigate ways of making the UI look cleaner. Some of my misgivings with Qt-macOS style are: 1. too much padding (look at the vertical gap here) [image: Inline image 1] v/s [image: Inline image 2] 2. misaligned buttons (just look at the padding around buttons like "X Normal, Camera Normal" [image: Inline image 3] v/s [image: Inline image 4] Maybe there are things we can do that are less dramatic than changing the default style to clean these up. > I think we should consult with the ParaView users mailing list to get > more user feedback, not just developer feedback. I think we should not do this too soon. It's the whole bike-shed thing -- everyone will have an opinion on this; we need to make sure we don't open a can of worms that we cannot close :). Utkarsh -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 22369 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 9554 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 9210 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 12633 bytes Desc: not available URL: From sumeet.kumar507 at gmail.com Fri Jul 28 19:33:17 2017 From: sumeet.kumar507 at gmail.com (sumeet kumar) Date: Fri, 28 Jul 2017 16:33:17 -0700 Subject: [Paraview-developers] Error While loading file using pvserver in parallel Message-ID: Hello all, I have reader plugin which works great for sequential visualization. But, whenever I try to run parallel visualization using pvserver by running ( mpirun -np 4 pvserver), after a successful connection, I get an abrupt error while loading my output file. The error is /home/sumeet/Softwares/RealESSI_ROOT/RealESSI_Utilities/SRC/paraview/VTK/ThirdParty/hdf5/vtkhdf5/src/H5I.c:1111: vtk__H5I_get_type: Assertion `ret_value >= H5I_BADID && ret_value < H5I_next_type' failed. For sequential/remote visualization using pvserver by running (pvserver) (1 process) always works fine. Also, at times I get the same error while sequential visualization as well. But, this is very rare. I tried to search this error on internet but with no success. If anybody has any hint/idea to possible problem I would really appreciate that. Thanks Sumeet -- Sumeet Kumar Sinha Graduate Student Phone: (+1) <%28%2B91%29%209910516219>5306018271 Website : http://www.sumeetksinha.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Sat Jul 29 14:16:34 2017 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Sat, 29 Jul 2017 23:46:34 +0530 Subject: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style on OsX by default In-Reply-To: References: <646e80ed857c451094b71ad39e6554de@ES01AMSNLNT.srn.sandia.gov> Message-ID: My few cents (replied inlined) On Fri, Jul 28, 2017 at 2:24 AM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > I think I am going to defer to people who use ParaView on Mac (looking at > you, Cory :) ) to investigate ways of making the UI look cleaner. Some of > my misgivings with Qt-macOS style are: > > 1. too much padding (look at the vertical gap here) > > [image: Inline image 1] v/s [image: Inline image 2] > > The "lesser" vertical padding is welcome from a user's perspective if they belong to the same group of data. In this example, the "search box" and the "Property panel" are not grouped together in any sense. In this case, "larger vertical padding" is more user friendly (and also as per the usability standards) > 2. misaligned buttons (just look at the padding around buttons like "X > Normal, Camera Normal" > > [image: Inline image 3] v/s [image: Inline image 4] > The vertical alignment of the texts and the buttons are not proper. The right hand side snapshot (Fusion type) is therefore aesthetically pleasing and follows the standard usability guideline. > > Maybe there are things we can do that are less dramatic than changing the > default style to clean these up. > > > I think we should consult with the ParaView users mailing list to get > > more user feedback, not just developer feedback. > > I think we should not do this too soon. It's the whole bike-shed thing -- > everyone will have an opinion on this; we need to make sure we don't open a > can of worms that we cannot close :). > > Utkarsh > > In general the icons used in PV are 3D type with shades. The buttons in fusion type also has the 3D effect. Therefore, in my opinion, they goes better with the icon styles. I vote for fusion type GUI for Mac. Thanks, Chiranjib > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 9210 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 9554 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 22369 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 12633 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Mon Jul 31 10:28:00 2017 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 31 Jul 2017 10:28:00 -0400 Subject: [Paraview-developers] [EXTERNAL] Re: Using "fusion" style on OsX by default In-Reply-To: References: <646e80ed857c451094b71ad39e6554de@ES01AMSNLNT.srn.sandia.gov> Message-ID: Thanks for your input, Chiranjib. I think the plan is to try to see if some of the alignment issues can be addressed in macOS style itself. ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Jul 31 10:51:17 2017 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 31 Jul 2017 10:51:17 -0400 Subject: [Paraview-developers] ParaView 5.4.1-RC2 available for download In-Reply-To: References: Message-ID: Hi folks, Signed Mac .dmg and .pkg installers for ParaView 5.4.1-RC2 are now available on the downloads page at www.paraview.org/download. Thanks, Cory On Thu, Jul 27, 2017 at 12:32 PM, Cory Quammen wrote: > On behalf of the ParaView development team, I am happy to announce > that ParaView 5.4.1-RC2 is available for download. Binaries and source > code are available from > > www.paraview.org/download > > Note that ParaView 5.4.1-RC1 had a critical bug that was identified > and resolved internally before binaries and source code were made > available for download, so we have skipped straight to RC2. > > The 5.4.1-RC2 bug fix release addresses a number of problems, including: > > * The black render window observed on some systems when FXAA was > enabled or an object's opacity was less than 1 has been fixed. > > * Field output for cells with non-straight edges has been corrected. > > * Derivatives for quadratic triangles are now computed correctly. > > * A bug that occurred when generating a Catalyst script with no images > output has been fixed. > > * A problem with writing animations as AVIs was fixed. > > * Logic in the CGNS reader was updated to correctly read all solution > nodes for each centering type when FlowSolutionPointers are missing. > > * Fixed crash in CGNS reader when moving forward in time. > > * Fixed problem with long-running animations not advancing past a > certain number of time steps. > > * Resolved issue where changing one file path in the state file loader > "Choose File Names" dialog also changed the file paths of other files > with the same type. > > * Addressed problem with enumerated property dependencies in ParaViewWeb. > > * Added ability to change the font size in the ParaView user interface. > > * Fixed BoxLib3D file reader. > > * State files now properly support files with relative paths. > > * Removed inappropriate scalar bar scaling when saving large screen shots. > > Please report any problems you find with this release candidate on the > mailing list or on the bug tracker at > https://gitlab.kitware.com/paraview/paraview/issues > > - Cory > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: