We've been thinking a bit about this and your other post. Maybe the easiest way to get this would just be to add a setting to make the arrow keys behave the same as the slideshow? Or just add Slideshow Next and Slideshow Prev to the shortcut settings? Then you can set all the settings you want in the slideshow UI.
Thank you for the suggestion! Even though this is a late response, we just wanted to say that we read all suggestions and appreciate everyone that takes the time to write one, even if we don't always have time to respond to each one! We'll add your suggestion to our notes and let you know if we get to adding this feature in the future :)
Thanks for the suggestion! You can currently kind of achieve this with the rectangle crop tool, you just have to first rotate your image. We'll make a note that you would like to see a lasso or similar in the future!
Thank you for the suggestion! We try to store the original location of images (works mostly when you drag & drop) that you can access with the Open source command, or view and copy in the Coordinate picker.
Thank you for the suggestion! You can use the Comment feature to add hidden notes to items. PureRef also tries to store the original location of images (works mostly when you drag & drop) that you can access with the Open source command.
Glad to hear it helped! PureRef 2.1 shouldn't actually use any more memory than 2.0, but we've noticed that Windows is a bit more aggressive with offloading idle memory in the background, and re-loading a lot of that at the same time seems a bit slow sometimes... Of course it could be a bug introduced in 2.1, but we're not able to reproduce the issue on our side so in that case it m
Thank you for the details! Have you tried different values for the performance mode, for example Cache on disk? It sounds like it could be a memory issue but it is strange that it happens for very small scenes as well in that case. Does it gets slow when you leave PureRef for a while and come back to it later?
It would also be interesting to know if it helps to downgrade to 2.0.
Thank you for the report! Does this happen even when exporting all images or only when exporting selected? Do you use groups or does it happen even if no selected images are grouped or parented? Could you make a small screen recording showing the issue so that we can understand it better?
Thank you for the report! We haven't seen this issue on our side, are you able to make a small screen recording to show the issue so that we can understand better what's going wrong? Alternatively if you can setup a test scene that has a structure that triggers the bug that we can test?
We're sorry to hear that you're experiencing issues with PureRef. We're not exactly sure what the reason might be for you but if you can answer some questions we might be able to narrow it down:
- Which operating system are you using?
- Does it happen for all scenes or only a specific one? If it is a specific one, can you share it with us so that we can take a look? In that case
@SorkinQuinzel: You can still drag and drop as usual onto the recent files widget to create a new scene. We understand that it is not as obvious especially when the window is smaller, we'll try to make it clearer in the future!
Thank you for the detailed report! We'll make sure to fix this in the next version of PureRef. Double commas are probably a good solution but we'll also document it in the handbook when it is released.
PureRef does not currently have the ability to send images directly for printing. What you can do is to either export the scene or, to make the process faster, use the new Copy as file function to quickly copy a selection and then pasting it to explorer as a file that you then can print.
Thank you for the kind words, we're happy to hear that you find the new cropping features useful! You can always "donate" by buying PureRef again, since we provide the pay-what-you-want model, but spreading the word always helps a lot too!
Thank you for the report! Unfortunately your link doesn't seem to work, can you upload it somewhere else?
Could you provide some more details about your setup:
- Which operating system are you using?
- What type of input device are you using?
Yes, we saw, but if you can share the image itself in its original size we can import it into PureRef to see what's going on better. But if you've tried the options this is currently a limitation of the rendering of PureRef. We'll note that this is something you would like to see improvements in, and see what can be done for future versions.
Yes! You can either use Export selection as scene (With the drawing and image selected, or checking the include children checkbox), Or Copy as file and then paste to where you want the image to be located on your system.
The thing that happens when you double click a file in explorer is that explorer starts a new PureRef process. That process then needs to communicate with any already running PureRef process, for example if you have changed the setting Open files in... we need to tell the other PureRef instance to open the image instead. It seems that this communication step fails on your end, unfortunately withou
This is always a balance between performance and accuracy unfortunately. Would you mind sharing an image that you think illustrates the issue the best for you so we can take a look at it? There's a few settings that impact how images get downsampled during rendering; Toggle bilinear sampling and Performance mode. Have you made any changes to these or are you using the defaults?
Can both of you check the logs in the settings dialog under System -> View log to see if there's anything in there that could give a hint? It could also be worth to test resetting the settings, you can do that by deleting the settings file (find where it is located here), but before you do please make a copy of it so that if it helps we can take a look at it and figure out what might be th
Thank you for the details! We'll make sure to make the thumbnail loading non-blocking in an upcoming version, and at that point it would be super helpful if you can give it a go just to verify that it solves the issue :) We'll let you know when it's available!
Thanks for the logs! Can you check in the task manager in case there's any PureRef process that has hung in the background? Or if a restart of the PC helps. If the issue is still there, you could also try to delete the PureRef folder in %TEMP% (C:\Users\user\AppData\Local\Temp\PureRef).
The issue seems to be that PureRef tries to communicate with another instance of PureRef but gets no res
How many images are in the folder? Can you also check if there's any relevant info in the log that you can view in the settings under System -> View log when a load fails?
If this happens for any image it could be worth looking at the health of your drive, both the system drive and the drive that holds the original image. Is it fast to just view the image in the system image viewer?
If it only happens for a specific image, could you share one with us so we can take a look?
When PureRef fails to open them, do you get any error message?
Thanks for reporting back! We'll try to make this not block the startup sequence in a future update, although it is a bit excessive that it should take that long. How many recent scenes shows on the start screen for you? Since it goes faster for subsequent startups it sounds like you have one or multiple drives that takes a while to start up (but that sounds more like an HDD issue)
Sorry to hear that you're experiencing issues with the update! We did make some changes to try to use the platform file browser so it might be something that is not working correctly on your install. Do you have xdg-desktop-portal installed?
Thanks for the report! This is a bug in 2.0 that has been fixed in 2.1, but unfortunately you have to update once before it is solved. It usually works if you select to try to close them anyway since Windows won't let you do it. If you don't want to try you can re-download PureRef and run the installer instead. Sorry for the inconvenience!
@Albert Street: That sounds like something might be bugged, there's no cache required for the startup, and the version check is happening in the background and shouldn't block the window from appearing. Which operating system are you on? Some things to try to narrow down the issue:
- Make sure no network traffic is going on by also disable anonymous usage statistics if you haven'
