May I ask what the limitations were that led to the result that the showText() function is this limited.
Simply that the code that displays the “showText” result is the same code that displays the PopClip pop-up itself. Indeed, the showText bubble is actually just a regular PopClip bar with one big a greyed-out button. And that code can only display one line of buttons.
Would it be a viable option to enhance it by passing an array of strings to showText()? So that each string in the array is an separate line in the popup-window?
Potentially. If I did it would be part of an overall re-write of the PopClip pop-up display & interaction capabilities. The actual PopClip bar display & button handling is actually the oldest part of the codebase. It would require a significant re-write of some core code so probably not any time soon. I’m quite conservative about feature additions and code changes. I don’t like to just bolt features on without deep consideration of how it factors in to to the usability, maintainability, simplicity and cohesiveness of the app.
Do you think that it’s possible make something like an showHtml() function? Or is this out the scope of this application?
I won’t say no! All this is great stuff. But, I’m just one person, just working on one thing at a time. I never promise features but I always listen to and think about the ideas people share. A lot of the best stuff in PopClip has come from user suggestions. So do keep on sharing your suggestions even if I do say “no” and “not yet” a lot
#popclip - classic YAML snippet
name: Sample AppleScript Dialog
set theDialogText to "The \n curent \n date \n and time is " & (current date) & "."
display dialog theDialogText
Thanks, great tip @NightBack and welcome to the forum.
Regarding F3, popclip.pressKey('f3') ought to work in general, but the way apps detect hotkeys can vary, and some apps will not detect PopClip’s presses. (For example, BetterTouchTool can’t see PopClip’s keypresses.)