Close up of the controls since the screenies got resized:

A quick look shows that it works (Win 64). I see that you post the source code, so maybe I can compile it on Linux too.

(1) I don’t see a way to close the program. That is, there is no main menu bar. If it is there, it is positioned off-screen. I know how to exit the program using Windows platform, but most users won’t know how to do that.

(2) When idle, it uses about 40% CPU. Doesn’t seem to slowly increase, the way it would with memory leaks. However, I wonder if there are some memory leaks in the code that launches it.

I don’t have linux installed right now, but I do have the CMakeLists.txt that I used to compile it for linux in the past if you’re interested. It needs to be fixed it up a bit since I ported the project to Visual Studio.
I actually still have an older binary for linux, but I think I made some major calculation changes in the Kansei scale part of the program. The rest of the program should be the same, but I rather not upload it and cause confusions.

1. Yup, you can close the windows using the close button or by hitting alt-F4 (this is defined in the program itself, so it should work on all platform). edit: actually, I looked into the code again, and it looks like I’m letting SFML handle the window closing events, so you close the program however you normally close the program in whatever OS you’re using. I also noticed that Pinguino might be using a lower res screen, which might be what is causing this problem. The windows should be resizable, but that might be hard depending on how it’s positioned on the screen. I’ll try and fix this later.

2. It actually use up an entire core. This is a property of SFML, which was designed for games, unfortunately. If it’s using up 40% of your CPU, then I’m guessing you have a dual core CPU. I have a quad core, so it only use ~20% of my CPU. It was something I didn’t realize until I began learning this framework, and was too invested by the time I found out to switch over to something else. It might to worth it to rewrite this in .Net or something.

Prospective users should realize that much of the CIECAM02 color gamut is outside the gamut of a typical home computer monitor. So, many of the colors (particularly the most chromatic) are only “suggestive” of the real color.

This is quite important to note

Here’s a sample CMakeLists.txt in case you need it (main.cpp no longer exist + some case sensitivity stuff + maybe a bunch of other changes are required).

[code]
cmake_minimum_required(VERSION 2.6)
project(ciecamviewer)

include_directories(“./imgui”)

add_executable(ciecamviewer main.cpp ciecamviewer.cpp colorwheel.cpp color.cpp viewingcondition.cpp colorschemer.cpp pigmentlocator.cpp imgui/imgui.cpp imgui/imgui_draw.cpp imgui/imgui-SFML.cpp imgui/imgui_demo.cpp)

set(CMAKE_MODULE_PATH “${CMAKE_SOURCE_DIR}/cmake_modules” ${CMAKE_MODULE_PATH})

find_package(SFML 2 REQUIRED system window graphics audio)
find_package(OpenGL)

include_directories(${SFML_INCLUDE_DIR} ${OPENGL_INCLUDE_DIR})
target_link_libraries(ciecamviewer ${SFML_LIBRARIES} ${OPENGL_LIBRARIES} -lstdc++fs)

install(TARGETS ciecamviewer RUNTIME DESTINATION bin)
[/code]

Glad my program was of help to you! Good luck with your project