You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, if you have any Haxies, InputManagers, SIMBL plugins or
similar operating system hacks installed, please remove them first, restart
the program, and make sure the bug is reproducible without them.
> No, none in place.
What steps will reproduce the problem?
1. Browse a file in a directory "A" (mine had 3700 items in it)
2. Check prev/next works; and you can browse the directory
3. Drag another directory "B" onto the Xee dock icon (~4000 items in it for me)
4. Browse images in directory B
5. Using the shortcut key to previous 'copy destination' (Cmd-1 in my case)
copy images from B -> A
6. Copies work fine, but after a few attempts the windows showing the file
from 'A' turns to 'static', and reports 'No images found' at the bottom
7. Doing prev/next brings up file-open dialog (Xee does not have
permission...); but after clicking 'open' it still reports 'no images found'
What is the expected output? What do you see instead?
- the 'A' directory image should never change (except for the count of how many
files are in that directory)
- I have previously authorised directory 'A' -- so don't quite get why i need
to reauth it in the first-place.
What version of the product are you using? On what operating system?
- 3.0.5 (22) via App Store
Please provide any additional information below.
- the first 1-2 times this occurred; i _believe_ doing steps 7 worked - and
after re-authorisation it resumed browsing the directory from the previous
image. However, i can't get that 'workaround' to function this time.
- If i quit Xee; and re-browse the A & B directories it works (e.g. is auth'd)
-- but this problem pops up again, reasonably consistently.
Original issue reported on code.google.com by [email protected] on 4 Aug 2013 at 6:56
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 4 Aug 2013 at 6:56The text was updated successfully, but these errors were encountered: