Definition of Variables Window – Sizing (Want)
- This topic has 8 replies, 3 voices, and was last updated 4 months ago by
.
-
You will obtain this in the Want/Bugs list, right ?
I am happy to do above, but thought I’d make it a general discipline to leave for a day or two to give a chance for others to say … you’ve got it wrong GraHal, you need to do this or that then you won’t have that problem??
Anyway as you are working the Wants and Bugs through PRT, so might you be best to add all Wants & Bugs to the List then you will recognise your own wording / description etc.
Some folks also may be hesitant to commit themselves to adding to the List?
Aren’t we breaking our own rules here by discussing List procedures on a Wants Topic?? 🙂
1 user thanked author for this post.
For hopefully additional clarity for PRT :
- Although GraHal does not mention it, the same counts for the width of this form; once you have one variable with a so much longer name that the form does not anticipate it, a horizontal scrollbar appears and only with scrolling or dragging wider, you can reach the “step size” for all variables. Thus, drag wider each time the variables window opens (because it was closed for whatever reason you like).
- What GraHal rightfully points out is that the variables window will be large up to huge, covering other more important stuff on the screen, for the moment (like charts).
PRT, please, in the devleopment (coding) environment, all works differently than in the normal platform environment. So what I explicitly like to add (but in the end it is the very same problem) is that whatever is given the focus (clicked) the whole coding environment with all its forms, comes on top of everything else you rather liked to see. For example, it I click that variables window, I do not want the editor to overlay charts etc. Or, if I click the editor, I don’t want the variables window to overlay my other stuff (this is what GraHal talks about, though from different angles).
- Allow for every form to go to the taskbar individually, on command (“minus” button in title bar)
- Please notice and recognize that ALL in the normal platform is just 100% perfect regarding this. This includes clicking a form that causing only that form to overlay some other part. But click it again, and the whole platform overlays everything. I could not have designed this better. It is plainly superb. … Now apply all these (thus well known !) features to the coding environment, and so many people will be so happy with so much smaller monitors. 🙂
One more example I now think of in the again same realm : The right hand part of the Editor form is mostly not accessed. But it can’t be dragged smaller. It is relatively “huge” for something you mostly don’t need at all. And … it will overlay something else important of the coding environment itself. It is all about the same things …
1 user thanked author for this post.
Hi… @GraHal, been trying to understand the problem.
Is this it, when you have a lot of variables in the DoV, the Dov size adapts to cater for all the variables.
When its opens, the lower portion, falls off bottom of screen, the only way to remedy the situation, is to drag the window up, whereby you may see all the variables, but no access to bottom of window. Or drag top of window down, which show the scroll bar, then move window up to see bottom of window, then use scroll for variables.
What I noticed while looking at this was, regardless where my chart is on 1 screen, when I open the Modify ProBacktest window, the editor gets centred around the middle of the screen, if saved small enough. If I then open the DoV, the top of the DoV window is aligned with the center line of screen. This leaves only half the monitor height to show the DoV window. Not going to happen with a lot of variables.
However, after opening the Dov, you close it, and then re-open it again, it renders from top of screen. This helps depending on how many variables listed because fullhight of screen used.
Portrait or Multiple monitors help even more, with one above other. With chart in top monitor, Dov has x1.5 monitor height or x2, or back to drag n scroll.
Altering the general font size as an affect, but down side is it changes every thing else.
Failing that, how long is a piece of string!
1 user thanked author for this post.
Yes the problem is as you describe above and all would be solved if the scrollbar auto-showed when variables are out of view.
It would also be a massive improvement, if there could be a font size adjuster widget on the DoV window / Form (same as in the code editor) then we could adjust DoV font size independent of font size everywhere else on the Platform.
1 user thanked author for this post.
It appears that non of the PRC windows can sense the bottom of the screen.
Its a pity that using the ‘SET’ feature doesn’t save the layout position/size, just the options under ‘Value’ header.
Your right, if the number of displayed variables was limited , the scroll bar would kick in, also, there space to optimise the row size.
1 user thanked author for this post.
Find exclusive trading pro-tools on 
