Thebattlefront

Or actually, do you happen to have the version of medved trader from just before July 30, 2022? I just wanna check that version of MT to see if my old scans will work on that one as compared to the new MT to see if there is any difference there.

Yea the paintbar is huge, apologies for that. Most of it is just data storing for the different candlestick data (at the end of the paintbar) so it's larger than it actually is i think. Maybe like 3000-4000 lines of actual coding but yeah It's still kinda confusing. Maybe I can make an example paintbar that is shorter that you can look at that has the same issue with setscanresult. As for the calculation of the %/b and the total winrate of the paintbar over the period, yeah it takes the average sum over the total range. I'm not too familiar with StateFIFOQueue and how it works, although I do remember you telling me to use that to get the highest high and lowest low for the yearly range a few months back and I just copy pasted what you gave me and it seemed to work just fine so I'm continuing to use that. I think I have another paintbar that has issues with the setscanresult and its much, much shorter. Just a few hundred lines of code. Maybe I can send that one instead for you to see?

ok

Ok I sent it. The scan is called "Better MomCyc" that I'm referring to. Not the "Better MomCyc vCurr" one. That is like a copy of the other one but I think i pasted one of the older codes onto that scan so don't use that one at the moment.

That previous code i posted was saved on July 30, 2022. So i think the change must have been in between that time and today (October 16, 2022). Although I think it's more maybe like a month or two ago. So possible around August or September. Again maybe my code is no longer valid with the current way things are done in advanced paintbar

I keep all my older scans in a folder just in case i need to revert back to a previous version. But as i said, it would appear none of those older codes work anymore. Here's an example of a previous code I made that I marked as being "greatly improved winrate" but it now shows as having a bunch of zeros in the left most column - meaning there's no profit to be had on any trade i make on those stocks when its still the same set of stocks I'm running the scans on - something that shouldnt be occurring.

Yea sorry for the wonky part, I wasn't very descriptive in my post because I just wanted to see if anyone else noticed anything out of the ordinary. Here's a screenshot of the results I'm getting currently to explain what I mean: These values for %/b used to be above 1 for every result. But after a certain patch I started getting a bunch of zeroes ( as you can see in the screenshot). In order to double-check this, I ran an older code that I know had previously worked and gave positive values for the %/b column, but that code also produces a bunch of zeroes and strange values for the number of trades per stock (the #T column). So this is why I brought it up, it would appear something maybe changed in the advance paintbar scanner in some way but I'm not exactly sure what it could have been. I have no idea if its actually related to the currentstate variables. Or maybe it somehow is my code going wrong but, it sort of seems unlikely since the older codes that did work for me no longer produce the results I was expecting either? If you want i can send you my code and you can take a look and i can show you the parts where the setscanresult calculates these values.

Hello, Has anyone else noticed glitched results when they run their scan using advanced paintbar? It would seem even older versions of the code I run are producing very wonky results as of a few weeks ago. I didn't post about it back then because I wasn't sure if it would be fixed in the next patch but it would appear the problem is persisting. I think it's related to the currentstate variables or something along those lines. Just wanted to know if anyone else has been having this problem recently.

Hello, I was wondering if it were possible to use a system-defined indexed variable as an argument to a function. For example, this function: //----------------------------------------- lowest function private double Lowest(double Value, int candle_Start, int candle_End) { double a = Min(candle_Start, candle_End, Value); return a; } Returns an error because the variable "Value" is not an indexed variable. In this context, I'd like the variable "Value" to be one of either Close, Low, or High (something that is inherently an indexed variable) but I'm not sure how to declare the variable type in the function's argument. I know it's not double, but I don't know what exactly the variable type it is. So an example of how I want this function to work is: Lowest(Close, 0, 4) Will return the lowest value of the close from day 0 to day 4. Edit: I understand I can separate the function definitions to be LowestClose(candle_start, candle_End) and LowestHigh(), LowestLow() etc but I'd like for the function to be more dynamic if I could make it that way because It allows for less repetition.

That's really weird. All I did was comment out the Piercing function (Orange P) and then saved the paintbar and it was fixed. But, I then proceeded to uncomment the piercing function and... it still worked. I suspect this error has something to do with the weird candlestick data at the beginning of the historical data. Once I cleared the data, and changed the backfill source, and then saved the program over again the error disappeared. I didn't change anything with the code. So at least I know now.

Hi Jerry and Mike, So, I am having an issue where the paintbar i use is kind of having some serious issues printing on only a very small fraction of stocks that I have. Normally, it looks like this: That is the image for a stock called "ROKU". It works very well for the majority of stocks on my watchlists, however, when I run this paintbar on the stock MTCH the result is this: \ Note that this screenshot occurs at the beginning of the data for "MTCH". These are the only markings that get printed on the chart - there is no later data for more recent candlesticks. On another note, if I clear the data for the historical chart, and choose a different source to backfill "MTCH" with, the end result of the paintbar changes dramatically. Here's an example using Webull as a backfill source instead for the same stock (MTCH): Another thing I notice as im pasting these chart in, is that the final result of the paintbar (Orange P --> Green Circle) seems to be consistent no matter which source I use to backfill. So probably something wrong with the paintbar itself. I'll look into that I guess.

Hello, I had a quick question. I was wondering if there was a way to disable the ability for data coming in from the after-market hours to affect the current last candlestick's data. I just want the last candlestick on the daily chart to remain unchanged after the close at 1:00 pm EST instead of it's close fluctuating based on prices after hours. The reason is I have a paintbar that trades based on the candle closes on the historical chart and so usually I decide whether I want to buy or sell a stock after the market has closed and the market has made its official "closing price" for the day (and therefore, whatever candlestick pattern has formed will remain stagnant). However, incoming data from after market hours changes the shape of the last candlestick and that affects the paintbar's result and I don't want it to do that.

Thank you Mike, works like a charm now.

Mike, I have a suspicion that those two values don't update as the paintbar goes backward. I'm having some weird errors in my program that get solved when I replace SymbolData.High52 and Symbol.DataLow52 with Max(0, 260, High) and Min(0, 260, Low). Any thoughts? So to explain what I mean, let's say my paintbar is examining a bar 260 bars ago. I want my program to calculate the 52 week high and 52 week low from that point, and then make calculations based on those values. So, for bar[260] the yearly range would be between the bars bar[261] and bar[521]. Not from bar[0] to bar[260] which would be the current yearly range. EDIT to clarify: I don't ACTUALLY want my program to calculate that as it makes a lot of lag from the paintbar having to do a very heavy amount of calculations. What i was hoping for was that the historical yearly high and yearly low was cataloged and I could access it directly without having my computer struggle from having to calculate it for each individual bar.

Thank you!

Hello, I was wondering if there was a variable inside the paintbar that already has in it the value for the 52 week high and 52 week low for a particular security. I know it is simple to calculate, i.e.: YearlyHigh = Max(0, 261, High); YearlyLow = Max(0, 261, Low); However, when this scan is done for many thousands of candlesticks, it makes the program run quite a bit slower and cause quite a bit of lag as it needs to calculate these two values for each bar (calculate 261 candles behind it, that is). So I was wondering if these two values could be added to the available variables list for paintbars.

Yessir Jerry I shall email it to you.

Wow I really messed up the formatting. How do i delete this lol I will rewrite it here again instead: Is it possible to declare and use a CurrentState variable as an array? Hello, I have been having a bit of trouble getting arrays to work with the CurrentState variables. For example: This line of code: double[] abc_Vector = {1, 2, 3, 4}; double abc = abc_Vector[1]; Works without any issues. The debugging log and the chart shows the correct PBShapes and Colors for those shapes, so I know the code is working. However, if I were to declare a new CurrentState variable in this way: private void PaintbarInitialize() { CurrentState.m_dTest = new double[4] {0, 0, 0, 0}; } private struct PaintbarState { public double[] m_dTest; } And then subsequently write the line of code somewhere in any another function: double abc = CurrentState.m_dTest[1]; The debugging log below the code lines does not return any immediate error in the coding. However, a red "X" displays on the Chart next to the PaintBar's name in the top left and the PBShapes and Colors don't show on the chart as well. So I know something running inside the program is having a problem. And the only thing that I've changed from the working program, to the one that is not working, is the declaration of the CurrentState array variable. So I was wondering if I have declared or defined something incorrectly, or if possibly the CurrentState function doesn't support array type variables. EDIT: Apparently I can't copy paste code from the Paintbar directly into a post. It turns up empty. EDIT: I typed it in manually instead

Hello, I have been having a bit of trouble getting arrays to work with the CurrentState variables. For example: This line of code:

Thanks again Jerry, you're the best

I cannot send the log, it will not let me do anything as the layout is saved so it loads the charts, portfolios, other windows everytime it starts, causing the freeze.

Hello, My Medved Trader has completely frozen and I am unable to use it. This occurred after installing the latest patch (today, Aug 5) and opening an intraday chart and going back to at least 90 days of intraday data on the 5 minute timeframe. When Medved is open, I am unable to click on anything, I only see the loading circle of the mouse and cannot close or bring up any other window on medved. I must force end the program using task manager, it is the only way to do anything. Attached screenshot is what I can see when I open medved. Unable to access any other windows as they all are listed as "not responding" according to Task manager.

When you extend the parallel of the base line the tool gets "stuck" and will only extend a fixed distance away from the initial line. Notice the white dot. The parallel line should pass through that point.

Hello, I have been trading using Medved Trader to trade but have been unable to execute a "buy put" order on a stock named ARWR. I get a "Hyperlink - URL missing" error every time. Yet I can place call orders for the same stock without any issue.

Woops forgot the link to the thread, but I included the symbols with it and a description of the error.