PDA

View Full Version : Aligned in NRD.. Misaligned in NR



NeoMorph
August 6th, 2007, 01:03 PM
OK... friend has setup a 1280x1024 native lcd for me to test my new panel on. In NRD on my 1280x800 laptop the buttons are aligned perfect but when I open it up in NR the buttons are slightly out.

Another thing is in NRD I have to fudge factor shift the mastertemplate background -8 X and -2 Y to get the whole screen visible. It isn't the screen's setup because I shrunk the image and it's still off without the fudge factor.

The screenshots show it more clearly. I wonder if this is the same problem like I have when using NR on the 1280x800 screen except this time there are no alignment problems and the blank bar is on the right hand of the screen.

The screenshot of that can be found here -> http://www.promixis.com/forums/showthread.php?t=17098

The gfx chipset on the laptop is a GeForce FX Go5700 and I'm using DirectX 9.0c along with Nvidia 7.9.7.2 video drivers. I thought I had posted that info previously on the other thread but my post doesn't seem to have appeared (I may have done my usual trick of hiting preview instead of submit lol).

NeoMorph
August 6th, 2007, 04:49 PM
OK... more wierdness. A complete restart of NR shoved the image back so I had to remover the fudge factor... though oh well.

Several edits and saves later and the weird effect resurfaced... fudge back in... thought to reboot... now it's going off screen the other way lol.

Rob H
August 7th, 2007, 06:08 AM
It sort of looks as though it's trying to scale the graphics slightly.

You could try a bit of Lua to check the size that NR thinks the screen is I guess - something like this


w, h = NetRemote.GetWindowSize()

NetRemote.SetVariable('Width', w)
NetRemote.SetVariable('Height', h)


And add labels to the home page for Width and Height.

NeoMorph
August 7th, 2007, 06:44 AM
OK... Tried that and it's shown up some wierd stuff...

When it starts up it thinks the screen is 1286x1026 but if you run the code again it gets it right and shows 1280x1024.

Wonder what is going on here...:confused:

Now I just restarted and its looking at the other screen and still got it wrong... 1276x796.

Looks like we've found the problem of the alignment. It seems it grabs the first guess and sticks by it... even though the later guess is the correct one every time...

Rob H
August 7th, 2007, 07:11 AM
That is seriously weird! But it certainly explains what you've been seeing. Not sure what to suggest except perhaps trying different versions of the screen drivers?

NeoMorph
August 7th, 2007, 09:48 AM
There is a problem there... Geforce Go drivers are'nt downloadable from Nvidia direct... they come from the OEM which in my case is Acer and they haven't updated in a while.

I'll just have to put up with it. The end product will be on a different machine anyway - it's just that I'm stuck in bed atm and having to use the laptop.

Rob H
August 8th, 2007, 02:38 AM
In that case it's probably best to not run it full screen, but you can hide the title bar etc by pressing Ctrl-Space.

NeoMorph
August 8th, 2007, 02:47 AM
In that case it's probably best to not run it full screen, but you can hide the title bar etc by pressing Ctrl-Space.

Oooh... nice one... except it now has a big gap at the top and I can't move the window.

Is there a command to force it to position 0,0?

Rob H
August 8th, 2007, 03:22 AM
Hmm... in theory NetRemote.SetWindowPosition(0, 0) should work, but I just tried it and it didn't. Ah, looks like a bug - it's actually adjusting the wrong window, instead of moving the main NR window, it's moving a child window ie the drawing surface.

You used to be able to drag the window around using the background, but that doesn't seem to work any more - I seem to remember some discussions about that a while back.

The other possibility that I was playing with was using the command line parameters to start it at a given position, but that doesn't help either since you can't use negative values :(

I'm not sure what to suggest at the moment.

NeoMorph
August 9th, 2007, 08:56 AM
Don't worry about it... the results seem pretty random. While I'm testing every time I hit save restarts NR in a random seeming position. Sometimes its off to the left and sometimes it's off to the right.

Could the multiple screens be giving it problems? No other programs are showing this wierd effect so it's got to be something in NR or NRD that's causing it to behave strange. My bet would be on NR as NRD opens up perfectly aligned on either screen. Why would one know the right coordinates and not the other?

Rob H
August 9th, 2007, 10:00 AM
NR has no problem with multiple screens here. I suspect that this is something to do with the bizarre size issue that it's reporting, although I'm surprised that this doesn't seem to affect any other programs.

NeoMorph
August 9th, 2007, 12:19 PM
It doesn't even affect NRD... :confused: It's got to be NR at fault here becuase I've run this laptop for a fair while now and this is the only program that has ever got out of alignment. NRD has never shown this problem... not even once. If it was something to do with my laptops drivers surely other programs should show it. NR shows it all the time and not consistently either.

There must be something that NR does that NRD doesn't. When NR goes into full screen mode does it do something unique?

I have to admit these are the worst bugs a programmer can come across... intermittent and inconsistent bugs used to drive me nuts back when I was working as a programmer. Is there anything I could do to help here? Unfortunatly I only ever used high level languages so C++ type languages arent my forte but I've hunted down my share of bugs over the years (a lot of them due to the fact that I knew a bundle of languages and kept using another languages syntax instead... I knew the code was right yet the compiler was arguing it was wrong. I was right... just not for the language I was using.)

Am I the only one who's ever reported this problem?

Rob H
August 9th, 2007, 12:49 PM
I'm not sure what NR does when it goes full screen I'm afraid.

I don't recall anyone else reporting this issue