From michael.bowerman at gmail.com Fri Aug 15 10:26:14 2014 From: michael.bowerman at gmail.com (Michael Bowerman) Date: Fri, 15 Aug 2014 09:26:14 -0500 Subject: [Ves] kiwi build failure Message-ID: Sorry for the basic question, most of the build documentation available is before git revision d11b159563760944dc166d0435e4a7be9fc54eda (android kiwi: change build scripts to be more flexible), where the *.sh files were removed. When I try to build with CMake, I get lots of errors. First, if I try to do the build in the source tree, it gives me the an error about "in-source builds not supported" when I try to build from: Apps/Android/Kiwi Next, I tried to build from Apps/Android/build, but that gives me build errors when I make. First, with not being able to find jni.h. After I manually add the include to CMAKE_CXX_FLAGS to find java, I get another error with not being able to find android/log.h. I am most likely doing something wrong before that point. I should not need to manually add all of these includes, right? Thanks! $ sw_vers ProductName: Mac OS X ProductVersion: 10.9.4 BuildVersion: 13E28 CMakeCache.txt: # This is the CMakeCache file. # For build in directory: /Users/luser/VES/Apps/Android/build # It was generated by CMake: /opt/local/bin/cmake # You can edit this file to change values found and used by cmake. # If you do not want to change any of the values, simply exit the editor. # If you do want to change a value, simply edit, save, and exit the editor. # The syntax for the file is as follows: # KEY:TYPE=VALUE # KEY is the name of a variable in the cache. # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. # VALUE is the current value for the KEY. ######################## # EXTERNAL cache entries ######################## //The android command-line tool ANDROID_EXECUTABLE:FILEPATH=/Applications/Android Studio.app/sdk/tools/android //No help, variable specified on the command line. ANDROID_NATIVE_API_LEVEL:UNINITIALIZED=8 //The Android API to target ANDROID_TARGET:STRING=android-18 //The ant build tool ANT_EXECUTABLE:FILEPATH=/opt/local/bin/ant //Path to a program. CMAKE_AR:FILEPATH=/usr/bin/ar //No help, variable specified on the command line. CMAKE_BINARY_DIR:UNINITIALIZED=/Users/luser/VES/Apps/Android/Kiwi/CMakeBuild //Choose the type of build, options are: None(CMAKE_CXX_FLAGS or // CMAKE_C_FLAGS used) Debug Release RelWithDebInfo MinSizeRel. CMAKE_BUILD_TYPE:STRING= //Enable/Disable color output during build. CMAKE_COLOR_MAKEFILE:BOOL=ON //CXX compiler. CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ //Flags used by the compiler during all build types. CMAKE_CXX_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_CXX_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //C compiler. CMAKE_C_COMPILER:FILEPATH=/usr/bin/cc //Flags used by the compiler during all build types. CMAKE_C_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_C_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //Flags used by the linker. CMAKE_EXE_LINKER_FLAGS:STRING=' ' //Flags used by the linker during debug builds. CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Enable/Disable output of compile commands during generation. CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF //Path to a program. CMAKE_INSTALL_NAME_TOOL:FILEPATH=/usr/bin/install_name_tool //Install path prefix, prepended onto install directories. CMAKE_INSTALL_PREFIX:PATH=/usr/local //Path to a program. CMAKE_LINKER:FILEPATH=/usr/bin/ld //Path to a program. CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make //Flags used by the linker during the creation of modules. CMAKE_MODULE_LINKER_FLAGS:STRING=' ' //Flags used by the linker during debug builds. CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_NM:FILEPATH=/usr/bin/nm //Path to a program. CMAKE_OBJCOPY:FILEPATH=CMAKE_OBJCOPY-NOTFOUND //Path to a program. CMAKE_OBJDUMP:FILEPATH=CMAKE_OBJDUMP-NOTFOUND //Build architectures for OSX CMAKE_OSX_ARCHITECTURES:STRING= //Minimum OS X version to target for deployment (at runtime); newer // APIs weak linked. Set to empty string for default value. CMAKE_OSX_DEPLOYMENT_TARGET:STRING= //The product will be built against the headers and libraries located // inside the indicated SDK. CMAKE_OSX_SYSROOT:STRING= //Value Computed by CMake CMAKE_PROJECT_NAME:STATIC=KiwiViewer //Path to a program. CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib //Flags used by the linker during the creation of dll's. CMAKE_SHARED_LINKER_FLAGS:STRING=' ' //Flags used by the linker during debug builds. CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING= //If set, runtime paths are not added when installing shared libraries, // but are added when building. CMAKE_SKIP_INSTALL_RPATH:BOOL=NO //If set, runtime paths are not added when using shared libraries. CMAKE_SKIP_RPATH:BOOL=NO //Flags used by the linker during the creation of static libraries. CMAKE_STATIC_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_STRIP:FILEPATH=/usr/bin/strip //No help, variable specified on the command line. CMAKE_TOOLCHAIN_FILE:UNINITIALIZED=/Users/luser/VES/CMake/toolchains/android.toolchain.cmake //If true, cmake will use relative paths in makefiles and projects. CMAKE_USE_RELATIVE_PATHS:BOOL=OFF //If this value is on, makefiles will be generated without the // .SILENT directive, and all commands will be echoed to the console // during the make. This is useful for debugging only. With Visual // Studio IDE projects all commands are done without /nologo. CMAKE_VERBOSE_MAKEFILE:BOOL=FALSE //Dependencies for the target KiwiNative_LIB_DEPENDS:STATIC=general;GLESv2;general;ves;general;vesShaders;general;kiwi;general;/usr/lib/libz.dylib;general;log; //Value Computed by CMake KiwiViewer_BINARY_DIR:STATIC=/Users/luser/VES/Apps/Android/build //Value Computed by CMake KiwiViewer_SOURCE_DIR:STATIC=/Users/luser/VES/Apps/Android/Kiwi //Build KiwiViewer with PCL support USE_PCL:BOOL=OFF //The directory containing a CMake configuration file for VES. VES_DIR:PATH=/Users/luser/VES/Apps/Android/CMakeBuild/build/CMakeExternals/Install/ves-android/lib //The directory containing a CMake configuration file for VTK. VTK_DIR:PATH=/Users/luser/VES/Apps/Android/CMakeBuild/build/CMakeExternals/Install/vtk-android/lib/cmake/vtk-6.0 //Path to a file. ZLIB_INCLUDE_DIR:PATH=/usr/include //Path to a library. ZLIB_LIBRARY:FILEPATH=/usr/lib/libz.dylib ######################## # INTERNAL cache entries ######################## //MODIFIED property for variable: ANDROID_EXECUTABLE ANDROID_EXECUTABLE-MODIFIED:INTERNAL=ON //ADVANCED property for variable: CMAKE_AR CMAKE_AR-ADVANCED:INTERNAL=1 //This is the directory where this CMakeCache.txt was created CMAKE_CACHEFILE_DIR:INTERNAL=/Users/luser/VES/Apps/Android/build //Major version of cmake used to create the current loaded cache CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3 //Minor version of cmake used to create the current loaded cache CMAKE_CACHE_MINOR_VERSION:INTERNAL=0 //Patch version of cmake used to create the current loaded cache CMAKE_CACHE_PATCH_VERSION:INTERNAL=0 //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=/opt/local/bin/cmake //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/opt/local/bin/cpack //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/opt/local/bin/ctest //ADVANCED property for variable: CMAKE_CXX_COMPILER CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1 //MODIFIED property for variable: CMAKE_CXX_FLAGS CMAKE_CXX_FLAGS-MODIFIED:INTERNAL=ON //ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_COMPILER CMAKE_C_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS CMAKE_C_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //Path to cache edit program executable. CMAKE_EDIT_COMMAND:INTERNAL=/opt/local/bin/ccmake //Executable file format CMAKE_EXECUTABLE_FORMAT:INTERNAL=Unknown //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1 //Name of generator. CMAKE_GENERATOR:INTERNAL=Unix Makefiles //Name of generator toolset. CMAKE_GENERATOR_TOOLSET:INTERNAL= //Start directory with the top level CMakeLists.txt file for this // project CMAKE_HOME_DIRECTORY:INTERNAL=/Users/luser/VES/Apps/Android/Kiwi //ADVANCED property for variable: CMAKE_INSTALL_NAME_TOOL CMAKE_INSTALL_NAME_TOOL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_LINKER CMAKE_LINKER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MAKE_PROGRAM CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_NM CMAKE_NM-ADVANCED:INTERNAL=1 //number of local generators CMAKE_NUMBER_OF_LOCAL_GENERATORS:INTERNAL=2 //ADVANCED property for variable: CMAKE_OBJCOPY CMAKE_OBJCOPY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_OBJDUMP CMAKE_OBJDUMP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_RANLIB CMAKE_RANLIB-ADVANCED:INTERNAL=1 //Path to CMake installation. CMAKE_ROOT:INTERNAL=/opt/local/share/cmake-3.0 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_RPATH CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STRIP CMAKE_STRIP-ADVANCED:INTERNAL=1 //uname command CMAKE_UNAME:INTERNAL=/usr/bin/uname //ADVANCED property for variable: CMAKE_USE_RELATIVE_PATHS CMAKE_USE_RELATIVE_PATHS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1 //Details about finding ZLIB FIND_PACKAGE_MESSAGE_DETAILS_ZLIB:INTERNAL=[/usr/lib/libz.dylib][/usr/include][v1.2.5()] //ADVANCED property for variable: ZLIB_INCLUDE_DIR ZLIB_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ZLIB_LIBRARY ZLIB_LIBRARY-ADVANCED:INTERNAL=1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamie.wright at nhs.net Sat Aug 16 14:32:11 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Sat, 16 Aug 2014 19:32:11 +0100 Subject: [Ves] vesMapper ScalarVisibiltyOff()? In-Reply-To: <37570C539C687742B34305706109271F086A6222B2@NHS-PCLI-MBC036.AD1.NHS.NET> References: <37570C539C687742B34305706109271F086A6222B2@NHS-PCLI-MBC036.AD1.NHS.NET> Message-ID: <20140816183239.AF558448530@nhs-pd1e-esg109.ad1.nhs.net> Dear All, I am attempting to show a vtkPolyData surface in an app I have created. However whenever I load in and render a .vtp file the polydata surface is colored blue, and I cannot set the color using the vesKiwiPolyDataRepresentation::SetColor() method. When this occurs in standard VTK it is because the scalar visibilty is on and vtkMapper->ScalarVisibilityOff() solves the issue. There does not seem to be a similar flag in vesMapper though. Can anyone direct me to where I need to set/unset a flag. I notice that one of the included datasets with the Kiwiviewer app, the visible-woman-hand.vtp has a white (or no lookup table set) color, so do we have to include some metadata in the .vtp files? thanks, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** From jamie.wright at nhs.net Sun Aug 17 01:36:07 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Sun, 17 Aug 2014 06:36:07 +0100 Subject: [Ves] vesMapper ScalarVisibiltyOff()? In-Reply-To: <20140816184251.CFB30448FE4@nhs-pd1e-esg006.ad1.nhs.net> References: <37570C539C687742B34305706109271F086A6222B2@NHS-PCLI-MBC036.AD1.NHS.NET>, <20140816184251.CFB30448FE4@nhs-pd1e-esg006.ad1.nhs.net> Message-ID: <20140817053832.BB4F5448062@nhs-pd1e-esg106.ad1.nhs.net> To answer my own question in part. To remove the blue coloring it was a case of going into the pointdata of the polydata object and calling RemoveArray() on the scalar array. I am still unaware if there is a VES option to turn the scalar visibility off Jamie Wright | Clinical Scientist | Nuclear Medicine | NHSGGC (Southern General and Glasgow Royal Infirmary) jamie.wright at nhs.net ________________________________________ From: Ves [ves-bounces at public.kitware.com] On Behalf Of Wright James (NHS Greater Glasgow & Clyde) [jamie.wright at nhs.net] Sent: 16 August 2014 19:32 To: ves at public.kitware.com Subject: [Ves] vesMapper ScalarVisibiltyOff()? --- This message was sent from an email address external to NHSmail but gives the appearance of being from an NHSmail (@nhs.net) address. The recipient should verify the sender and content before acting upon information contained within. The identified sender is ves-bounces at public.kitware.com --- Dear All, I am attempting to show a vtkPolyData surface in an app I have created. However whenever I load in and render a .vtp file the polydata surface is colored blue, and I cannot set the color using the vesKiwiPolyDataRepresentation::SetColor() method. When this occurs in standard VTK it is because the scalar visibilty is on and vtkMapper->ScalarVisibilityOff() solves the issue. There does not seem to be a similar flag in vesMapper though. Can anyone direct me to where I need to set/unset a flag. I notice that one of the included datasets with the Kiwiviewer app, the visible-woman-hand.vtp has a white (or no lookup table set) color, so do we have to include some metadata in the .vtp files? thanks, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** _______________________________________________ Ves mailing list Ves at public.kitware.com http://public.kitware.com/mailman/listinfo/ves ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** From jamie.wright at nhs.net Tue Aug 19 16:06:05 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Tue, 19 Aug 2014 21:06:05 +0100 Subject: [Ves] two or more vesKiwiImageWidgetRepresentation objects Message-ID: <20140819200606.5361C448C11@nhs-pd1e-esg105.ad1.nhs.net> Dear VES experts, I have a project with multiple vesKiwiImageWidgetRepresentation objects rendered to the screen at once. Panning, rotation and scaling happens across the objects. However, when I scroll through the slices of one imagewidgetrep object I cannot get the slices in the other objects to also scroll. I have overridden vesKiwiWidgetInteractionDelegate::handleSingleTouchDown() so that if there is more than one kiwiImageWidgetRep object then after the first representation has moved, the subsequent representations take the touchWorldPosition vector and use this in a method I have called doSliceScroll() which takes as arguments touchWorldPosition, a vtkTypeId variable called cellId, and std::vector variable called cellIdToPlaneId (calculated from the second object). Basically this method performs the code inside handleSingleTouchDown() from the point where locator->IntersectWithLine() is called and found to be true. I thought that doing this would cause the slices in other imageWidgetRepresentation objects to scroll if the corresponding slice in the first representation scrolls. However this causes my app to crash Could anyone point me to where I am going wrong? Do I have to issue some kind of callback to the other representations if I want their slices to also scroll? thanks, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** From aashish.chaudhary at kitware.com Tue Aug 19 16:24:36 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Tue, 19 Aug 2014 16:24:36 -0400 Subject: [Ves] two or more vesKiwiImageWidgetRepresentation objects In-Reply-To: <20140819200606.5361C448C11@nhs-pd1e-esg105.ad1.nhs.net> References: <20140819200606.5361C448C11@nhs-pd1e-esg105.ad1.nhs.net> Message-ID: It should be doable. I will look into the code and will get back to you sometime later today. - Aashish On Tue, Aug 19, 2014 at 4:06 PM, Wright James (NHS Greater Glasgow & Clyde) wrote: > Dear VES experts, > > I have a project with multiple vesKiwiImageWidgetRepresentation objects > rendered to the screen at once. Panning, rotation and scaling happens > across the objects. However, when I scroll through the slices of one > imagewidgetrep object I cannot get the slices in the other objects to also > scroll. I have overridden > vesKiwiWidgetInteractionDelegate::handleSingleTouchDown() so that if there > is more than one kiwiImageWidgetRep object then after the first > representation has moved, the subsequent representations take the > touchWorldPosition vector and use this in a method I have called > doSliceScroll() which takes as arguments touchWorldPosition, a vtkTypeId > variable called cellId, and std::vector variable called > cellIdToPlaneId (calculated from the second object). Basically this method > performs the code inside handleSingleTouchDown() from the point where > locator->IntersectWithLine() is called and found to be true. I thought that > doing this would cause the slices in other imageWidgetReprese > ntation objects to scroll if the corresponding slice in the first > representation scrolls. However this causes my app to crash > > Could anyone point me to where I am going wrong? Do I have to issue some > kind of callback to the other representations if I want their slices to > also scroll? > > thanks, Jamie > > > ******************************************************************************************************************** > > This message may contain confidential information. If you are not the > intended recipient please inform the > sender that you have received the message in error before deleting it. > Please do not disclose, copy or distribute information in this e-mail or > take any action in reliance on its contents: > to do so is strictly prohibited and may be unlawful. > > Thank you for your co-operation. > > NHSmail is the secure email and directory service available for all NHS > staff in England and Scotland > NHSmail is approved for exchanging patient data and other sensitive > information with NHSmail and GSi recipients > NHSmail provides an email address for your career in the NHS and can be > accessed anywhere > > > ******************************************************************************************************************** > _______________________________________________ > Ves mailing list > Ves at public.kitware.com > http://public.kitware.com/mailman/listinfo/ves > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamie.wright at nhs.net Thu Aug 21 09:50:50 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Thu, 21 Aug 2014 14:50:50 +0100 Subject: [Ves] two or more vesKiwiImageWidgetRepresentation objects In-Reply-To: <20140819202438.F0B5347C330@nhs-pd1e-esg007.ad1.nhs.net> References: <20140819200606.5361C448C11@nhs-pd1e-esg105.ad1.nhs.net>, <20140819202438.F0B5347C330@nhs-pd1e-esg007.ad1.nhs.net> Message-ID: <20140821135228.3F4DD449264@nhs-pd1e-esg101.ad1.nhs.net> Hi Aashish, Could I ask if you have had time to look into the problem of scrolling through the slices of multiple vesKiwiImageWidgetRepresentation objects simultaneously? regards, Jamie ________________________________ From: Aashish Chaudhary [aashish.chaudhary at kitware.com] Sent: 19 August 2014 21:24 To: Wright James (NHS Greater Glasgow & Clyde) Cc: ves at public.kitware.com Subject: Re: [Ves] two or more vesKiwiImageWidgetRepresentation objects It should be doable. I will look into the code and will get back to you sometime later today. - Aashish On Tue, Aug 19, 2014 at 4:06 PM, Wright James (NHS Greater Glasgow & Clyde) > wrote: Dear VES experts, I have a project with multiple vesKiwiImageWidgetRepresentation objects rendered to the screen at once. Panning, rotation and scaling happens across the objects. However, when I scroll through the slices of one imagewidgetrep object I cannot get the slices in the other objects to also scroll. I have overridden vesKiwiWidgetInteractionDelegate::handleSingleTouchDown() so that if there is more than one kiwiImageWidgetRep object then after the first representation has moved, the subsequent representations take the touchWorldPosition vector and use this in a method I have called doSliceScroll() which takes as arguments touchWorldPosition, a vtkTypeId variable called cellId, and std::vector variable called cellIdToPlaneId (calculated from the second object). Basically this method performs the code inside handleSingleTouchDown() from the point where locator->IntersectWithLine() is called and found to be true. I thought that doing this would cause the slices in other imageWidgetReprese ntation objects to scroll if the corresponding slice in the first representation scrolls. However this causes my app to crash Could anyone point me to where I am going wrong? Do I have to issue some kind of callback to the other representations if I want their slices to also scroll? thanks, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** _______________________________________________ Ves mailing list Ves at public.kitware.com http://public.kitware.com/mailman/listinfo/ves -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamie.wright at nhs.net Wed Aug 27 09:52:44 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Wed, 27 Aug 2014 14:52:44 +0100 Subject: [Ves] VES-kiwi for Win8 Message-ID: <20140827135248.02687448493@nhs-pd1e-esg101.ad1.nhs.net> Dear developers, I would like to know if there are any plans to port the VES and kiwi libraries for use in developing Windows mobile applications. regards, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Wed Aug 27 11:27:30 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 27 Aug 2014 11:27:30 -0400 Subject: [Ves] VES-kiwi for Win8 In-Reply-To: <20140827135248.02687448493@nhs-pd1e-esg101.ad1.nhs.net> References: <20140827135248.02687448493@nhs-pd1e-esg101.ad1.nhs.net> Message-ID: Hi Jamie, In the future, we will be merging / replacing the VES code with VTK new rendering work (Geometry and Volume). Once that happens, you will be able to build the APP mostly in VTK. We may port Kiwi into VTK as well but that has not been finalized yet. Hope this helps. - Aashish On Wed, Aug 27, 2014 at 9:52 AM, Wright James (NHS Greater Glasgow & Clyde) wrote: > Dear developers, > > I would like to know if there are any plans to port the VES and kiwi > libraries for use in developing Windows mobile applications. > > regards, Jamie > > > ******************************************************************************************************************** > > This message may contain confidential information. If you are not the > intended recipient please inform the > sender that you have received the message in error before deleting it. > Please do not disclose, copy or distribute information in this e-mail or > take any action in reliance on its contents: > to do so is strictly prohibited and may be unlawful. > > Thank you for your co-operation. > > NHSmail is the secure email and directory service available for all NHS > staff in England and Scotland > NHSmail is approved for exchanging patient data and other sensitive > information with NHSmail and GSi recipients > NHSmail provides an email address for your career in the NHS and can be > accessed anywhere > > > ******************************************************************************************************************** > > _______________________________________________ > Ves mailing list > Ves at public.kitware.com > http://public.kitware.com/mailman/listinfo/ves > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamie.wright at nhs.net Wed Aug 27 13:29:45 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Wed, 27 Aug 2014 18:29:45 +0100 Subject: [Ves] VES-kiwi for Win8 In-Reply-To: <20140827152737.7970B448C56@nhs-pd1e-esg002.ad1.nhs.net> References: <20140827135248.02687448493@nhs-pd1e-esg101.ad1.nhs.net>, <20140827152737.7970B448C56@nhs-pd1e-esg002.ad1.nhs.net> Message-ID: <20140827173356.3405F448B48@nhs-pd1e-esg110.ad1.nhs.net> Hi Aashish, Aplogies for my ignorance but does this mean that the new VTK rendering code, which iirc targets open gl 2.1+, can be run on desktop or mobile applications? So open-gl2.1+ runs on fixed and mobile platforms and replaces opengl-es? Jamie Wright | Clinical Scientist | Nuclear Medicine | NHSGGC (Southern General and Glasgow Royal Infirmary) jamie.wright at nhs.net ________________________________ From: Aashish Chaudhary [aashish.chaudhary at kitware.com] Sent: 27 August 2014 16:27 To: Wright James (NHS Greater Glasgow & Clyde) Cc: ves at public.kitware.com Subject: Re: [Ves] VES-kiwi for Win8 Hi Jamie, In the future, we will be merging / replacing the VES code with VTK new rendering work (Geometry and Volume). Once that happens, you will be able to build the APP mostly in VTK. We may port Kiwi into VTK as well but that has not been finalized yet. Hope this helps. - Aashish On Wed, Aug 27, 2014 at 9:52 AM, Wright James (NHS Greater Glasgow & Clyde) > wrote: Dear developers, I would like to know if there are any plans to port the VES and kiwi libraries for use in developing Windows mobile applications. regards, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** _______________________________________________ Ves mailing list Ves at public.kitware.com http://public.kitware.com/mailman/listinfo/ves -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.bowerman at gmail.com Fri Aug 15 10:26:14 2014 From: michael.bowerman at gmail.com (Michael Bowerman) Date: Fri, 15 Aug 2014 09:26:14 -0500 Subject: [Ves] kiwi build failure Message-ID: Sorry for the basic question, most of the build documentation available is before git revision d11b159563760944dc166d0435e4a7be9fc54eda (android kiwi: change build scripts to be more flexible), where the *.sh files were removed. When I try to build with CMake, I get lots of errors. First, if I try to do the build in the source tree, it gives me the an error about "in-source builds not supported" when I try to build from: Apps/Android/Kiwi Next, I tried to build from Apps/Android/build, but that gives me build errors when I make. First, with not being able to find jni.h. After I manually add the include to CMAKE_CXX_FLAGS to find java, I get another error with not being able to find android/log.h. I am most likely doing something wrong before that point. I should not need to manually add all of these includes, right? Thanks! $ sw_vers ProductName: Mac OS X ProductVersion: 10.9.4 BuildVersion: 13E28 CMakeCache.txt: # This is the CMakeCache file. # For build in directory: /Users/luser/VES/Apps/Android/build # It was generated by CMake: /opt/local/bin/cmake # You can edit this file to change values found and used by cmake. # If you do not want to change any of the values, simply exit the editor. # If you do want to change a value, simply edit, save, and exit the editor. # The syntax for the file is as follows: # KEY:TYPE=VALUE # KEY is the name of a variable in the cache. # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. # VALUE is the current value for the KEY. ######################## # EXTERNAL cache entries ######################## //The android command-line tool ANDROID_EXECUTABLE:FILEPATH=/Applications/Android Studio.app/sdk/tools/android //No help, variable specified on the command line. ANDROID_NATIVE_API_LEVEL:UNINITIALIZED=8 //The Android API to target ANDROID_TARGET:STRING=android-18 //The ant build tool ANT_EXECUTABLE:FILEPATH=/opt/local/bin/ant //Path to a program. CMAKE_AR:FILEPATH=/usr/bin/ar //No help, variable specified on the command line. CMAKE_BINARY_DIR:UNINITIALIZED=/Users/luser/VES/Apps/Android/Kiwi/CMakeBuild //Choose the type of build, options are: None(CMAKE_CXX_FLAGS or // CMAKE_C_FLAGS used) Debug Release RelWithDebInfo MinSizeRel. CMAKE_BUILD_TYPE:STRING= //Enable/Disable color output during build. CMAKE_COLOR_MAKEFILE:BOOL=ON //CXX compiler. CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ //Flags used by the compiler during all build types. CMAKE_CXX_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_CXX_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //C compiler. CMAKE_C_COMPILER:FILEPATH=/usr/bin/cc //Flags used by the compiler during all build types. CMAKE_C_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_C_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //Flags used by the linker. CMAKE_EXE_LINKER_FLAGS:STRING=' ' //Flags used by the linker during debug builds. CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Enable/Disable output of compile commands during generation. CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF //Path to a program. CMAKE_INSTALL_NAME_TOOL:FILEPATH=/usr/bin/install_name_tool //Install path prefix, prepended onto install directories. CMAKE_INSTALL_PREFIX:PATH=/usr/local //Path to a program. CMAKE_LINKER:FILEPATH=/usr/bin/ld //Path to a program. CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make //Flags used by the linker during the creation of modules. CMAKE_MODULE_LINKER_FLAGS:STRING=' ' //Flags used by the linker during debug builds. CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_NM:FILEPATH=/usr/bin/nm //Path to a program. CMAKE_OBJCOPY:FILEPATH=CMAKE_OBJCOPY-NOTFOUND //Path to a program. CMAKE_OBJDUMP:FILEPATH=CMAKE_OBJDUMP-NOTFOUND //Build architectures for OSX CMAKE_OSX_ARCHITECTURES:STRING= //Minimum OS X version to target for deployment (at runtime); newer // APIs weak linked. Set to empty string for default value. CMAKE_OSX_DEPLOYMENT_TARGET:STRING= //The product will be built against the headers and libraries located // inside the indicated SDK. CMAKE_OSX_SYSROOT:STRING= //Value Computed by CMake CMAKE_PROJECT_NAME:STATIC=KiwiViewer //Path to a program. CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib //Flags used by the linker during the creation of dll's. CMAKE_SHARED_LINKER_FLAGS:STRING=' ' //Flags used by the linker during debug builds. CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING= //If set, runtime paths are not added when installing shared libraries, // but are added when building. CMAKE_SKIP_INSTALL_RPATH:BOOL=NO //If set, runtime paths are not added when using shared libraries. CMAKE_SKIP_RPATH:BOOL=NO //Flags used by the linker during the creation of static libraries. CMAKE_STATIC_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_STRIP:FILEPATH=/usr/bin/strip //No help, variable specified on the command line. CMAKE_TOOLCHAIN_FILE:UNINITIALIZED=/Users/luser/VES/CMake/toolchains/android.toolchain.cmake //If true, cmake will use relative paths in makefiles and projects. CMAKE_USE_RELATIVE_PATHS:BOOL=OFF //If this value is on, makefiles will be generated without the // .SILENT directive, and all commands will be echoed to the console // during the make. This is useful for debugging only. With Visual // Studio IDE projects all commands are done without /nologo. CMAKE_VERBOSE_MAKEFILE:BOOL=FALSE //Dependencies for the target KiwiNative_LIB_DEPENDS:STATIC=general;GLESv2;general;ves;general;vesShaders;general;kiwi;general;/usr/lib/libz.dylib;general;log; //Value Computed by CMake KiwiViewer_BINARY_DIR:STATIC=/Users/luser/VES/Apps/Android/build //Value Computed by CMake KiwiViewer_SOURCE_DIR:STATIC=/Users/luser/VES/Apps/Android/Kiwi //Build KiwiViewer with PCL support USE_PCL:BOOL=OFF //The directory containing a CMake configuration file for VES. VES_DIR:PATH=/Users/luser/VES/Apps/Android/CMakeBuild/build/CMakeExternals/Install/ves-android/lib //The directory containing a CMake configuration file for VTK. VTK_DIR:PATH=/Users/luser/VES/Apps/Android/CMakeBuild/build/CMakeExternals/Install/vtk-android/lib/cmake/vtk-6.0 //Path to a file. ZLIB_INCLUDE_DIR:PATH=/usr/include //Path to a library. ZLIB_LIBRARY:FILEPATH=/usr/lib/libz.dylib ######################## # INTERNAL cache entries ######################## //MODIFIED property for variable: ANDROID_EXECUTABLE ANDROID_EXECUTABLE-MODIFIED:INTERNAL=ON //ADVANCED property for variable: CMAKE_AR CMAKE_AR-ADVANCED:INTERNAL=1 //This is the directory where this CMakeCache.txt was created CMAKE_CACHEFILE_DIR:INTERNAL=/Users/luser/VES/Apps/Android/build //Major version of cmake used to create the current loaded cache CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3 //Minor version of cmake used to create the current loaded cache CMAKE_CACHE_MINOR_VERSION:INTERNAL=0 //Patch version of cmake used to create the current loaded cache CMAKE_CACHE_PATCH_VERSION:INTERNAL=0 //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=/opt/local/bin/cmake //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/opt/local/bin/cpack //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/opt/local/bin/ctest //ADVANCED property for variable: CMAKE_CXX_COMPILER CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1 //MODIFIED property for variable: CMAKE_CXX_FLAGS CMAKE_CXX_FLAGS-MODIFIED:INTERNAL=ON //ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_COMPILER CMAKE_C_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS CMAKE_C_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //Path to cache edit program executable. CMAKE_EDIT_COMMAND:INTERNAL=/opt/local/bin/ccmake //Executable file format CMAKE_EXECUTABLE_FORMAT:INTERNAL=Unknown //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1 //Name of generator. CMAKE_GENERATOR:INTERNAL=Unix Makefiles //Name of generator toolset. CMAKE_GENERATOR_TOOLSET:INTERNAL= //Start directory with the top level CMakeLists.txt file for this // project CMAKE_HOME_DIRECTORY:INTERNAL=/Users/luser/VES/Apps/Android/Kiwi //ADVANCED property for variable: CMAKE_INSTALL_NAME_TOOL CMAKE_INSTALL_NAME_TOOL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_LINKER CMAKE_LINKER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MAKE_PROGRAM CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_NM CMAKE_NM-ADVANCED:INTERNAL=1 //number of local generators CMAKE_NUMBER_OF_LOCAL_GENERATORS:INTERNAL=2 //ADVANCED property for variable: CMAKE_OBJCOPY CMAKE_OBJCOPY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_OBJDUMP CMAKE_OBJDUMP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_RANLIB CMAKE_RANLIB-ADVANCED:INTERNAL=1 //Path to CMake installation. CMAKE_ROOT:INTERNAL=/opt/local/share/cmake-3.0 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_RPATH CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STRIP CMAKE_STRIP-ADVANCED:INTERNAL=1 //uname command CMAKE_UNAME:INTERNAL=/usr/bin/uname //ADVANCED property for variable: CMAKE_USE_RELATIVE_PATHS CMAKE_USE_RELATIVE_PATHS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1 //Details about finding ZLIB FIND_PACKAGE_MESSAGE_DETAILS_ZLIB:INTERNAL=[/usr/lib/libz.dylib][/usr/include][v1.2.5()] //ADVANCED property for variable: ZLIB_INCLUDE_DIR ZLIB_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ZLIB_LIBRARY ZLIB_LIBRARY-ADVANCED:INTERNAL=1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamie.wright at nhs.net Sat Aug 16 14:32:11 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Sat, 16 Aug 2014 19:32:11 +0100 Subject: [Ves] vesMapper ScalarVisibiltyOff()? In-Reply-To: <37570C539C687742B34305706109271F086A6222B2@NHS-PCLI-MBC036.AD1.NHS.NET> References: <37570C539C687742B34305706109271F086A6222B2@NHS-PCLI-MBC036.AD1.NHS.NET> Message-ID: <20140816183239.AF558448530@nhs-pd1e-esg109.ad1.nhs.net> Dear All, I am attempting to show a vtkPolyData surface in an app I have created. However whenever I load in and render a .vtp file the polydata surface is colored blue, and I cannot set the color using the vesKiwiPolyDataRepresentation::SetColor() method. When this occurs in standard VTK it is because the scalar visibilty is on and vtkMapper->ScalarVisibilityOff() solves the issue. There does not seem to be a similar flag in vesMapper though. Can anyone direct me to where I need to set/unset a flag. I notice that one of the included datasets with the Kiwiviewer app, the visible-woman-hand.vtp has a white (or no lookup table set) color, so do we have to include some metadata in the .vtp files? thanks, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** From jamie.wright at nhs.net Sun Aug 17 01:36:07 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Sun, 17 Aug 2014 06:36:07 +0100 Subject: [Ves] vesMapper ScalarVisibiltyOff()? In-Reply-To: <20140816184251.CFB30448FE4@nhs-pd1e-esg006.ad1.nhs.net> References: <37570C539C687742B34305706109271F086A6222B2@NHS-PCLI-MBC036.AD1.NHS.NET>, <20140816184251.CFB30448FE4@nhs-pd1e-esg006.ad1.nhs.net> Message-ID: <20140817053832.BB4F5448062@nhs-pd1e-esg106.ad1.nhs.net> To answer my own question in part. To remove the blue coloring it was a case of going into the pointdata of the polydata object and calling RemoveArray() on the scalar array. I am still unaware if there is a VES option to turn the scalar visibility off Jamie Wright | Clinical Scientist | Nuclear Medicine | NHSGGC (Southern General and Glasgow Royal Infirmary) jamie.wright at nhs.net ________________________________________ From: Ves [ves-bounces at public.kitware.com] On Behalf Of Wright James (NHS Greater Glasgow & Clyde) [jamie.wright at nhs.net] Sent: 16 August 2014 19:32 To: ves at public.kitware.com Subject: [Ves] vesMapper ScalarVisibiltyOff()? --- This message was sent from an email address external to NHSmail but gives the appearance of being from an NHSmail (@nhs.net) address. The recipient should verify the sender and content before acting upon information contained within. The identified sender is ves-bounces at public.kitware.com --- Dear All, I am attempting to show a vtkPolyData surface in an app I have created. However whenever I load in and render a .vtp file the polydata surface is colored blue, and I cannot set the color using the vesKiwiPolyDataRepresentation::SetColor() method. When this occurs in standard VTK it is because the scalar visibilty is on and vtkMapper->ScalarVisibilityOff() solves the issue. There does not seem to be a similar flag in vesMapper though. Can anyone direct me to where I need to set/unset a flag. I notice that one of the included datasets with the Kiwiviewer app, the visible-woman-hand.vtp has a white (or no lookup table set) color, so do we have to include some metadata in the .vtp files? thanks, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** _______________________________________________ Ves mailing list Ves at public.kitware.com http://public.kitware.com/mailman/listinfo/ves ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** From jamie.wright at nhs.net Tue Aug 19 16:06:05 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Tue, 19 Aug 2014 21:06:05 +0100 Subject: [Ves] two or more vesKiwiImageWidgetRepresentation objects Message-ID: <20140819200606.5361C448C11@nhs-pd1e-esg105.ad1.nhs.net> Dear VES experts, I have a project with multiple vesKiwiImageWidgetRepresentation objects rendered to the screen at once. Panning, rotation and scaling happens across the objects. However, when I scroll through the slices of one imagewidgetrep object I cannot get the slices in the other objects to also scroll. I have overridden vesKiwiWidgetInteractionDelegate::handleSingleTouchDown() so that if there is more than one kiwiImageWidgetRep object then after the first representation has moved, the subsequent representations take the touchWorldPosition vector and use this in a method I have called doSliceScroll() which takes as arguments touchWorldPosition, a vtkTypeId variable called cellId, and std::vector variable called cellIdToPlaneId (calculated from the second object). Basically this method performs the code inside handleSingleTouchDown() from the point where locator->IntersectWithLine() is called and found to be true. I thought that doing this would cause the slices in other imageWidgetRepresentation objects to scroll if the corresponding slice in the first representation scrolls. However this causes my app to crash Could anyone point me to where I am going wrong? Do I have to issue some kind of callback to the other representations if I want their slices to also scroll? thanks, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** From aashish.chaudhary at kitware.com Tue Aug 19 16:24:36 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Tue, 19 Aug 2014 16:24:36 -0400 Subject: [Ves] two or more vesKiwiImageWidgetRepresentation objects In-Reply-To: <20140819200606.5361C448C11@nhs-pd1e-esg105.ad1.nhs.net> References: <20140819200606.5361C448C11@nhs-pd1e-esg105.ad1.nhs.net> Message-ID: It should be doable. I will look into the code and will get back to you sometime later today. - Aashish On Tue, Aug 19, 2014 at 4:06 PM, Wright James (NHS Greater Glasgow & Clyde) wrote: > Dear VES experts, > > I have a project with multiple vesKiwiImageWidgetRepresentation objects > rendered to the screen at once. Panning, rotation and scaling happens > across the objects. However, when I scroll through the slices of one > imagewidgetrep object I cannot get the slices in the other objects to also > scroll. I have overridden > vesKiwiWidgetInteractionDelegate::handleSingleTouchDown() so that if there > is more than one kiwiImageWidgetRep object then after the first > representation has moved, the subsequent representations take the > touchWorldPosition vector and use this in a method I have called > doSliceScroll() which takes as arguments touchWorldPosition, a vtkTypeId > variable called cellId, and std::vector variable called > cellIdToPlaneId (calculated from the second object). Basically this method > performs the code inside handleSingleTouchDown() from the point where > locator->IntersectWithLine() is called and found to be true. I thought that > doing this would cause the slices in other imageWidgetReprese > ntation objects to scroll if the corresponding slice in the first > representation scrolls. However this causes my app to crash > > Could anyone point me to where I am going wrong? Do I have to issue some > kind of callback to the other representations if I want their slices to > also scroll? > > thanks, Jamie > > > ******************************************************************************************************************** > > This message may contain confidential information. If you are not the > intended recipient please inform the > sender that you have received the message in error before deleting it. > Please do not disclose, copy or distribute information in this e-mail or > take any action in reliance on its contents: > to do so is strictly prohibited and may be unlawful. > > Thank you for your co-operation. > > NHSmail is the secure email and directory service available for all NHS > staff in England and Scotland > NHSmail is approved for exchanging patient data and other sensitive > information with NHSmail and GSi recipients > NHSmail provides an email address for your career in the NHS and can be > accessed anywhere > > > ******************************************************************************************************************** > _______________________________________________ > Ves mailing list > Ves at public.kitware.com > http://public.kitware.com/mailman/listinfo/ves > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamie.wright at nhs.net Thu Aug 21 09:50:50 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Thu, 21 Aug 2014 14:50:50 +0100 Subject: [Ves] two or more vesKiwiImageWidgetRepresentation objects In-Reply-To: <20140819202438.F0B5347C330@nhs-pd1e-esg007.ad1.nhs.net> References: <20140819200606.5361C448C11@nhs-pd1e-esg105.ad1.nhs.net>, <20140819202438.F0B5347C330@nhs-pd1e-esg007.ad1.nhs.net> Message-ID: <20140821135228.3F4DD449264@nhs-pd1e-esg101.ad1.nhs.net> Hi Aashish, Could I ask if you have had time to look into the problem of scrolling through the slices of multiple vesKiwiImageWidgetRepresentation objects simultaneously? regards, Jamie ________________________________ From: Aashish Chaudhary [aashish.chaudhary at kitware.com] Sent: 19 August 2014 21:24 To: Wright James (NHS Greater Glasgow & Clyde) Cc: ves at public.kitware.com Subject: Re: [Ves] two or more vesKiwiImageWidgetRepresentation objects It should be doable. I will look into the code and will get back to you sometime later today. - Aashish On Tue, Aug 19, 2014 at 4:06 PM, Wright James (NHS Greater Glasgow & Clyde) > wrote: Dear VES experts, I have a project with multiple vesKiwiImageWidgetRepresentation objects rendered to the screen at once. Panning, rotation and scaling happens across the objects. However, when I scroll through the slices of one imagewidgetrep object I cannot get the slices in the other objects to also scroll. I have overridden vesKiwiWidgetInteractionDelegate::handleSingleTouchDown() so that if there is more than one kiwiImageWidgetRep object then after the first representation has moved, the subsequent representations take the touchWorldPosition vector and use this in a method I have called doSliceScroll() which takes as arguments touchWorldPosition, a vtkTypeId variable called cellId, and std::vector variable called cellIdToPlaneId (calculated from the second object). Basically this method performs the code inside handleSingleTouchDown() from the point where locator->IntersectWithLine() is called and found to be true. I thought that doing this would cause the slices in other imageWidgetReprese ntation objects to scroll if the corresponding slice in the first representation scrolls. However this causes my app to crash Could anyone point me to where I am going wrong? Do I have to issue some kind of callback to the other representations if I want their slices to also scroll? thanks, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** _______________________________________________ Ves mailing list Ves at public.kitware.com http://public.kitware.com/mailman/listinfo/ves -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamie.wright at nhs.net Wed Aug 27 09:52:44 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Wed, 27 Aug 2014 14:52:44 +0100 Subject: [Ves] VES-kiwi for Win8 Message-ID: <20140827135248.02687448493@nhs-pd1e-esg101.ad1.nhs.net> Dear developers, I would like to know if there are any plans to port the VES and kiwi libraries for use in developing Windows mobile applications. regards, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Wed Aug 27 11:27:30 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 27 Aug 2014 11:27:30 -0400 Subject: [Ves] VES-kiwi for Win8 In-Reply-To: <20140827135248.02687448493@nhs-pd1e-esg101.ad1.nhs.net> References: <20140827135248.02687448493@nhs-pd1e-esg101.ad1.nhs.net> Message-ID: Hi Jamie, In the future, we will be merging / replacing the VES code with VTK new rendering work (Geometry and Volume). Once that happens, you will be able to build the APP mostly in VTK. We may port Kiwi into VTK as well but that has not been finalized yet. Hope this helps. - Aashish On Wed, Aug 27, 2014 at 9:52 AM, Wright James (NHS Greater Glasgow & Clyde) wrote: > Dear developers, > > I would like to know if there are any plans to port the VES and kiwi > libraries for use in developing Windows mobile applications. > > regards, Jamie > > > ******************************************************************************************************************** > > This message may contain confidential information. If you are not the > intended recipient please inform the > sender that you have received the message in error before deleting it. > Please do not disclose, copy or distribute information in this e-mail or > take any action in reliance on its contents: > to do so is strictly prohibited and may be unlawful. > > Thank you for your co-operation. > > NHSmail is the secure email and directory service available for all NHS > staff in England and Scotland > NHSmail is approved for exchanging patient data and other sensitive > information with NHSmail and GSi recipients > NHSmail provides an email address for your career in the NHS and can be > accessed anywhere > > > ******************************************************************************************************************** > > _______________________________________________ > Ves mailing list > Ves at public.kitware.com > http://public.kitware.com/mailman/listinfo/ves > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamie.wright at nhs.net Wed Aug 27 13:29:45 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Wed, 27 Aug 2014 18:29:45 +0100 Subject: [Ves] VES-kiwi for Win8 In-Reply-To: <20140827152737.7970B448C56@nhs-pd1e-esg002.ad1.nhs.net> References: <20140827135248.02687448493@nhs-pd1e-esg101.ad1.nhs.net>, <20140827152737.7970B448C56@nhs-pd1e-esg002.ad1.nhs.net> Message-ID: <20140827173356.3405F448B48@nhs-pd1e-esg110.ad1.nhs.net> Hi Aashish, Aplogies for my ignorance but does this mean that the new VTK rendering code, which iirc targets open gl 2.1+, can be run on desktop or mobile applications? So open-gl2.1+ runs on fixed and mobile platforms and replaces opengl-es? Jamie Wright | Clinical Scientist | Nuclear Medicine | NHSGGC (Southern General and Glasgow Royal Infirmary) jamie.wright at nhs.net ________________________________ From: Aashish Chaudhary [aashish.chaudhary at kitware.com] Sent: 27 August 2014 16:27 To: Wright James (NHS Greater Glasgow & Clyde) Cc: ves at public.kitware.com Subject: Re: [Ves] VES-kiwi for Win8 Hi Jamie, In the future, we will be merging / replacing the VES code with VTK new rendering work (Geometry and Volume). Once that happens, you will be able to build the APP mostly in VTK. We may port Kiwi into VTK as well but that has not been finalized yet. Hope this helps. - Aashish On Wed, Aug 27, 2014 at 9:52 AM, Wright James (NHS Greater Glasgow & Clyde) > wrote: Dear developers, I would like to know if there are any plans to port the VES and kiwi libraries for use in developing Windows mobile applications. regards, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** _______________________________________________ Ves mailing list Ves at public.kitware.com http://public.kitware.com/mailman/listinfo/ves -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.bowerman at gmail.com Fri Aug 15 10:26:14 2014 From: michael.bowerman at gmail.com (Michael Bowerman) Date: Fri, 15 Aug 2014 09:26:14 -0500 Subject: [Ves] kiwi build failure Message-ID: Sorry for the basic question, most of the build documentation available is before git revision d11b159563760944dc166d0435e4a7be9fc54eda (android kiwi: change build scripts to be more flexible), where the *.sh files were removed. When I try to build with CMake, I get lots of errors. First, if I try to do the build in the source tree, it gives me the an error about "in-source builds not supported" when I try to build from: Apps/Android/Kiwi Next, I tried to build from Apps/Android/build, but that gives me build errors when I make. First, with not being able to find jni.h. After I manually add the include to CMAKE_CXX_FLAGS to find java, I get another error with not being able to find android/log.h. I am most likely doing something wrong before that point. I should not need to manually add all of these includes, right? Thanks! $ sw_vers ProductName: Mac OS X ProductVersion: 10.9.4 BuildVersion: 13E28 CMakeCache.txt: # This is the CMakeCache file. # For build in directory: /Users/luser/VES/Apps/Android/build # It was generated by CMake: /opt/local/bin/cmake # You can edit this file to change values found and used by cmake. # If you do not want to change any of the values, simply exit the editor. # If you do want to change a value, simply edit, save, and exit the editor. # The syntax for the file is as follows: # KEY:TYPE=VALUE # KEY is the name of a variable in the cache. # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. # VALUE is the current value for the KEY. ######################## # EXTERNAL cache entries ######################## //The android command-line tool ANDROID_EXECUTABLE:FILEPATH=/Applications/Android Studio.app/sdk/tools/android //No help, variable specified on the command line. ANDROID_NATIVE_API_LEVEL:UNINITIALIZED=8 //The Android API to target ANDROID_TARGET:STRING=android-18 //The ant build tool ANT_EXECUTABLE:FILEPATH=/opt/local/bin/ant //Path to a program. CMAKE_AR:FILEPATH=/usr/bin/ar //No help, variable specified on the command line. CMAKE_BINARY_DIR:UNINITIALIZED=/Users/luser/VES/Apps/Android/Kiwi/CMakeBuild //Choose the type of build, options are: None(CMAKE_CXX_FLAGS or // CMAKE_C_FLAGS used) Debug Release RelWithDebInfo MinSizeRel. CMAKE_BUILD_TYPE:STRING= //Enable/Disable color output during build. CMAKE_COLOR_MAKEFILE:BOOL=ON //CXX compiler. CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ //Flags used by the compiler during all build types. CMAKE_CXX_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_CXX_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //C compiler. CMAKE_C_COMPILER:FILEPATH=/usr/bin/cc //Flags used by the compiler during all build types. CMAKE_C_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_C_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //Flags used by the linker. CMAKE_EXE_LINKER_FLAGS:STRING=' ' //Flags used by the linker during debug builds. CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Enable/Disable output of compile commands during generation. CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF //Path to a program. CMAKE_INSTALL_NAME_TOOL:FILEPATH=/usr/bin/install_name_tool //Install path prefix, prepended onto install directories. CMAKE_INSTALL_PREFIX:PATH=/usr/local //Path to a program. CMAKE_LINKER:FILEPATH=/usr/bin/ld //Path to a program. CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make //Flags used by the linker during the creation of modules. CMAKE_MODULE_LINKER_FLAGS:STRING=' ' //Flags used by the linker during debug builds. CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_NM:FILEPATH=/usr/bin/nm //Path to a program. CMAKE_OBJCOPY:FILEPATH=CMAKE_OBJCOPY-NOTFOUND //Path to a program. CMAKE_OBJDUMP:FILEPATH=CMAKE_OBJDUMP-NOTFOUND //Build architectures for OSX CMAKE_OSX_ARCHITECTURES:STRING= //Minimum OS X version to target for deployment (at runtime); newer // APIs weak linked. Set to empty string for default value. CMAKE_OSX_DEPLOYMENT_TARGET:STRING= //The product will be built against the headers and libraries located // inside the indicated SDK. CMAKE_OSX_SYSROOT:STRING= //Value Computed by CMake CMAKE_PROJECT_NAME:STATIC=KiwiViewer //Path to a program. CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib //Flags used by the linker during the creation of dll's. CMAKE_SHARED_LINKER_FLAGS:STRING=' ' //Flags used by the linker during debug builds. CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING= //If set, runtime paths are not added when installing shared libraries, // but are added when building. CMAKE_SKIP_INSTALL_RPATH:BOOL=NO //If set, runtime paths are not added when using shared libraries. CMAKE_SKIP_RPATH:BOOL=NO //Flags used by the linker during the creation of static libraries. CMAKE_STATIC_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_STRIP:FILEPATH=/usr/bin/strip //No help, variable specified on the command line. CMAKE_TOOLCHAIN_FILE:UNINITIALIZED=/Users/luser/VES/CMake/toolchains/android.toolchain.cmake //If true, cmake will use relative paths in makefiles and projects. CMAKE_USE_RELATIVE_PATHS:BOOL=OFF //If this value is on, makefiles will be generated without the // .SILENT directive, and all commands will be echoed to the console // during the make. This is useful for debugging only. With Visual // Studio IDE projects all commands are done without /nologo. CMAKE_VERBOSE_MAKEFILE:BOOL=FALSE //Dependencies for the target KiwiNative_LIB_DEPENDS:STATIC=general;GLESv2;general;ves;general;vesShaders;general;kiwi;general;/usr/lib/libz.dylib;general;log; //Value Computed by CMake KiwiViewer_BINARY_DIR:STATIC=/Users/luser/VES/Apps/Android/build //Value Computed by CMake KiwiViewer_SOURCE_DIR:STATIC=/Users/luser/VES/Apps/Android/Kiwi //Build KiwiViewer with PCL support USE_PCL:BOOL=OFF //The directory containing a CMake configuration file for VES. VES_DIR:PATH=/Users/luser/VES/Apps/Android/CMakeBuild/build/CMakeExternals/Install/ves-android/lib //The directory containing a CMake configuration file for VTK. VTK_DIR:PATH=/Users/luser/VES/Apps/Android/CMakeBuild/build/CMakeExternals/Install/vtk-android/lib/cmake/vtk-6.0 //Path to a file. ZLIB_INCLUDE_DIR:PATH=/usr/include //Path to a library. ZLIB_LIBRARY:FILEPATH=/usr/lib/libz.dylib ######################## # INTERNAL cache entries ######################## //MODIFIED property for variable: ANDROID_EXECUTABLE ANDROID_EXECUTABLE-MODIFIED:INTERNAL=ON //ADVANCED property for variable: CMAKE_AR CMAKE_AR-ADVANCED:INTERNAL=1 //This is the directory where this CMakeCache.txt was created CMAKE_CACHEFILE_DIR:INTERNAL=/Users/luser/VES/Apps/Android/build //Major version of cmake used to create the current loaded cache CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3 //Minor version of cmake used to create the current loaded cache CMAKE_CACHE_MINOR_VERSION:INTERNAL=0 //Patch version of cmake used to create the current loaded cache CMAKE_CACHE_PATCH_VERSION:INTERNAL=0 //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=/opt/local/bin/cmake //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/opt/local/bin/cpack //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/opt/local/bin/ctest //ADVANCED property for variable: CMAKE_CXX_COMPILER CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1 //MODIFIED property for variable: CMAKE_CXX_FLAGS CMAKE_CXX_FLAGS-MODIFIED:INTERNAL=ON //ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_COMPILER CMAKE_C_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS CMAKE_C_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //Path to cache edit program executable. CMAKE_EDIT_COMMAND:INTERNAL=/opt/local/bin/ccmake //Executable file format CMAKE_EXECUTABLE_FORMAT:INTERNAL=Unknown //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1 //Name of generator. CMAKE_GENERATOR:INTERNAL=Unix Makefiles //Name of generator toolset. CMAKE_GENERATOR_TOOLSET:INTERNAL= //Start directory with the top level CMakeLists.txt file for this // project CMAKE_HOME_DIRECTORY:INTERNAL=/Users/luser/VES/Apps/Android/Kiwi //ADVANCED property for variable: CMAKE_INSTALL_NAME_TOOL CMAKE_INSTALL_NAME_TOOL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_LINKER CMAKE_LINKER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MAKE_PROGRAM CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_NM CMAKE_NM-ADVANCED:INTERNAL=1 //number of local generators CMAKE_NUMBER_OF_LOCAL_GENERATORS:INTERNAL=2 //ADVANCED property for variable: CMAKE_OBJCOPY CMAKE_OBJCOPY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_OBJDUMP CMAKE_OBJDUMP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_RANLIB CMAKE_RANLIB-ADVANCED:INTERNAL=1 //Path to CMake installation. CMAKE_ROOT:INTERNAL=/opt/local/share/cmake-3.0 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_RPATH CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STRIP CMAKE_STRIP-ADVANCED:INTERNAL=1 //uname command CMAKE_UNAME:INTERNAL=/usr/bin/uname //ADVANCED property for variable: CMAKE_USE_RELATIVE_PATHS CMAKE_USE_RELATIVE_PATHS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1 //Details about finding ZLIB FIND_PACKAGE_MESSAGE_DETAILS_ZLIB:INTERNAL=[/usr/lib/libz.dylib][/usr/include][v1.2.5()] //ADVANCED property for variable: ZLIB_INCLUDE_DIR ZLIB_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ZLIB_LIBRARY ZLIB_LIBRARY-ADVANCED:INTERNAL=1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamie.wright at nhs.net Sat Aug 16 14:32:11 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Sat, 16 Aug 2014 19:32:11 +0100 Subject: [Ves] vesMapper ScalarVisibiltyOff()? In-Reply-To: <37570C539C687742B34305706109271F086A6222B2@NHS-PCLI-MBC036.AD1.NHS.NET> References: <37570C539C687742B34305706109271F086A6222B2@NHS-PCLI-MBC036.AD1.NHS.NET> Message-ID: <20140816183239.AF558448530@nhs-pd1e-esg109.ad1.nhs.net> Dear All, I am attempting to show a vtkPolyData surface in an app I have created. However whenever I load in and render a .vtp file the polydata surface is colored blue, and I cannot set the color using the vesKiwiPolyDataRepresentation::SetColor() method. When this occurs in standard VTK it is because the scalar visibilty is on and vtkMapper->ScalarVisibilityOff() solves the issue. There does not seem to be a similar flag in vesMapper though. Can anyone direct me to where I need to set/unset a flag. I notice that one of the included datasets with the Kiwiviewer app, the visible-woman-hand.vtp has a white (or no lookup table set) color, so do we have to include some metadata in the .vtp files? thanks, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** From jamie.wright at nhs.net Sun Aug 17 01:36:07 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Sun, 17 Aug 2014 06:36:07 +0100 Subject: [Ves] vesMapper ScalarVisibiltyOff()? In-Reply-To: <20140816184251.CFB30448FE4@nhs-pd1e-esg006.ad1.nhs.net> References: <37570C539C687742B34305706109271F086A6222B2@NHS-PCLI-MBC036.AD1.NHS.NET>, <20140816184251.CFB30448FE4@nhs-pd1e-esg006.ad1.nhs.net> Message-ID: <20140817053832.BB4F5448062@nhs-pd1e-esg106.ad1.nhs.net> To answer my own question in part. To remove the blue coloring it was a case of going into the pointdata of the polydata object and calling RemoveArray() on the scalar array. I am still unaware if there is a VES option to turn the scalar visibility off Jamie Wright | Clinical Scientist | Nuclear Medicine | NHSGGC (Southern General and Glasgow Royal Infirmary) jamie.wright at nhs.net ________________________________________ From: Ves [ves-bounces at public.kitware.com] On Behalf Of Wright James (NHS Greater Glasgow & Clyde) [jamie.wright at nhs.net] Sent: 16 August 2014 19:32 To: ves at public.kitware.com Subject: [Ves] vesMapper ScalarVisibiltyOff()? --- This message was sent from an email address external to NHSmail but gives the appearance of being from an NHSmail (@nhs.net) address. The recipient should verify the sender and content before acting upon information contained within. The identified sender is ves-bounces at public.kitware.com --- Dear All, I am attempting to show a vtkPolyData surface in an app I have created. However whenever I load in and render a .vtp file the polydata surface is colored blue, and I cannot set the color using the vesKiwiPolyDataRepresentation::SetColor() method. When this occurs in standard VTK it is because the scalar visibilty is on and vtkMapper->ScalarVisibilityOff() solves the issue. There does not seem to be a similar flag in vesMapper though. Can anyone direct me to where I need to set/unset a flag. I notice that one of the included datasets with the Kiwiviewer app, the visible-woman-hand.vtp has a white (or no lookup table set) color, so do we have to include some metadata in the .vtp files? thanks, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** _______________________________________________ Ves mailing list Ves at public.kitware.com http://public.kitware.com/mailman/listinfo/ves ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** From jamie.wright at nhs.net Tue Aug 19 16:06:05 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Tue, 19 Aug 2014 21:06:05 +0100 Subject: [Ves] two or more vesKiwiImageWidgetRepresentation objects Message-ID: <20140819200606.5361C448C11@nhs-pd1e-esg105.ad1.nhs.net> Dear VES experts, I have a project with multiple vesKiwiImageWidgetRepresentation objects rendered to the screen at once. Panning, rotation and scaling happens across the objects. However, when I scroll through the slices of one imagewidgetrep object I cannot get the slices in the other objects to also scroll. I have overridden vesKiwiWidgetInteractionDelegate::handleSingleTouchDown() so that if there is more than one kiwiImageWidgetRep object then after the first representation has moved, the subsequent representations take the touchWorldPosition vector and use this in a method I have called doSliceScroll() which takes as arguments touchWorldPosition, a vtkTypeId variable called cellId, and std::vector variable called cellIdToPlaneId (calculated from the second object). Basically this method performs the code inside handleSingleTouchDown() from the point where locator->IntersectWithLine() is called and found to be true. I thought that doing this would cause the slices in other imageWidgetRepresentation objects to scroll if the corresponding slice in the first representation scrolls. However this causes my app to crash Could anyone point me to where I am going wrong? Do I have to issue some kind of callback to the other representations if I want their slices to also scroll? thanks, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** From aashish.chaudhary at kitware.com Tue Aug 19 16:24:36 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Tue, 19 Aug 2014 16:24:36 -0400 Subject: [Ves] two or more vesKiwiImageWidgetRepresentation objects In-Reply-To: <20140819200606.5361C448C11@nhs-pd1e-esg105.ad1.nhs.net> References: <20140819200606.5361C448C11@nhs-pd1e-esg105.ad1.nhs.net> Message-ID: It should be doable. I will look into the code and will get back to you sometime later today. - Aashish On Tue, Aug 19, 2014 at 4:06 PM, Wright James (NHS Greater Glasgow & Clyde) wrote: > Dear VES experts, > > I have a project with multiple vesKiwiImageWidgetRepresentation objects > rendered to the screen at once. Panning, rotation and scaling happens > across the objects. However, when I scroll through the slices of one > imagewidgetrep object I cannot get the slices in the other objects to also > scroll. I have overridden > vesKiwiWidgetInteractionDelegate::handleSingleTouchDown() so that if there > is more than one kiwiImageWidgetRep object then after the first > representation has moved, the subsequent representations take the > touchWorldPosition vector and use this in a method I have called > doSliceScroll() which takes as arguments touchWorldPosition, a vtkTypeId > variable called cellId, and std::vector variable called > cellIdToPlaneId (calculated from the second object). Basically this method > performs the code inside handleSingleTouchDown() from the point where > locator->IntersectWithLine() is called and found to be true. I thought that > doing this would cause the slices in other imageWidgetReprese > ntation objects to scroll if the corresponding slice in the first > representation scrolls. However this causes my app to crash > > Could anyone point me to where I am going wrong? Do I have to issue some > kind of callback to the other representations if I want their slices to > also scroll? > > thanks, Jamie > > > ******************************************************************************************************************** > > This message may contain confidential information. If you are not the > intended recipient please inform the > sender that you have received the message in error before deleting it. > Please do not disclose, copy or distribute information in this e-mail or > take any action in reliance on its contents: > to do so is strictly prohibited and may be unlawful. > > Thank you for your co-operation. > > NHSmail is the secure email and directory service available for all NHS > staff in England and Scotland > NHSmail is approved for exchanging patient data and other sensitive > information with NHSmail and GSi recipients > NHSmail provides an email address for your career in the NHS and can be > accessed anywhere > > > ******************************************************************************************************************** > _______________________________________________ > Ves mailing list > Ves at public.kitware.com > http://public.kitware.com/mailman/listinfo/ves > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamie.wright at nhs.net Thu Aug 21 09:50:50 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Thu, 21 Aug 2014 14:50:50 +0100 Subject: [Ves] two or more vesKiwiImageWidgetRepresentation objects In-Reply-To: <20140819202438.F0B5347C330@nhs-pd1e-esg007.ad1.nhs.net> References: <20140819200606.5361C448C11@nhs-pd1e-esg105.ad1.nhs.net>, <20140819202438.F0B5347C330@nhs-pd1e-esg007.ad1.nhs.net> Message-ID: <20140821135228.3F4DD449264@nhs-pd1e-esg101.ad1.nhs.net> Hi Aashish, Could I ask if you have had time to look into the problem of scrolling through the slices of multiple vesKiwiImageWidgetRepresentation objects simultaneously? regards, Jamie ________________________________ From: Aashish Chaudhary [aashish.chaudhary at kitware.com] Sent: 19 August 2014 21:24 To: Wright James (NHS Greater Glasgow & Clyde) Cc: ves at public.kitware.com Subject: Re: [Ves] two or more vesKiwiImageWidgetRepresentation objects It should be doable. I will look into the code and will get back to you sometime later today. - Aashish On Tue, Aug 19, 2014 at 4:06 PM, Wright James (NHS Greater Glasgow & Clyde) > wrote: Dear VES experts, I have a project with multiple vesKiwiImageWidgetRepresentation objects rendered to the screen at once. Panning, rotation and scaling happens across the objects. However, when I scroll through the slices of one imagewidgetrep object I cannot get the slices in the other objects to also scroll. I have overridden vesKiwiWidgetInteractionDelegate::handleSingleTouchDown() so that if there is more than one kiwiImageWidgetRep object then after the first representation has moved, the subsequent representations take the touchWorldPosition vector and use this in a method I have called doSliceScroll() which takes as arguments touchWorldPosition, a vtkTypeId variable called cellId, and std::vector variable called cellIdToPlaneId (calculated from the second object). Basically this method performs the code inside handleSingleTouchDown() from the point where locator->IntersectWithLine() is called and found to be true. I thought that doing this would cause the slices in other imageWidgetReprese ntation objects to scroll if the corresponding slice in the first representation scrolls. However this causes my app to crash Could anyone point me to where I am going wrong? Do I have to issue some kind of callback to the other representations if I want their slices to also scroll? thanks, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** _______________________________________________ Ves mailing list Ves at public.kitware.com http://public.kitware.com/mailman/listinfo/ves -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamie.wright at nhs.net Wed Aug 27 09:52:44 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Wed, 27 Aug 2014 14:52:44 +0100 Subject: [Ves] VES-kiwi for Win8 Message-ID: <20140827135248.02687448493@nhs-pd1e-esg101.ad1.nhs.net> Dear developers, I would like to know if there are any plans to port the VES and kiwi libraries for use in developing Windows mobile applications. regards, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Wed Aug 27 11:27:30 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Wed, 27 Aug 2014 11:27:30 -0400 Subject: [Ves] VES-kiwi for Win8 In-Reply-To: <20140827135248.02687448493@nhs-pd1e-esg101.ad1.nhs.net> References: <20140827135248.02687448493@nhs-pd1e-esg101.ad1.nhs.net> Message-ID: Hi Jamie, In the future, we will be merging / replacing the VES code with VTK new rendering work (Geometry and Volume). Once that happens, you will be able to build the APP mostly in VTK. We may port Kiwi into VTK as well but that has not been finalized yet. Hope this helps. - Aashish On Wed, Aug 27, 2014 at 9:52 AM, Wright James (NHS Greater Glasgow & Clyde) wrote: > Dear developers, > > I would like to know if there are any plans to port the VES and kiwi > libraries for use in developing Windows mobile applications. > > regards, Jamie > > > ******************************************************************************************************************** > > This message may contain confidential information. If you are not the > intended recipient please inform the > sender that you have received the message in error before deleting it. > Please do not disclose, copy or distribute information in this e-mail or > take any action in reliance on its contents: > to do so is strictly prohibited and may be unlawful. > > Thank you for your co-operation. > > NHSmail is the secure email and directory service available for all NHS > staff in England and Scotland > NHSmail is approved for exchanging patient data and other sensitive > information with NHSmail and GSi recipients > NHSmail provides an email address for your career in the NHS and can be > accessed anywhere > > > ******************************************************************************************************************** > > _______________________________________________ > Ves mailing list > Ves at public.kitware.com > http://public.kitware.com/mailman/listinfo/ves > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamie.wright at nhs.net Wed Aug 27 13:29:45 2014 From: jamie.wright at nhs.net (Wright James (NHS Greater Glasgow & Clyde)) Date: Wed, 27 Aug 2014 18:29:45 +0100 Subject: [Ves] VES-kiwi for Win8 In-Reply-To: <20140827152737.7970B448C56@nhs-pd1e-esg002.ad1.nhs.net> References: <20140827135248.02687448493@nhs-pd1e-esg101.ad1.nhs.net>, <20140827152737.7970B448C56@nhs-pd1e-esg002.ad1.nhs.net> Message-ID: <20140827173356.3405F448B48@nhs-pd1e-esg110.ad1.nhs.net> Hi Aashish, Aplogies for my ignorance but does this mean that the new VTK rendering code, which iirc targets open gl 2.1+, can be run on desktop or mobile applications? So open-gl2.1+ runs on fixed and mobile platforms and replaces opengl-es? Jamie Wright | Clinical Scientist | Nuclear Medicine | NHSGGC (Southern General and Glasgow Royal Infirmary) jamie.wright at nhs.net ________________________________ From: Aashish Chaudhary [aashish.chaudhary at kitware.com] Sent: 27 August 2014 16:27 To: Wright James (NHS Greater Glasgow & Clyde) Cc: ves at public.kitware.com Subject: Re: [Ves] VES-kiwi for Win8 Hi Jamie, In the future, we will be merging / replacing the VES code with VTK new rendering work (Geometry and Volume). Once that happens, you will be able to build the APP mostly in VTK. We may port Kiwi into VTK as well but that has not been finalized yet. Hope this helps. - Aashish On Wed, Aug 27, 2014 at 9:52 AM, Wright James (NHS Greater Glasgow & Clyde) > wrote: Dear developers, I would like to know if there are any plans to port the VES and kiwi libraries for use in developing Windows mobile applications. regards, Jamie ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** _______________________________________________ Ves mailing list Ves at public.kitware.com http://public.kitware.com/mailman/listinfo/ves -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ******************************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: