I'm interested in using a non-square (i.e. rectangular) workspace in the cursor task application. In the configuration window, you can make the window rectangular by, for example, setting WindowWidth = 800 pixels and WindowHeight = 600 pixels.
However, when the application launches, the workspace for the cursor task becomes the largest square that will fit inside the window, in this case 600 pixels x 600 pixels. I want the workspace to extend to the whole 800 pixels in the width direction.
Does anyone know of a work around for this?
Non-square cursor task workspace?
-
boulay
- Posts: 382
- Joined: 25 Dec 2011, 21:14
Re: Non-square cursor task workspace?
(Sorry I can't test)
Any luck if you set RenderingQuality to 0?
Any luck if you set RenderingQuality to 0?
-
poiss89
- Posts: 7
- Joined: 28 Jan 2014, 18:45
Re: Non-square cursor task workspace?
No, setting RenderingQuality from 1 to 0 merely changes the task from 3D to 2D, and does changes some other features dealing with collisions and stuff.
I figured out a hack to get it to work. In "FeedbackScene2D.cpp" you need to comment out lines 60 and 61 (mScalingX and mScalingY) and introduce another scaling factor, "float scale = height/width;" which you use to scale the 'x'-components of the GUI::Rect targetRect and GUI::Rect cursorRect lines of code further down the script.
Of course, this is a hack, so I don't know how good of an idea is. I think at the very least I've lost some potential information, since both CursorPosX and CursorPosY will be encoded from 0-100, even though the range for CursorPosY should be greater.
I think I've won this battle, though.
I figured out a hack to get it to work. In "FeedbackScene2D.cpp" you need to comment out lines 60 and 61 (mScalingX and mScalingY) and introduce another scaling factor, "float scale = height/width;" which you use to scale the 'x'-components of the GUI::Rect targetRect and GUI::Rect cursorRect lines of code further down the script.
Of course, this is a hack, so I don't know how good of an idea is. I think at the very least I've lost some potential information, since both CursorPosX and CursorPosY will be encoded from 0-100, even though the range for CursorPosY should be greater.
I think I've won this battle, though.
Who is online
Users browsing this forum: No registered users and 0 guests
