New Windows builds

The first time I started Gimp on Windows, I didn’t see the main Gimp window because it was mostly off-screen on the left. That’s what I believe. There are icons all over the left part of my screen and the portion of the Gimp window on the screen as I saw it on my second try was a thin vertical line which was quite easy to miss. I saw that line the second time I tried because, at that point, I felt mystified and looked more closely.

It happened to me before on my TabletPC that I started a program and the window opened off-screen. That was the first time I met that issue on Win10.

That’s right, my experience is that Gimp starts quickly whatever that “Legacy diskette A” setting is set to in the Bios. RT is sensitive to that setting though.

I believe you are talking about delays when opening files from the Gtk file browser. Isn’t that a different issue than the slow start problem? I ask since I am new to those problems. I did a quick search on Google and found some people experiencing delays on NFS and Samba. My own experience using Gimp on Windows earlier today is that I found it surprisingly responsive, and I didn’t experience any abnormal delay. I didn’t try opening a file on the network yet. I will do that the next time I boot my PC. Well I just tried minutes ago to open a network file from RT on the TabletPC but the network locations are not listed within RT.

We’d need to send you a build with debug messages displayed at various stages while loading to be sure. Speaking of which, have you had time to try the “verbose=true” test I mentioned?

My bad. I also missed that one. Here are the results.

First, about the Gimp test. Why the Gimp window was off-screen in the first place? I think I have some clue.

  1. This PC is dual-monitor with the main monitor on the right and the left monitor turned off most of the time. So any activity on the left monitor might escape my attention.
  2. That PC initially ran Vista and I likely installed Gimp at least once and then uninstalled Gimp but the config file, which is created after the install was leftover. After the migration to Win10 the Gimp config file was probably still there and the new Gimp install I did yesterday reused that old Gimp config file. So if the last time I used Gimp on Vista, the main Gimp window was on my left monitor, that’s where the new Gimp install would start it.

Back to your question, here is the listing you asked for. That test was done after I set ‘Legacy diskette A’ to ‘1.44 MB 3.5 in’ in the BIOS. I list the output of the RT console. I included some lines of the Mingw console but didn’t include the full listing since it is long and uninformative. I will post it if you need it though.


2016-10-10

All times are Greenwich based and rounded to the minute.
My notes are in brackets <>. RT wrote on its own console.

<14:35 On Mingw console>

> (date; rawtherapee.exe 2>&1; date) | tee /d/live/Downloads_Windows/start_rawtherapee.txt
 ...
file c:\Program Files\RawTherapeeMaster\.\profiles\Skintones\Skintones - StudioBase 1 TM.pp3...OK
file c:\Program Files\RawTherapeeMaster\.\profiles\Skintones\Skintones - StudioBase 1.pp3...OK

<14:36 On RawTherapee-4.2.1234 console.>

RawTherapee, version 4.2.1234
WARNING: closing this window will close RawTherapee!

< After a couple of minutes.  My notes>

**************** FileCatalog::getFilter *** AFTER STEP 1
filter.showRanked[0] = 1
filter.showRanked[1] = 1
filter.showRanked[2] = 1
filter.showRanked[3] = 1
filter.showRanked[4] = 1
filter.showRanked[5] = 1
filter.showCLabeled[0] = 1
filter.showCLabeled[1] = 1
filter.showCLabeled[2] = 1
filter.showCLabeled[3] = 1
filter.showCLabeled[4] = 1
filter.showCLabeled[5] = 1
filter.showEdited[0] = 1
filter.showEdited[1] = 1
filter.showRecentlySaved[0] = 1
filter.showRecentlySaved[1] = 1

<14:38  RT white screen. My note>

(rawtherapee.exe:360): Gtk-WARNING **: Failed to fetch network locations: Error
opening directory 'c:\Program Files\RawTherapeeMaster\network:': No such file or
 directory

(rawtherapee.exe:360): Gtk-WARNING **: Failed to fetch network locations: Error
opening directory 'c:\Program Files\RawTherapeeMaster\network:': No such file or
 directory

(rawtherapee.exe:360): Gtk-WARNING **: Failed to fetch network locations: Error
opening directory 'c:\Program Files\RawTherapeeMaster\network:': No such file or
 directory

(rawtherapee.exe:360): Gtk-WARNING **: Failed to fetch network locations: Error
opening directory 'c:\Program Files\RawTherapeeMaster\network:': No such file or
 directory

(rawtherapee.exe:360): Gtk-WARNING **: Failed to fetch network locations: Error
opening directory 'c:\Program Files\RawTherapeeMaster\network:': No such file or
 directory

(rawtherapee.exe:360): Gtk-WARNING **: Failed to fetch network locations: Error
opening directory 'c:\Program Files\RawTherapeeMaster\network:': No such file or
 directory

(rawtherapee.exe:360): Gtk-WARNING **: Failed to fetch network locations: Error
opening directory 'c:\Program Files\RawTherapeeMaster\network:': No such file or
 directory

(rawtherapee.exe:360): Gtk-WARNING **: Failed to fetch network locations: Error
opening directory 'c:\Program Files\RawTherapeeMaster\network:': No such file or
 directory

(rawtherapee.exe:360): Gtk-WARNING **: Failed to fetch network locations: Error
opening directory 'c:\Program Files\RawTherapeeMaster\network:': No such file or
 directory

<14:39  RT screen all painted. My note>

**************** FileCatalog::getFilter *** AFTER STEP 1
filter.showRanked[0] = 1
filter.showRanked[1] = 1
filter.showRanked[2] = 1
filter.showRanked[3] = 1
filter.showRanked[4] = 1
filter.showRanked[5] = 1
filter.showCLabeled[0] = 1
filter.showCLabeled[1] = 1
filter.showCLabeled[2] = 1
filter.showCLabeled[3] = 1
filter.showCLabeled[4] = 1
filter.showCLabeled[5] = 1
filter.showEdited[0] = 1
filter.showEdited[1] = 1
filter.showRecentlySaved[0] = 1
filter.showRecentlySaved[1] = 1

<14:50  Crtl-Q Exit RT> 
<14:51 Exit script>

Thanks @rlx009! I edited your post and included code marks to make the log more readable, hope you don’t mind.

You’re welcome.

The latest Windows 64-bit builds (Release and Debug) can be downloaded from here:

5 Likes

You forgot to change builds numbers !
1122 or 1291

##mode étourdi ON##

Oups… Merci encore une fois :stuck_out_tongue_winking_eye:!

Merci à toi !

In an attempt to keep this particular topic a little cleaner I’ve moved the help request with @TooWaBoo’s theme:
14 posts were split to a new topic: Help with theme and scaling

My old WXP PC is dead!
So I installed the msys2 toolchain on my new 64bit W10 PC. It was difficult and I think there are some bugs in the new installer.

I am first building 64 bit RT (master and GTK3), but with gtkmm 3.22, the RT UI is really ugly.
So, @sguyader could you upload GTK and GTKMM 3.18 64 bit packages that you could find in
[MSYS2 installdir]/var/cache/pacman/pkg
the names of packages could be something like
mingw-w64-x86_64-gtk3-3.18.x-y-any.pkg.tar.xz
mingw-w64-x86_64-gtk3-3.18.z-w-any.pkg.tar.xz
After installing them, I will suppress automatic update for those packages.

I am going to install and try mingw32 to build 32 bits versions.

André

@gaaned92 André I’m sorry, but it looks like at some point I purged the packages cache from my msys2 environment, I don’t have the gtk[mm]3 packages anymore. Isn’t there an archive of these packages on the internet?

@gaaned92 try this link, it seems to host an archive of the new and older versions of all the packages.

@gaaned92 we are actively working on adding support for Gtk+ >=3.20 to RawTherapee, so you soon should be able to make builds using that. Follow Add support for Gtk+ 3.20 and/or 3.22 · Issue #3446 · Beep6581/RawTherapee · GitHub

@sguyader thanks for the link
@Morgan_Hardwood I am aware of your efforts to solve the issue. As I am not able to help you, in the meantime, I will use 3.18.
I hope that the future GTK3 releases will remain compatible with 3.20,3.22
Edit : I found on the linked site the 3.18 versions, but the build fail due to missing entries in the" dlls. So I give up and wait for the 3.20 version

You will find in my W32 RT drive an
experimental master branch 4.2.1165 Windows 32bits release build.
This build is made on windows10 64bits. I tested it on this PC. It is a 32bit application and it runs ok on W10
Give me your feedback if it runs ok or not on your 32 bit PC.

Hey @gaaned92
I confirm that RawTherapee_WinXP_32_master_release_4.2.1165.zip works fine in Windows XP 32-bit.
But the installer wants to install to C:\Program Files\RawTherapee-master-release-4.2.1165 and to use RTmasterrelease4.2.1165 as the Start menu folder name. It would be much nicer if it installed to %PROGRAMFILES%\RawTherapee and used RawTherapee as the start menu folder.

How do you do that? have you an old pc with XP?

To do that, the modification of WindowsInnoSetup.iss.in is straightforward. Replace
line 51 by DefaultDirName={pf}{#MyAppName}
line 52 by DefaultGroupName={#MyAppName}

These modifications should be checked and commited by @Hombre

But, while for the usual user, this will make install surely easier, for the user who wants to install a few versions (release, debug, different branches, different bit depth) to test or experiment, multiple installations will become an hassle.
So I propose that for stable version (or when you ask for) I use the above modified windowsInnosetup and I keep as it is for development builds.

Do you agree?
André

I run Sabayon on my work laptop with Windows XP in a virtual machine.

I agree, with a small tweak. How about this:

  • Official releases use %PROGRAMFILES%\RawTherapee as the default installation path.
    Nightly builds use %PROGRAMFILES%\RawTherapee-branch-version-buildtype (buildtype at the end).
  • All releases put shortcuts into a “RawTherapee” start menu folder.
    The shortcut name is RawTherapee 5 (or 5.1, 5.2, etc) for official releases, and
    RawTherapee branch version buildtype for nightlies.

Then things look nice for people who only install official releases and for people who install nightlies.

1 Like

As I will build 32 and 64 bit builds on the same pc, I would like to add the bit depth for nightly builds.
I have to test the second point.