You're welcome! I'm not sure what you are trying to do with OutputDebug but if it's working now then great! I'm not aware of any changes I've made that would influence this, other than I updated the version of AHK_H being used in the compiled script.hotkeyguy wrote: ↑09 Nov 2018, 15:42Hello GeekDude,
many thanks for CodeQuickTester v2.8, especially Save/Save As and rename. I just wanted to ask. And OutputDebug works now (not in v2.7). Yep, I got v2.7 compiled meanwhile. No problems starting v2.8.
Greetings and thanks for that early St. Nicholas' Day gift
You may have confused ribbon design with the Windows 10 window manager. I haven't done any significant theming changes other than reducing/removing margins in the main GUI. It may be possible to grab one of those window theming dlls that are basically drop-in addons for the script but I can't do that while maintaining the "all functionality should be available when using just one file" requirement I've been trying to uphold.CyL0N wrote: Sweet , but RIBBONS,where be the RIBBONS .... i guess i Can wait . But really though,much needed update so thanks.
A suggestion for the next patch, for status bar instead of , I think |, is a bit more poignant,comma just looks a little weird.
Something like this,
Code: Select all
SB_SetText("Len " Len " | Line " Row " | Col " Col . (Sel > 0 ? " | Sel " Sel : "") " " this.SyntaxTip)
As far as the status bar, I was mostly trying to copy how they handle the status bar in the popular new editor Visual Studio Code. A vertical pipe might be better, but maybe not. Microsoft has a reasonable design team and I would bet they've done UX testing on this topic and found people preferred the commas. Status bar design is definitely a point to revisit in the future.
I'm glad you like what I've been cooking up! I would also like to see it get tabs some day, but I think there might need to be some rethinking first. The more parts in a single script, the more likely that script is to hang or crash. If I am going to increase the propensity for crashing, I should consider what the script should do in the event of a crash: Should I introduce auto-saving to a temporary file for unsaved script panes? That's a little antithetical to one of the goals of the script (don't create temporary files). Is that goal still a good thing to shoot for?SpecialGuest wrote: Keep it comin' GeekDude
By the way: I would love to see this get tabs some day
Should I attempt to go for a browser-like approach where each tab has its own process, so that if one crashes it won't take down the whole editor? If so, how should I perform process management? There's an API in Windows to designate some processes as children to be killed when the parent dies but when I was testing it I couldn't get it to work.
So many options
Thank you for the nice comment!r2997790 wrote: Geekdude, thank you for your continuing hard work on CodeQuickTester. It's a wonderful tool.
I'm glad you haven't overloaded it with functionality. It remains a joy to use for testing code snippets and short routines.
I'm not sure what the threshold is for overloaded haha, I've been slowly adding more things to it over a long time. Working in it before there was a right click menu or a find and replace dialog just felt kind of... incomplete. I'm probably going to keep adding things until you change your mind .
SpecialGuest wrote:Desperate attempt at fixing integration (to be ignored lol) :
ozzii wrote: @SpecialGuest
Thanks for the update but I have this when I click to open on your code:
SpecialGuest wrote: Thanks for letting me know. Hadn't really had the chance to look at it very long last night.
Just saw the regular integration wasn't doing anything and attempted to fix the link.
It seems I didn't look at it long enough to notice the result being the whole page instead of the codebox' content lol
Consider this to be broken for now as we require the download link, which isn't available anymore on the current codebox..
With the download link you can retrieve the codebox' content but I don't see a way to do it with the forum being as it is atm.
I've been thinking of a way to make this work, and I'm wondering now if there's a way for me to jam the code into something like a Base64 string that I pass to the script instead of an http(s) link. Of course, this will depend on how much data is supported in one of those links but people use similar links to embed images into html so hey maybe it'll workozzii wrote:OK, I will wait for a fix, I hope....
I'm glad you like it! Configuring the window size and having it remember the last window size is on the roadmap already, so you can expect to see it in the future.kiwichick wrote: Hi there, this is such a nifty little script. So helpful! I have a couple of requests. First, will you please make it possible to open it maximised, or at least remember the last window setting? And second, will you please change the wording for "Open Help File" to specify that it's the AutoHotkey help file that's opened, not a CodeQuickTester help file? Keep up the good work. Cheers.
The help file link could be a little more descriptive, though I don't think it's especially misleading as it is. I can definitely update it to say something like "Open AHK Help File" instead if you'd like.
Yeah that's a known issue. I have no idea why it does that but if you figure it out let me know . If not, it's on my list of things to look at in the future.CyL0N wrote: Bug: Line Numbering Gets Messed Up With Ctrl+Home, Ctrl+End., given a script with more than 200lines...