Here’s the link to the weekly snapshot of darktable 3.7, https://drive.google.com/file/d/1R29GYTUpNhyPHm37Qxt7iabVaziBorTX/view?usp=sharing. New this week is an additional vectorscope, RYB.
Where do we report issues for each new Win64 build?
Awesome - Thanks for taking the time to build this, and publish it.
I will add though, since 3.6.0.1, I have been so satisfied with dt, this is the 1st time in weeks that I have made the effort to come to pixls, to check up on any posts related to dt.
2 Likes
Thanks again for doing this Bill, it’s a real timesaver
I have to say that I’ve had a lot darktable crashes and even Windows level crashes under 3.7 than I’ve seen under any prior build. I still don’t have enough information to submit a GitHub report, but I wonder if anyone else is having the same problem
1 Like
Greetings, First I really appreciate all the hard work that goes into DT and DT Win. Second, you are providing a great service by allowing us to checkout and troubleshoot the latest Win snapshot.
However, if you look at my only issue report they are kind of saying this is Linux software. I got the distinct feeling my issue was annoying them which is the last thing I want to do as I really respect all the hard work that goes into DT…
I don’t know what issue you are referring to but, as has been mentioned before, we have very few developers who can work on Windows-specific issues. It’s not that we don’t want to support Windows, more that pretty much all of the developers are Linux users and aren’t able to provide Windows support. If you know any Windows developers who would like to help out it would be much appreciated.
Can you provide the issue number or a link to it please?
Not wanting to upset anything is there anyway we can report our issues directly to the existing Win developers as I personally regrettably cannot recommend anybody to help with development.
I will look again but they closed it…
GitHub is the place to report all issues. If they look to be Windows-specific someone will tag them as such. Sadly I’m not sure “Windows developers” deserves the plural yet.
Whoever it is there work is deeply appreciated!
Looking at this, I think it was closed as “not an issue: working as designed” rather than “we won’t fix it because it’s a Windows issue”. Unfortunately, in using backslash as a directory separator Windows is very much the odd-one-out here - Mac and Linux both use forward slash. Given that most developers and (I believe) most users are on Linux, we prefer to (slightly) inconvenience Windows users than everyone else so backslash is defined as an escape character.
The solution to your issue (use two back-slashes or, I think, use a forward slash) was provided. It might be worth adding a sentence to the user manual though as I don’t think this is explained.
I totally agree adding adding two backslashes is little price to pay for such an awesome product. I do believe the manual should warn Windows users of the situation. Beyond that issue should we still report Win problems there… It is hard to know if our issue is Win related or more global.
Yes. Report all issues on github. If a developer can’t replicate it on Linux it will be tagged as a Windows problem so someone else can (hopefully) pick it up.
It could also be that the path is a URI, which specifically uses backslashes, even on windows. This is what should be used when writing paths into the database.
Mark-64, who replied to your issue, is the most active windows developer at the moment and the one who has gotten windows paths working with imports as well as cleaning up some other path related issues.
1 Like