XYplorer Beta Club

Thanks Don. I was thinking at the time, even though files like exes don't currently generate a hover box, maybe a possible answer would be to have some obligatory hover box for exes (and maybe some others) similar to a "cannot decode" error but maybe instead display "executable file" or just the file name. So, when an exe file is encountered with hover box, the box would simply show the exe file name or something similar. This would allow continuing hover box movement with the arrow keys to the next file.

Exactly what I did.

Beta v24.30.0107 works great. I can travel through a folder full of miscellaneous file types without Hover Box being disrupted. It makes for a more pleasurable Hover Box experience.

While I can see this change making sense when you are using the keyboard to navigate with HoverBox showing, depending on the config settings, getting a HoverBox with no info in it instead of an InfoTip containing shell properties isn't desired when using the mouse. I exclude filetypes from HoverBox because I am more interested in the InfoTip, instead showing a HB with minimal info isn't helpful.

So now I guess I have either got to change to showing HB to only when over the icon, which slows down being able to invoke, on the filetypes its actually wanted for, or always use a modifier. It also creates an issue with config settings, because now if certain InfoTip settings are checked, they don't do what they say, you always get the HB now if enabled.

Hi jupe, I suppose everyone has difference taste when it comes to showing Info Tips and Hover Box. After a while I just found it to be irritating having Info Tips, or Hover box for that matter, popping up everywhere when I moved my mouse over filenames. So, I ended up doing Hover Box only on icons and Info Tips on filenames but only with shift key help down. I don't need to see Info Tips all the time unless I really need to see them. As far as hover box goes, well when it's set to only on icons at least it's not popping up everywhere. But I see your other points on Configuration conflicts.

jupe wrote: ↑19 Apr 2023 19:38 showing hover box to only when over the icon, which slows down being able to invoke

Why is that if you have an initial delay set to "0"? Is it because of the "allow dragging items by thumbnail" setting? I keep that disabled because it puts a minor delay on MDBU. Are you saying that setting also affects hover box? Maybe you're simply talking about the additional time it takes to move over the icon in lieu of the filename.

klownboy wrote: ↑19 Apr 2023 20:51 Maybe you're simply talking about the additional time it takes to move over the icon in lieu of the filename.

I am. I guess I will have to get used to the new way, but for me it was convenient disabling HB for filetypes I didn't want to see it, and then on those I do like images I could quickly invoke it on the whole length of the file name on those types, and not have to be super accurate, now I need to change my settings to either use a modifier, or only over icon for HB. And now the settings don't really reflect reality under certain constellations, and disabling HB categories seems pointless now under most conditions.

Yes, I forgot about the option to actively disable the hover box for certain file types. The next beta will restore the previous way for normal mouse-triggered HBs, and keep the new way only for key-triggered HBs.

Don, would it be out of the realm of possibilities to have the info tip display instead of hover box in cases where you encounter files that display a no preview or cannot decode message? In other words, it would be a kind of cross over event between hover box and info tips. They are two separate features and controls so that may be out of the question.

I had the same thought and made some experiments. Did not work well. Too many side effects and complications.

OK Don, I kind of figured it would be a nightmarish idea. I suppose if you were at the very starting point of implementing hover box and info tips it would be one thing, but now with both firmly in place and working, it's quite another.

v24.30.0001 - 2023-04-13 17:36
+ Hover Box: Now you can move the Hover Box to another item using the arrow keys
(Left, Right, Up, Down, PageUp, PageDown).

I like this feature, is it possible to remove the preview size limit? I want to zoom in on the preview image as much as possible, and then the image should be displayed from the top as much as possible?

Nah, not really part of the plan.

Hi Don, was this ever done, earlier in this thread viewtopic.php?p=210097#p210097 ? It was to actually initiate the Hover Box display for the file under the current mouse position. We can currently turn the hover box capability on and off and escape frim HB, but this was to actually display HB via a command ID or script command regardless of those settings.

This was done: Miscellaneous | Focus Functions | Trigger Mouse Move

OK Don, I saw Trigger Mouse Move and read more about since your reply.

+ Miscellaneous | Focus Functions: Added command "Trigger Mouse Move". Triggers a fake
mouse move at the current mouse position. Allows you, for example, to open a Hover
Box or File Info Tip using the keyboard if the current mouse position is suitable.
FYI, I personally assigned Shift+Esc to it (to reverse HB-hiding Esc).

I suppose I'm still not sure what that's supposed to be doing. I assigned it "Shift Esc" as you mentioned in the Beta notes. It doesn't trigger the Hover Box on for me when I'm over the file or icon. I'm not sure what the mouse positioning supposed to be to accomplish that.

Separate question, that's probably more important (to me). If I'm simply hovering over a file, is there a scripting command or Command ID that would give me the filename/path of the file I'm hovering over. I know I can get SC indexatpos, but it would seem to make scripting sense and also be worthwhile that we could in one command get the actually file name being hovered. If not, could we get a command that would do this? You've obtained that information for HoverBox. Edit: Possibly a SC get("HoveredItemPathName"), similar to the existing get("SelectedItemsPathNames").