02-18-2025 04:17 AM
If the filename don't fit into the Path control the abbreviation cuts out all and shows nothing. It should show something, right? Like "...\...-d21e141c5ce2_1.pdf"
LV2019, LV2024
02-18-2025 07:10 AM
Hello,
You can set it to Clip path, to display partial path.
Regards,
Mano Prabha
02-19-2025 02:55 AM
@mano123 wrote:
Hello,
You can set it to Clip path, to display partial path.
Yes, but then i only see the beginning part of the path, i want to see as much of the file name as possible. "C:\user\Documents" doesn't tell me much. 🙂
02-19-2025 03:10 AM
Hi Yamaeda,
@Yamaeda wrote:
Yes, but then i only see the beginning part of the path, i want to see as much of the file name as possible. "C:\user\Documents" doesn't tell me much. 🙂
So the described behaviour is not a bug, but "just unwanted/unexpected" because you want a "different behaviour"?
Workarounds:
02-19-2025 06:17 AM
Another try:
1. If you want to keep the appearance of the path control (path glyph) place a transparent string control on top of the path control. The path control gets the font color to white.
2. The string control needs to be set to "Limit to single Line" and unchecked at "Enable Wrapping", the "Text Overflow" setting needs to be unchecked, the text alignment needs to be set to "right"
3. In the "Value Canged"- event of the path control the value of the string control gets updated.
Another advantage of this is, that even too long filenames for the control will be shown with as many letters as possible.
02-21-2025 06:52 AM
@GerdW wrote:
Hi Yamaeda,
@Yamaeda wrote:
Yes, but then i only see the beginning part of the path, i want to see as much of the file name as possible. "C:\user\Documents" doesn't tell me much. 🙂So the described behaviour is not a bug, but "just unwanted/unexpected" because you want a "different behaviour"?
Workarounds:
- Put the whole path into the tipstrip of the path control: now you could read the whole path when you hover the mouse of the control…
- Enlarge the control…
We can ofc show nothing in the control, that'd be the strongest abbreviation ...
02-21-2025 11:21 AM
I don't know if this a bug, but maybe a lack of rules.
If you ever read about TeX, you would know there are all sorts of typesetting rules as far a spacing goes or extending into the margins, where to put a break, etc. It's why a TeX document looks and reads so much better than a similar Word document.
My guess is there are simple rules for the path control as to where to abbreviate, and if none of those rules can be applied, then it defaults to the dots you see. I also guess that some of the rules are probably hidden property nodes or special ini file settings. Maybe NI can release them so we can modify the rules to our liking.
02-24-2025 08:56 AM
@mcduff wrote:
I don't know if this a bug, but maybe a lack of rules.
If you ever read about TeX, you would know there are all sorts of typesetting rules as far a spacing goes or extending into the margins, where to put a break, etc. It's why a TeX document looks and reads so much better than a similar Word document.
My guess is there are simple rules for the path control as to where to abbreviate, and if none of those rules can be applied, then it defaults to the dots you see. I also guess that some of the rules are probably hidden property nodes or special ini file settings. Maybe NI can release them so we can modify the rules to our liking.
That would ofc help a lot, though i would assume it'd show as much as possible in the available indicator as standard.