argumentum Posted 5 hours ago Author Posted 5 hours ago 2 hours ago, WildByDesign said: I always call it right after the includes. The earlier, the better. There is no need to first load #includes. But before creating any GUI stuff. If you have an experience that pushed you to the advise please share it. P.S.: where is your update / bettered / 2026 edition of the darkMode_mod.au3 ????, I will need it ( I've grown lazy ) WildByDesign 1 Follow the link to my code contribution ( and other things too ). FAQ - Please Read Before Posting.
WildByDesign Posted 5 hours ago Posted 5 hours ago 1 minute ago, argumentum said: The earlier, the better. There is no need to first load #includes. But before creating any GUI stuff. If you have an experience that pushed you to the advise please share it. You are 100% right. The earlier during process init the better. I think the only reason why I had it after includes was more a matter of keeping everything at the top looking clean and tidy. But realistically it should be right at the top, you are right. 5 minutes ago, argumentum said: P.S.: where is your update / bettered / 2026 edition of the darkMode_mod.au3 ????, I will need it ( I've grown lazy ) This is something that should be done. Needs to be done, really. I’m just afraid to step on any “toes” because I believe NoNameCode mentioned getting back into it for another version but also UEZ shared some incredible subclassing code for dark mode. I’m not sure which code would be the best “base code” to start with. It got much more complicated when it came to applying dark mode to statusbar, menubar, and a few other things. Trying to figure out how to add those methods to a UDF makes my brain start to smoke a bit. Plus having to overpaint that white line in a dark mode menubar. If organized and done right, it could be really incredible. We have all of those individual, beautiful pieces to the puzzle. But figuring out how to put that complex puzzle together in a single UDF is something that I may not be skilled enough for. But I am definitely willing to jump in and help with the dark mode stuff. Even light mode theming has improvements there too, so technically it would be good to run it and have the choice between applying light or dark.
argumentum Posted 5 hours ago Author Posted 5 hours ago Take a look at https://www.autoitscript.com/forum/topic/201673-json-http-post-serverlistener/page/2/#comment-1447447 for a how to JSON - AJAX ( the example on top when running the script ) to give you an idea for the example button(s) that is enclosed in "if (document.URL.match(/^mk:@MSITStore:/i)) {" Global $tcp_Port = 80 ; if 80 is in use, try 81, as in http://127.0.0.1:81/home/ that port should read from your ini file for now ( in the example I linked above ) Follow the link to my code contribution ( and other things too ). FAQ - Please Read Before Posting.
argumentum Posted 5 hours ago Author Posted 5 hours ago 2 minutes ago, WildByDesign said: I’m just afraid to step on any “toes” because I believe NoNameCode mentioned getting back into it for another version but also UEZ shared some incredible subclassing code for dark mode. I’m not sure which code would be the best “base code” to start with. Yes it will be the best, because you are the best ( don't tell anyone I said that ) An in regards to toes, fvk'em. There are no toes but if any toes popup, add a mention like: "..thanks to the crying baby @userName for parts of the code" WildByDesign 1 Follow the link to my code contribution ( and other things too ). FAQ - Please Read Before Posting.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now