Forum for XYplorer Users and Developers
https://www.xyplorer.com/xyfc/
Yep, that works, thanks!admin wrote:Without any testing I would say simply append the delimiter manually if you really need it at the end:
Code: Select all
$filelist = getinfo('SelectedItemsPathNames', '|') . '|';
XY != God.zer0 wrote:Yep, that works, thanks!admin wrote:Without any testing I would say simply append the delimiter manually if you really need it at the end:
Code: Select all
$filelist = getinfo('SelectedItemsPathNames', '|') . '|';
P.S. Would be nice for XY to identify such pitfalls and alert the user
Agreed. But not all people who use scripts are experts at scripting. I was able to narrow down the cause to a particular change of a specific beta release. Proactive action is not only smart, but also saves time which is in my case means money.admin wrote:XY != God.
You're a kind of right here...zer0 wrote:Agreed. But not all people who use scripts are experts at scripting. I was able to narrow down the cause to a particular change of a specific beta release. Proactive action is not only smart, but also saves time which is in my case means money.admin wrote:XY != God.
Code: Select all
If your script depends on the now deleted trailing delimiter, you have to change it accordinglyCode: Select all
If you wrongly misused the token separators including the last one as a kind of end-of-token-identifiers, you either have to add a separator to the end of the string, or change the logic to interpret the string as character-separated tokens.Code: Select all
rename s, "text.to.remove./";Not arguing against teaching Search & Replace some new tricks, but could you not use regex here instead?zer0 wrote:However, if that string is at the end of the base name, XYplorer refuses to remove it. My suspicion is that this is because it thinks that removing that dot would alter the extension and since there is no "/e" switch present, it does not proceed.Code: Select all
rename s, "text.to.remove./";
Code: Select all
rename r, "text\.to\.remove\. > ";I can, but not being very proficient in RegEx meant that it wasn't the first renaming method that I went for. Your method works, but that trick should definitely be taught to S&R.TheQwerty wrote:Not arguing against teaching Search & Replace some new tricks, but could you not use regex here instead?Code: Select all
rename r, "text\.to\.remove\. > ";
Code: Select all
<html><head>
<style type="text/css">
#a {
margin:0 10px 10px;
}
#b {
width:100%;
}
</style>
<title>Makes XYplorer non-responsive</title>
</head>
<body>
<table><tr><td>
<div id="a">
<form id="b">
<input type="text" name="test"/>
</div>
</td><td width="1"></td></tr></table>
</body></html>Problem confirmed, but since the conditions for problematic HTML code are not known there is no way to provide a safety net.zer0 wrote:Running html() with the following code causes XYplorer to stop respondingTechnically, it's not a problem with XYplorer, but IE. That said, since we can't help but use IE's engine, there should be some safety nets.Code: Select all
<html><head> <style type="text/css"> #a { margin:0 10px 10px; } #b { width:100%; } </style> <title>Makes XYplorer non-responsive</title> </head> <body> <table><tr><td> <div id="a"> <form id="b"> <input type="text" name="test"/> </div> </td><td width="1"></td></tr></table> </body></html>
I've run it through the W3C Validator, played around some more and I believe this is the error that validator flagged that is the cause:admin wrote:Problem confirmed, but since the conditions for problematic HTML code are not known there is no way to provide a safety net.
Changing that id from "b" to "a" -- in line with <div> tag's name above -- makes the page load fine.required attribute "ACTION" not specified
<form id="b">
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
Code: Select all
"Report Column Format Discrepency"
Sel 1;
$r1 = Report("{Created} {Size}", "<focitem>");
$r2 = Report("{Created} {Size}", 1);
Echo("F: $r1<crlf>S: $r2");That's on purpose. Giving a source list disconnects the report from the current list and it's formatting.TheQwerty wrote:Seems giving Report() an item list causes it to ignore the user-defined column formats.
Looks like it's been there since v9.40 so I'm guessing it goes all the way back to when Report was blessed with ItemList support.Code: Select all
"Report Column Format Discrepency" Sel 1; $r1 = Report("{Created} {Size}", "<focitem>"); $r2 = Report("{Created} {Size}", 1); Echo("F: $r1<crlf>S: $r2");
Errr why? Why wouldn't I want the formatting here?admin wrote:That's on purpose. Giving a source list disconnects the report from the current list and it's formatting.
Can't really give a good reply now. The reporting code is quite complex and I did not look at it for more than a year. No idea how many users are using these functions but yours is the first complaint. From first impression I agree with you and wonder why it is as it is. But I would have to look very deep to make a good decision. No space for this in my schedule right now.TheQwerty wrote:Errr why? Why wouldn't I want the formatting here?admin wrote:That's on purpose. Giving a source list disconnects the report from the current list and it's formatting.
If I didn't want the formatting I would have included the desired formatting in the template, but I didn't because I want the same formatting as the column.
This means if a user wanted to compare the data from the focused item with the rest of the items they now have to jump through hoops; especially if they need to then use this data in SelFilter which expects the filter pattern to be in the exact same format as the column.
Unfortunately "{Created List}" doesn't work either, and in this case that would be more of a pain since I'm getting the column/template name from a Get("Sort") in the first place.
I really don't understand why I'd want to ignore the current list formatting just because I'm using a source list?