1
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Can you try this for me just to see if it gives any more clues:
Open up your LBC configuration and select some node you don't care about.
Now drag and drop a file onto the ICON IMAGE.. Normally this has LBC replace the node icon with the one representing the file you've dropped. I'm just curious if that also causes an error when you drop pdf/text files onto it.
And you're using the latest version of LBC?Yes, the latest. Installed with the setup in: "C:\Program Files(x86)\LaunchBarCommander"
Can you try this: download the portable version and unpack it somewhere and run it (exit your normal LBC); that will give you a new file.Closed down existing LBC and installed/run the portable version. Dropped a known good PDF onto the default bar (not via config. window), immediately the same access violation - see below.
Try dropping adding the pdfs to that new bar. Let's see if it happens right from the start
In your photo the command path looks like its not set -- I wonder if that's a clue.Can't be sure but it may be blank due to the access violation. Otherwise LBC presumably will not try to get access to the pdf.
Which makes me wonder if it's something about the pdf file or the configuration in LBC that is making it confused.It happens with known good pdf's. Some time ago it came to mind there may be a configuration file issue, so I made a new bar and dragged over my nodes but no luck with that. It does look like it's more likely to be something in the configuration, the mystery is what.
If you drop a new different pdf file (one made a different way ideally), onto the config, does it have the same problem?Yes, the access violation happens immediately on dropping.
If you can figure out any more clues as to when this problem happens let me know.I haven't previously investigated this much in case I can't access it at all. But to get more info, I now find that the same access violation (same address) happens with other files too. All my .chm files and strangely some .bat files. The same bat file under a node I can click on but the same bat file under another node gives the error.