How to get the total number of pixels of a window? | Page 2 | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

MT4 - Terminal window in separate window? 44 replies

Indi that plots the data-window in the main chart-window? 0 replies

Best and total number of currency pairs? 21 replies

total value for end of bar total 0 replies

Stoch window above price window/ separate price indicator? 2 replies

Attachments: How to get the total number of pixels of a window?
Exit Attachments

How to get the total number of pixels of a window?

  • #21
  • Sep 5, 2009 7:05am Sep 5, 2009 7:05am
Quoting xecret
Can we follow Irtron's idea without place a yellow line, just to recognize the gap? The thing is how we can get the foreground and background color of the window.
There is no need to recognise the colours. It would be enough to detect the colour change on the boundary.

Here is the script. Inputs might depend on the screen resolution. Default parameters work on my 96dpi display.
Attached File(s)
File Type: mq4 SubwindowHeight.mq4   < 1 KB | 553 downloads
  • #22
  • Sep 5, 2009 9:35am Sep 5, 2009 9:35am
Quoting Irtron
There is no need to recognise the colours. It would be enough to detect the colour change on the boundary.

Here is the script. Inputs might depend on the screen resolution. Default parameters work on my 96dpi display.
Very smart and concise coding. Much appreciated.
  • #23
  • Sep 5, 2009 1:51pm Sep 5, 2009 1:51pm
Thanks Irtron. I learned a lot about device context and pixels.

Xecret: Do you use wingdings in those output buffers to get the squares - if so how do you change them from one bar to the next?

Thanks, Ken
  • #24
  • Sep 5, 2009 4:37pm Sep 5, 2009 4:37pm
Quoting Kenz987
Xecret: Do you use wingdings in those output buffers to get the squares - if so how do you change them from one bar to the next?

Thanks, Ken
Yes, wingdings are applied to buffers. Multiple buffers are used, each buffer corresponds to a wingding. If you want to output a wingding, just give that buffer a value and give other buffers EMPTY_VALUE's.
  • #25
  • Sep 5, 2009 5:52pm Sep 5, 2009 5:52pm
Hi Irtron, the script stopped working from late last night (here GMT+8). It seemed to quit directly without execution, there's even no comfirmation of the input parameters (X and Y). I tried restarting MT4 and Windows, it kept the same. Strange, it worked well as I just downloaded it and put it into the script folder.
Attached Image
  • #26
  • Sep 6, 2009 8:51am Sep 6, 2009 8:51am
Quoting xecret
Hi Irtron, the script stopped working from late last night (here GMT+8). It seemed to quit directly without execution, there's even no comfirmation of the input parameters (X and Y). I tried restarting MT4 and Windows, it kept the same. Strange, it worked well as I just downloaded it and put it into the script folder.
What does the log in Experts tab show?
  • #27
  • Sep 6, 2009 6:37pm Sep 6, 2009 6:37pm
Quoting Irtron
What does the log in Experts tab show?
Ah, it's showing the right things. I did not notice I was looking in a wrong tab. Sorry.
  • #28
  • Sep 6, 2009 6:50pm Sep 6, 2009 6:50pm
Irtron and Kenz987, with your help I managed to make the indicator as desired. Lots of thanks to you two.
Attached Image(s) (click to enlarge)
Click to Enlarge Name: 2009-09-07_074138.png Size: 48 KB
Click to Enlarge Name: 2009-09-07_074206.png Size: 23 KB
  • #29
  • Sep 6, 2009 7:26pm Sep 6, 2009 7:26pm
Anyway, there are still two problems not solved:
1. How to detect the window index of the indicator subwindow.
The text labels are created by ObjectCreate(), so the window index is needed. I use WindowOnDropped() to get the window index. But there is problem if you delete a subwindow above the subwindow where the indicator is located, because the actual window index is changed but the value of WindowOnDropped() remains the old value. So, is there a better way to get the window index in which the indicator is located?
2. How to detect the action of minimizing or maximizing the window.
Only when there is such an action do we need an adjustment of the display offset. At other times there is no need to count the subwindow pixels wasting system resources. I use WindowBarsPerChart() to detect this. While I click the zoom in or zoom out button, WindowBarsPerChart() also changes its value leading to unnecessary calculations. Is there a better way to detect the minimization or maximization of a window?
Thanks.
  • #30
  • Sep 6, 2009 9:44pm Sep 6, 2009 9:44pm
1: Irtron's script gives the index. Also, there is a Windows function in MQL to give it (WindowFind).
2:http://msdn.microsoft.com/en-us/libr...31(VS.85).aspx
IsZoomed Function
The IsZoomed function determines whether a window is maximized.
Syntax
BOOL IsZoomed(
HWND hWnd
);
Parameters
hWnd
[in] Handle to the window to test.
Return Value
If the window is zoomed, the return value is nonzero.
If the window is not zoomed, the return value is zero
//
http://msdn.microsoft.com/en-us/libr...27(VS.85).aspx
IsIconic Function
The IsIconic function determines whether the specified window is minimized (iconic).
Syntax
BOOL IsIconic( HWND hWnd
);
Parameters
hWnd
[in] Handle to the window to test.
Return Value
If the window is iconic, the return value is nonzero.
If the window is not iconic, the return value is zero.
//
I don't know what you get if the window is neither...
//
I am attaching a VB reference of Window's API functions. Using this and the MSDN website I can usually find what I need. Maybe it will be a help to you.
Attached File(s)
File Type: txt WIN32API.TXT   683 KB | 2,715 downloads
  • #31
  • Sep 7, 2009 12:46am Sep 7, 2009 12:46am
Thanks Ken for your time answering the quetions. I will go studying those documents.
  • #32
  • Edited 2:37pm Feb 21, 2011 2:06pm | Edited 2:37pm
Hi, everyone, I'm having the same issue Xecret posted initially on this thread, but for some reason I can't get his code to work. I need a function to retrive the current security's window height in pixels, to be used in an Indicator I'm building. I'm on MT4 using WinXP. Here goes the code:



#property indicator_chart_window
#import "user32.dll"
int GetWindowRect(int hWnd, int rect[4]);
#import
int init() {return(0);}
int deinit() {Comment(""); return(0);}
int start()
{
int r[4];
GetWindowRect(WindowHandle(Symbol(), Period()), r);
Comment(r[0]," ",r[1]," ",r[2]," ",r[3]);
return(0);
}



Unfortunately, it simply doesn't work. No values at all are displayed in the comments section. This is my first time using Windows API, so I'm not really sure I'm doing everything right. Could anybody help, please?
  • #33
  • Feb 22, 2011 7:14pm Feb 22, 2011 7:14pm
Well, it seems I got some progress here. The "Allow DLL Imports" option was unchecked. Now the code displays 4 different values in the comments section, but MT4 crashes when I delete it from the Indicators list.

Any idea why this happens? None of the 4 numbers actually behave as if they were the window's pixel height. Any clues on that?
  • #34
  • Feb 25, 2011 6:41pm Feb 25, 2011 6:41pm
Hi RogerVF,


#property indicator_chart_window

#import "user32.dll"
int GetWindowDC(int dc);
int ReleaseDC(int h, int dc);
bool GetWindowRect(int h, int& pos[4]);
#import
//


int init() {return(0);}
int deinit() {Comment(""); return(0);}
int start()
{
//
int hWnd = WindowHandle(Symbol(), Period());
int hDC = GetWindowDC(hWnd);
int r[4];
GetWindowRect(hWnd, r);

Comment("Left = ", r[0], ", Top = ",r[1],", Right = ",r[2],", Bottom = ",r[3]);


return(0);
}
  • #35
  • Feb 26, 2011 4:08am Feb 26, 2011 4:08am
Hey, Kevin, thank you very much for your answer, I had already figured it out. the crashes I was having were also solved too. At first I thought user32.dll should be copied to the indicator's folder, but this was actually creating some kind of conflict and crashing down the system. Removing the unneeded copies stabilized it once again. But thanks a lot for your help.
  • #36
  • Feb 28, 2011 5:39am Feb 28, 2011 5:39am
Alright, I've been struggling not to come back and bother you guys, but there's still some kind of problem with this code. It works perfectly, but when I change profiles and come back I get a "divide by zero" error in the "specialists" window. I've managed to isolate the part of the code that's giving me the error and guess what... (Please take into consideration that prior codes have been ommited)

int r[4];
GetWindowRect(WindowHandle(Symbol(), Period()), r);
int Window_Height_Coeficient = (r[3]-r[1]);
Spacing = 10.5*(WindowPriceMax()-WindowPriceMin())/Window_Height_Coeficient;

The major problem is that it's intermitent, that is, it doesn't happen all the time. If I don't have many charts open, most of the time the indicator will reload flawlessly. It seems there's some kind of delay getting de command "GetWindowRect(WindowHandle(Symbol(), Period()), r);" executed, and for some reason the rest of the code gets executed before it gathers correct values for r[3] and r[1].

Has anybody experienced this issue? Any possible workarounds? Thank you very much for your time and patience.
  • #37
  • Feb 28, 2011 7:43am Feb 28, 2011 7:43am
Roger

I bet your running this code in an indicator and not a EA or script. Indicators work differently then EAs and scripts, they dont wate for a return from a dll call. That is why MT tells you, you can't use messageBox() function in an indicator because it will not wate for the user's response to a button click. That is why some other functions (like sleep()) don't work.

work arround that.

Keit

Quoting RogerVF

for some reason the rest of the code gets executed before it gathers correct values for r[3] and r[1].

Has anybody experienced this issue? Any possible workarounds? Thank you very much for your time and patience.
Trader Keit ... Methods Of A Dirt Road Mad Man....
  • #38
  • Feb 28, 2011 4:14pm Feb 28, 2011 4:14pm
Hey, Keit, thanks a lot for your answer, that's correct, it's an Indicator im coding. I've tried a WHILE (division=0) loop, but the code locks up MT.

It seems what I need is a code that forces the indicator to be recalculated after everything has been executed. Any clues on that? Not really sure I want to switch over to an EA, since there aren't any strategies associated with it.
  • #39
  • Edited 9:15am Mar 1, 2011 9:03am | Edited 9:15am
dont know how your code works but you can try to short cycle the code till you get the a nor zero return. at the begining of the start function... You should put the code for retreving the window size in a routine that is called on each tick as it should be able to see if the window was changed while active.


x = GetWindowSize();
if( x < 1 ) return;

if put at the begining of the start function it should stop the indicator from running till you get the window size. you will need to add in some routine to remove / move your objects if the window size was changed.

Let me know how you worked it out, I have done some thing similar but it uses the window scale to place objects and if the window size is changed the placement of the objects get a little out of aliment, I dont need to change the window size, so that works for me. but may think of changing that.


Keit

edit[Roger is not a name I see very offen.]

Quoting RogerVF
Hey, Keit, thanks a lot for your answer, that's correct, it's an Indicator im coding. I've tried a WHILE (division=0) loop, but the code locks up MT.

It seems what I need is a code that forces the indicator to be recalculated after everything has been executed. Any clues on that? Not really sure I want to switch over to an EA, since there aren't any strategies associated with it.
Trader Keit ... Methods Of A Dirt Road Mad Man....
  • #40
  • Mar 3, 2011 7:50am Mar 3, 2011 7:50am
Hi, Keit, that was my first attempt, but as I said, it makes MT lock up. So I have to restart the program and remove the command line from the indicator, before I get it to work again. As you said, the command line was placed inside the start() function, to make sure it gets re-checked every new tick.

(I'm assuming GetWindowSize() is just a way you found to quote my code)

I still think the best way to make this work would be to write a line at the end of the start() function to check if the value returned was =0 and, if so, force the indicator to be recalculated. I tried WindowRedraw(), but I couldn't really see anything happening.

But, Keit, thank you very much for answering me, man, it's great not to think alone My name is french, by the way, you don't pronounce it like you would in english
0 traders viewing now