In the popup tool tip that pops up when you drag a item and hover between btns there is a icon and a path, when that path next to the icon is truncated due to length.
Ok, everything with CTBs seems to be back to normal in .0329, thanks. :cup: I've been rolling back till now, so I'm just now starting to test BTBs properly, and have noticed that the BTB drop popup tooltip box that pops up when between btns, displays the ? icon when the path is truncated. Also a sug...
When you open XY config dialog on that PC, does the path in the titlebar start with a write protected location, ie Program Files, if it does then move it to another location, then reload it from there.
I'm just not sure how I could use the readurlutf8() part tho. You just want the page title right?, so I meant something like this, saves you from read/write/deleting a file. text gettoken(readurlutf8("https://youtu.be/watch?v=H4ZCmsyhtg4",, 1), 1, " - YouTube"); I thought readin...
If you don't mind having those UWP apps associated as the OS default for those filetypes, you can use CFA to open single items from XY in those apps. Your XY CFA entries of course can still override and not match the OS default.
The 25.80.0312 beta has messed up <drop> for CTBs, instead of any item names, the return is what looks to be positioning identifiers for BTBs, and if you don't drop, the return is unresolved <drop> instead of blank.
I still see the same issue in .0312. One other thing I noticed, is that in the help, the scripting definition line shows patchimage as a function instead of a cmd.
In v25.80.0310 beta, patchimage seems to have stopped working properly (default imgs shown instead), it seems to work at anything below 1x when using large btns, unless switch to XL which works if over 0.95x, small btns seem ok though.
First issue looks like your CEA script isn't indented properly, or that stream comment is messed up (no closing */?). The second issue sounds like a scripting issue too, do you in any of your CEA browse events (changing location) temporarily disable CEA, or anything similar (or via AHK), if you try ...
Because of your chosen wide font and fontsize the text from the line above is wrapping around and being hidden behind the Contents line, but you are still seeing the tops of some of the chars, given the layout constraints we'll have to see if the dev can/will be able to adjust it.