@GoldenClarinet

QueueClear time-sync noteHackatime is currently filtered to project queueclear and shows 3h 25m total. The Stardance project page still displays 2 Total hours. I am attaching screenshots of both pages so the project-time link can be checked.The current public demo and source are here:https://aaravkatiyar55-gif.github.io/queueclear/https://github.com/aaravkatiyar55-gif/queueclearThis note documents the visible time mismatch only. It does not claim that previous review feedback has already been resolved.

DevLog #22 : I started working on redefining the structure of the code to strengthen robustness and clarify the architecture. I asked Codex to make me a check list of all the modifications to operate. Thanks for reading 😁 PS : Special thanks to @Aaravkatiyar for liking and commenting DevLog #21 and following ! (You are the GOAT!)

I messed something up and m editor wasnt responding I couldt click anything. I was trying to fix it almost 5 hours. What I fixed? - vulkan and SDL were recreating while turning MSAA on and GPU was loosing context

DevLog #21 : New functionality! You can now download data from a specific date range. I added this feature to prevent long downloads ( ~ 5 minutes for the whole history with a time frame of 15m and 15 times longer for a timeframe of 1m ). I am now working on computing series with incompatible indicators with general_application. Thanks for reading ✌️! PS : Special thanks to @alyaanmughal for liking DevLog #18, @Aaravkatiyar for liking DevLog #20 and @Sreeni for following me !

DevLog #21 : New functionality! You can now download data from a specific date range. I added this feature to prevent long downloads ( ~ 5 minutes for the whole history with a time frame of 15m and 15 times longer for a timeframe of 1m ). I am now working on computing series with incompatible indicators with general_application. Thanks for reading ✌️! PS : Special thanks to @alyaanmughal for liking DevLog #18, @Aaravkatiyar for liking DevLog #20 and @Sreeni for following me !

DevLog #20 : New design ! I redesign the main menu by moving 🧩 Manage Custom Indicators and Events, 🗑️ Delete a Column and 📁 Open or Create a Database in the ⚙️ Settings. Small change but it improves the user experience and the understanding of the main menu. Thanks for reading 😄!

DevLog #17 : New functionality ! You can now create a file containing your own custom indicators and events. I also created a function called general_event_application which simplifies the creation of new events. Thanks for reading 😄 PS : Special thanks to @bali0531 for liking DevLog #16 !

DevLog #18 : New indicator and new event ! The filter_savgol applies a Savitzky-Golay filter (filter that works on polynomial regression) and peak_detection. This led me to add a system that allows the use of indicators and events functions that do not comply with the functions general_application and general_event_application (functions that simplify the création of custom indicators and events). The next steps are the packaging and the writing of the README. Thanks for reading 🙌!

DevLog #19 : New functionality ! You can now compute series of the same indicator but with different windows (EMA 20; EMA 30; EMA 40 …). It only work for the functions compatible with general_application for now but I am working to extend this feature to the custom indicator functions. Thanks for reading 🙌!

DevLog #19 : New functionality ! You can now compute series of the same indicator but with different windows (EMA 20; EMA 30; EMA 40 …). It only work for the functions compatible with general_application for now but I am working to extend this feature to the custom indicator functions. Thanks for reading 🙌!

DevLog #18 : New indicator and new event ! The filter_savgol applies a Savitzky-Golay filter (filter that works on polynomial regression) and peak_detection. This led me to add a system that allows the use of indicators and events functions that do not comply with the functions general_application and general_event_application (functions that simplify the création of custom indicators and events). The next steps are the packaging and the writing of the README. Thanks for reading 🙌!

DevLog #17 : New functionality ! You can now create a file containing your own custom indicators and events. I also created a function called general_event_application which simplifies the creation of new events. Thanks for reading 😄 PS : Special thanks to @bali0531 for liking DevLog #16 !

DevLog #16 : New functionality ! You can now calculate statistics of an event to show up in function of two parameters. In The example, the event is a cross between the close and the SMA 100 in function of the volume and the the volume of the quote. I am coming to the end of the project, the next steps are to allowing the user create its own indicators and events. Thanks for reading 🙌 ! PS : Special thanks to @MathBty and @dhruvalya for liking DevLog #15 !

DevLog #15 : New functionality ! You can now search a file already created to make returning to work easier on an existing file. Thank for reading 😄 ! PS : Special thanks to @Gerafftes for liking DevLog #14 !

DevLog #14 : New fonctionality ! You can now plot a Status with indicators directly with the interface. In the example, Close, SMA 100, SMA 50 and Cross(SMA 100, SMA 50) are plotted on the same graph. The next step is to calculate Stats and plot it too. Thanks for reading 🫡

DevLog #13 : New functionalities ! You can now plot any indicators already calculated directly with the interface. The next step is to plot status (like “cross”) and stats. I also added 4 functional indicators in the indicator dict of the interface (ATR, VWMA, Amplitude and Relative). The Indicator Dict is able to contain recommended parameters for each indicator and they are printed when entering parameters to calculate indicators. Thanks for reading 🫡. PS : Special thanks to @Jinan (again!), @CoolDuck and @MathBty for liking DevLog #12, @PAPER_01 for liking my first DevLog. Thanks again to @jinan for the amazing comment about DevLog #12 and @yeshwingadde for following !

DevLog #12 : Bugs fixed ! I added in the code verifications for each user entry to prevent incorrect type of entries and reduce program crash. I also added the option Continue after an action. Hope you like the new logo. Thanks for reading 🙌! PS: Special thanks to @shi , @Jinan and @f for liking DevLog #11. Thank again to @f for the nice comment about DevLog #11!

DevLog #11 : New functionality ! You can now calculate indicators directly with the interface and delete it. I also added an History to remember the actions that have been done. Hope you like the new design with emojis. I am still taking ideas from you. Thanks for reading 😁

DevLog #10 : New functionality ! I have started to build a terminal-based user interface to make Market Lab much easier to use. Here is a preview of the first functionality : Download Data to download every candles of the selected symbol and interval. I am also continuing to work on the heat map feature (look at DevLog #9). If you have advice about the design or whatever of the interface, I will be very happy to listen to it. Thanks for reading 🫶 !

DevLog #10 : New functionality ! I have started to build a terminal-based user interface to make Market Lab much easier to use. Here is a preview of the first functionality : Download Data to download every candles of the selected symbol and interval. I am also continuing to work on the heat map feature (look at DevLog #9). If you have advice about the design or whatever of the interface, I will be very happy to listen to it. Thanks for reading 🫶 !