system_profiler doesn’t tell you, but the display is scaled to look like 1680x1050 (according to the Displays System Preferences panel).Īccording to Cocoa, the backingScaleFactor for this display is 2. I get: system_profiler SPDisplaysDataTypeįramebuffer Depth: 24-Bit Color (ARGB8888) Resolution: 1920 x 1080 (1080p FHD - Full High Definition)įramebuffer Depth: 30-Bit Color (ARGB2101010) Metal: Supported, feature set macOS GPUFamily2 v1 Maybe the program could take advantage of that info? $ system_profiler SPDisplaysDataType Get newsletters and notices that include site news, special offers and exclusive discounts about IT products & services. So for those with a Retina display, that would be indicated, where mine below says 1080p. Get notifications on updates for this project. The command system_profiler SPDisplaysDataType will output the info about the GPUs and displays. I suppose there is more to do with icon size/padding and mac resolution, I got the impression that there was a problem using the Retina display (4K/5K etc) on mac laptops and those monitors in general. I think the rc1 looks fine on 1080p, icons being large in icon-size-fix. There are a lot of glib assert failures, but there always have been on the mac version, so they’re probably harmless. (rawtherapee-bin:34747): GLib-GObject-CRITICAL **: 12:37:51.982: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (rawtherapee-bin:34747): GLib-GObject-CRITICAL **: 12:37:51.581: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (rawtherapee-bin:34747): GLib-GObject-WARNING **: 12:37:51.560: invalid cast from 'GtkMenuBar' to 'GtkWindow' Running rc1 with verbose=true produces a lot of output, the only bit I can see relevant to UI layout is: "Non-Default" font size(9) * scale(1) / fontScale(1.000) Link flags: -mtune=generic -headerpad_max_install_names -flto If someone could make a build of the icon-size-fix branch for macOS available, I’d be happy to try it.īuild flags: -std=c++11 -std=c++11 -mtune=generic -Werror=unused-label -mmacosx-version-min=10.9 -flto -Wall -Wuninitialized -Wno-deprecated-declarations -Wno-unused-result -Xpreprocessor -fopenmp /opt/local/lib/libiomp5.dylib -I/opt/local/include -Werror=unknown-pragmas -O3 -DNDEBUG -ftree-vectorize Lifetime, sometimes those efforts are overtaken by events.- unfortunately I don’t have a working build environement for RawTherapee at the moment. Version prior this bug is closed as described in the policy above.Īlthough we aim to fix as many bugs as possible during every release's Of Fedora, you are encouraged change the 'version' to a later Fedora To see this bug fixed and are able to reproduce it against a later version Thank you for reporting this issue and we are sorry that we were notĪble to fix it before Fedora 19 is end of life. Plan to fix it in a currently maintained version, simply change the 'version' Package Maintainer: If you wish for this bug to remain open because you Approximately 4 (four) weeks from now this bug willīe closed as EOL if it remains open with a Fedora 'version' of '19'. It isįedora's policy to close all bug reports from releases that are no Has stopped maintaining and issuing updates for Fedora 19. This message is a notice that Fedora 19 is now at end of life. #3 Gtk::Widget_Class::button_release_event_callback at :4673 #2 ImageArea::on_button_release_event at /usr/src/debug/rawtherapee-4.0.11/rtgui/:247 #1 CropWindow::buttonRelease at /usr/src/debug/rawtherapee-4.0.11/rtgui/:370 #0 LWButtonSet::releaseNotify at /usr/src/debug/rawtherapee-4.0.11/rtgui/:129 Version-Release number of selected component:Ĭrash_function: LWButtonSet::releaseNotify Howerthe program immediately became unresponsive and crashed after couple of seconds. I have clicked on "open detail window" button twice too quick and it dispalyed two such windows in the picture area.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |