TheDcoder

Okay, so it's an imposter

Uhh... I don't think that's a placebo, it's a placeholder

Don't worry, I'm sure @jchd will keep your erotica library a secret Or alternatively, you could delete all but a few entries in the database and send that instead.

Let's not forget about https://wormhole.app for easy file sharing needs, it supports files up to 10 GB.

Technically yes but it would be highly dependent on AutoIt's internal representation of maps and other internal state which you may not even know about. So in short, it's not worth it and it is a bad idea. I suggest that you just write some bridge code which serializes the "map" data in your DLL and then parse that serialized map in AutoIt to create a proper map. Yes, but it's not official, it's just something I did for fun a long time ago, it's still on my GitHub and maybe even here. It doesn't have anything special inside it... except maybe you can pass a Scripting.Dictionary object from your DLL? My UDF has a _Map_DictToMap function which will create a map from that.

If only I had a dollar for every time someone asks me if I code in the D programming language

What exactly is this abomination? Are they developing their own Windows runtime? I doubt it will be nearly as good as WINE, which has been in development for many years with commercial backing. If it's just a highly themed Linux distro, then it's just a gimmick like Zorin OS. You can install WINE in any Linux system... so unless you are looking to make your Linux system look like Windows (why would you anyway?), it's of no practical use. Also about Android Apps, there are several projects which allow you to run Android apps in Linux too, and I bet this project is using one of them.

As long it's valid JSON any parser worth its salt would be able to handle it, the internal structure doesn't matter.

Source: https://forum.dtw.tools/d/28-easycodeit-progress-flex-bison-parser/15

@phoenixhuynh09 No worries, I suggest looking up the help file and understanding the difference between Select and Switch. Also look up the ternary operator (? and : symbols), it should help you reduce conditional statements. If you are up for it, you can rewrite the function after learning and maybe even submit a PR at GitHub, I'll be happy to take a look

@phoenixhuynh09 Thanks, but are you sure that your code is correct? It seems you wanted to use "Select" and not "Switch" Also I think we can rewrite it without using such long statements

I'd suggest you just use an external program for the proxy server instead of trying to implement your own in AutoIt, would be much more easy and reliable that way.

Please don't necro-post old threads. I's suggest using a proper SOCKS server like this one: https://github.com/rofl0r/microsocks

Great work @AspirinJunkie! Wish we had something like this sooner I don't like the JSMN-based UDF because it embeds the library as a binary blob in code, so it's great to have a native AutoIt implementation. And implementing objects with maps is a nice touch too! I think it boils down to having the need to manually copy the parsed data from native data structures to AutoIt datatypes, a native AutoIt implementation would entirely side-step the issue as there's no need to convert parsed values

What's that?

Sounds like a bug in the parser/interpreter to me, this is definitely fixable without any syntax change and it should be fixed. Tagging @jpm so that we can get his opinion on the issue as an AutoIt developer

I know that I'm not helping with the script but I'm curious, why not just decrease the brightness of the screen? Edit: I was stupid and didn't read this There might already be programs out there which can do this for you, perhaps they might be a better option.

Hi @SOLVE-SMART, Thanks for the PRs, I replied to all of them. At this point, no. It would just increase the friction between changes. I don't intend to push a lot of updates, and I don't think the users of the UDF (i.e. other developers) would need such neat versioning and change-logs anyway, they can just diff the changes to see what changed, at-least that's what I do I don't have any major plans for this UDF, there might be some small updates here and there but that's it.

Hi @SOLVE-SMART, Yup, that's the quick and dirty script I wrote to test changes on the fly Sure, it's your choice, we can also discuss here. No one in particular, I just put it out for people who need to perform tasks according to a schedule everyday. Personally I'm using this in one of my work projects, I already created several variants of things like this for automation related work projects, so I made this comprehensive solution to cover all my bases in the future and avoid reinventing the wheel everytime I think the README is adequate, but I'm always open for suggestions. No worries, the aspect about accuracy is just a nice to have feature, that wasn't one of my primary goals. It's fine if you don't have an use for this at the moment cron is indeed similar to Windows Task Scheduler, but it also shares all of the drawbacks that I mentioned. Don't push yourself to find some use case, at the end of the day it's just a hobby project Having an example script is just another "nice to have" thing, it's not critical and I'm sure the person who wants to use this in a project can figure it out quite easily with the documentation... and maybe with a little bit of help from here

Hello again, I just fixed some wicked nasty bugs in the UDF which practically makes the original version unusable. I also added some quality of life improvements in the meanwhile My most embarrassing bug is the nasty one, where I wrote incorrect documentation for the schedule format because I wrote from my memory. Turns out my 6-month old implementation was significantly different, who knew So I rewrote the algorithm to fit the documentation --- If anyone has free time and would like to lend me a hand, please write an example script for the UDF. At this point the DIY testing script is broken due to all the changes, and I don't want to update it. So I'll probably remove it soon, so an example script could be of great help. You will get due credit of course. If you are interested just fork my repo and send me a PR, or get in touch here with the script and I'll take a look. --- Hopefully there aren't any more bugs in there...

@SOLVE-SMART You might also be interested in this repository: https://github.com/J2TEAM/awesome-AutoIt It's in no way comprehensive but it looks like a good collection

Thanks Yes, definitely. Windows Task Scheduler just runs your program, it's not integrated into your program itself unlike my UDF, which gives you full control over the schedule, not to mention that your program can still display a GUI and do stuff periodically with AdlibRegister while the main event loop is sleeping. None of that is possible with Windows Task Scheduler. The most important thing though, is the simplicity and independence, no need to bother messing with an external program and risk potential complications. Also it's just not a good look if you are developing a end-user GUI program and it doesn't have it's own schedule thing, instead you have to rely on the user or potentially other programs to not screw up whatever Task Scheduler settings need to be changed.

Scheduler UDF A time-based task scheduler to run arbitrary tasks at set times in a day. Features Milli-second precision with reasonable accuracy Repeating tasks Run tasks even if scheduled time has elapsed (optional) Interruptible Project Home GitHub: https://github.com/TheDcoder/Scheduler.au3 --- Hello everyone, it's been a long time since I've made a new UDF I originally wanted to release this yesterday as my Christmas present to the AutoIt community but I couldn't find the time, so I'm releasing it today as a belated present Work on this was started many months ago but I got caught up with many things and couldn't find the time to clean this up and document everything. I made this UDF because I found myself implementing this in one way or the other in many projects, so I made it into a neat little package to release it to the general public, no need to reinvent the wheel and waste time on this. This implementation is very simple in my opinion and as a bonus I made it interruptible so that the user can exit out of the infinite event-loop. Enjoy and belated Merry Xmas! - TheDcoder

Thanks for sharing the UDF and I apologize in advance for posting in such an old topic, but I believe I found a bug. The OTP generation isn't working properly on my client's computer and I narrowed it down the function to convert base32 to hex, which is the part acting faulty on my client's computer, I haven't dug deeper so I have no idea what's going wrong. However the bug that I want to report here is that the given alternative function seems to be omitting the final hex digit for some reason... Here's my code for testing: For $iKey = 0 To 100 ConsoleWrite('Input: ' & $iKey & @CRLF) ConsoleWrite('_Base32ToHex: ' & _Base32ToHex(String($iKey), True) & @CRLF) ConsoleWrite('_b32toh: ' & '0x' & _b32toh(String($iKey)) & @CRLF) Next And the output: Input: 0 _Base32ToHex: _b32toh: 0x Input: 1 _Base32ToHex: _b32toh: 0x Input: 2 _Base32ToHex: 0xD0 _b32toh: 0xD Input: 3 _Base32ToHex: 0xD8 _b32toh: 0xD Input: 4 _Base32ToHex: 0xE0 _b32toh: 0xE Input: 5 _Base32ToHex: 0xE8 _b32toh: 0xE Input: 6 _Base32ToHex: 0xF0 _b32toh: 0xF Input: 7 _Base32ToHex: 0xF8 _b32toh: 0xF Input: 8 _Base32ToHex: _b32toh: 0x Input: 9 _Base32ToHex: _b32toh: 0x Input: 10 _Base32ToHex: _b32toh: 0x Input: 11 _Base32ToHex: _b32toh: 0x Input: 12 _Base32ToHex: 0xD0 _b32toh: 0xD Input: 13 _Base32ToHex: 0xD8 _b32toh: 0xD Input: 14 _Base32ToHex: 0xE0 _b32toh: 0xE Input: 15 _Base32ToHex: 0xE8 _b32toh: 0xE Input: 16 _Base32ToHex: 0xF0 _b32toh: 0xF Input: 17 _Base32ToHex: 0xF8 _b32toh: 0xF Input: 18 _Base32ToHex: _b32toh: 0x Input: 19 _Base32ToHex: _b32toh: 0x Input: 20 _Base32ToHex: 0xD0 _b32toh: 0xD Input: 21 _Base32ToHex: 0xD0 _b32toh: 0xD Input: 22 _Base32ToHex: 0xD680 _b32toh: 0xD6 Input: 23 _Base32ToHex: 0xD6C0 _b32toh: 0xD6 Input: 24 _Base32ToHex: 0xD700 _b32toh: 0xD7 Input: 25 _Base32ToHex: 0xD740 _b32toh: 0xD7 Input: 26 _Base32ToHex: 0xD780 _b32toh: 0xD7 Input: 27 _Base32ToHex: 0xD7C0 _b32toh: 0xD7 Input: 28 _Base32ToHex: 0xD0 _b32toh: 0xD Input: 29 _Base32ToHex: 0xD0 _b32toh: 0xD Input: 30 _Base32ToHex: 0xD8 _b32toh: 0xD Input: 31 _Base32ToHex: 0xD8 _b32toh: 0xD Input: 32 _Base32ToHex: 0xDE80 _b32toh: 0xDE Input: 33 _Base32ToHex: 0xDEC0 _b32toh: 0xDE Input: 34 _Base32ToHex: 0xDF00 _b32toh: 0xDF Input: 35 _Base32ToHex: 0xDF40 _b32toh: 0xDF Input: 36 _Base32ToHex: 0xDF80 _b32toh: 0xDF Input: 37 _Base32ToHex: 0xDFC0 _b32toh: 0xDF Input: 38 _Base32ToHex: 0xD8 _b32toh: 0xD Input: 39 _Base32ToHex: 0xD8 _b32toh: 0xD Input: 40 _Base32ToHex: 0xE0 _b32toh: 0xE Input: 41 _Base32ToHex: 0xE0 _b32toh: 0xE Input: 42 _Base32ToHex: 0xE680 _b32toh: 0xE6 Input: 43 _Base32ToHex: 0xE6C0 _b32toh: 0xE6 Input: 44 _Base32ToHex: 0xE700 _b32toh: 0xE7 Input: 45 _Base32ToHex: 0xE740 _b32toh: 0xE7 Input: 46 _Base32ToHex: 0xE780 _b32toh: 0xE7 Input: 47 _Base32ToHex: 0xE7C0 _b32toh: 0xE7 Input: 48 _Base32ToHex: 0xE0 _b32toh: 0xE Input: 49 _Base32ToHex: 0xE0 _b32toh: 0xE Input: 50 _Base32ToHex: 0xE8 _b32toh: 0xE Input: 51 _Base32ToHex: 0xE8 _b32toh: 0xE Input: 52 _Base32ToHex: 0xEE80 _b32toh: 0xEE Input: 53 _Base32ToHex: 0xEEC0 _b32toh: 0xEE Input: 54 _Base32ToHex: 0xEF00 _b32toh: 0xEF Input: 55 _Base32ToHex: 0xEF40 _b32toh: 0xEF Input: 56 _Base32ToHex: 0xEF80 _b32toh: 0xEF Input: 57 _Base32ToHex: 0xEFC0 _b32toh: 0xEF Input: 58 _Base32ToHex: 0xE8 _b32toh: 0xE Input: 59 _Base32ToHex: 0xE8 _b32toh: 0xE Input: 60 _Base32ToHex: 0xF0 _b32toh: 0xF Input: 61 _Base32ToHex: 0xF0 _b32toh: 0xF Input: 62 _Base32ToHex: 0xF680 _b32toh: 0xF6 Input: 63 _Base32ToHex: 0xF6C0 _b32toh: 0xF6 Input: 64 _Base32ToHex: 0xF700 _b32toh: 0xF7 Input: 65 _Base32ToHex: 0xF740 _b32toh: 0xF7 Input: 66 _Base32ToHex: 0xF780 _b32toh: 0xF7 Input: 67 _Base32ToHex: 0xF7C0 _b32toh: 0xF7 Input: 68 _Base32ToHex: 0xF0 _b32toh: 0xF Input: 69 _Base32ToHex: 0xF0 _b32toh: 0xF Input: 70 _Base32ToHex: 0xF8 _b32toh: 0xF Input: 71 _Base32ToHex: 0xF8 _b32toh: 0xF Input: 72 _Base32ToHex: 0xFE80 _b32toh: 0xFE Input: 73 _Base32ToHex: 0xFEC0 _b32toh: 0xFE Input: 74 _Base32ToHex: 0xFF00 _b32toh: 0xFF Input: 75 _Base32ToHex: 0xFF40 _b32toh: 0xFF Input: 76 _Base32ToHex: 0xFF80 _b32toh: 0xFF Input: 77 _Base32ToHex: 0xFFC0 _b32toh: 0xFF Input: 78 _Base32ToHex: 0xF8 _b32toh: 0xF Input: 79 _Base32ToHex: 0xF8 _b32toh: 0xF Input: 80 _Base32ToHex: _b32toh: 0x Input: 81 _Base32ToHex: _b32toh: 0x Input: 82 _Base32ToHex: 0xD0 _b32toh: 0xD Input: 83 _Base32ToHex: 0xD8 _b32toh: 0xD Input: 84 _Base32ToHex: 0xE0 _b32toh: 0xE Input: 85 _Base32ToHex: 0xE8 _b32toh: 0xE Input: 86 _Base32ToHex: 0xF0 _b32toh: 0xF Input: 87 _Base32ToHex: 0xF8 _b32toh: 0xF Input: 88 _Base32ToHex: _b32toh: 0x Input: 89 _Base32ToHex: _b32toh: 0x Input: 90 _Base32ToHex: _b32toh: 0x Input: 91 _Base32ToHex: _b32toh: 0x Input: 92 _Base32ToHex: 0xD0 _b32toh: 0xD Input: 93 _Base32ToHex: 0xD8 _b32toh: 0xD Input: 94 _Base32ToHex: 0xE0 _b32toh: 0xE Input: 95 _Base32ToHex: 0xE8 _b32toh: 0xE Input: 96 _Base32ToHex: 0xF0 _b32toh: 0xF Input: 97 _Base32ToHex: 0xF8 _b32toh: 0xF Input: 98 _Base32ToHex: _b32toh: 0x Input: 99 _Base32ToHex: _b32toh: 0x Input: 100 _Base32ToHex: _b32toh: 0x As you can see, _b32toh always omits the final digit in the result when you compare it to _Base32ToHex Anybody know why this is the case? I'm too tired to debug it myself... I'll post here if I find a solution before others.

@TheSaint Good suggestion but I think OP wants to create a self-extracting archive anyway, so it defeats the purpose.