PlanetZ forums - scopeusers.com

I'm in the (un?)fortunate situation to mess with M$'s VisualStudio SDK recently...
my half-educated guess is that the source of the problem is event handling
in some cases it doesn't work as documented, which may disable certain range checks etc
I didn't cross check it on Win7 yet
(currently using VS2010 express, but will do when the full version arrives)
basically the .Net stuff runs ok, but I had to implement workarounds for a couple of items

for the curious ones who are code savy, here's the most minimal example that fails on my system:
(I'm not the author)
http://www.codeproject.com/Articles/464 ... WPF-events
(middle of the page)
it's just a standard button/mouse/keyboard event handler with a single line of code
in my case it eats up the event, though the functions are supposed to pass it
with an extra line of code to manually raise the event on exit it works as should be...

as Win XP isn't supported anywhere officially, a switch to Win7 and above may apply...

cheers, Tom

?

short version for twigs:
there's no cure under XP
maybe someone feels responsible (or ambitious) and digs deeper...
Scope 5 is built with .NET

cheers, Tom

There is no cure for what?

I'd guess astro is looking into causes for VRC device crashing on some people's systems but not others. And it's looking like it doesn't work on XP, but might on Win7. So if you need VRC, and use XP....it's not gonna work.

yes, at least some folks can't use the VRC-128 or VRC-S in Scope 5 when running XP
up to Scope 4.5 the device is ok, as it is in Win7 and Scope 5

cheers, Tom

Seems ok here on Windows 7 Tom. Only thing is that there are exception errors when saving Vdat in the project, with a tape file inserted.
As long as I can record, that's the main thing.

Are you getting into programming now?

I've been into programming as long as I can think... but avoiding the mighty M$ Spaghetti Monster
to make a long story short I find a lot of my own concepts reflected in .NET 4 (in particular WPF)
that my read as a bold statement, but I have never ever cared about that technology until a couple of months ago
I knew it existed, that it was bulky, bloated code... imho better to be avoided

but since version 4 it seems to be a cool interface toolkit
... which can do some graphic tricks that I have neither the skills nor time to implement myself
at least recent evaluations looked promising for porting most of my former database logic to this surface
(neat separation of processing and user interaction parts included)
it's quite efficient and I obey money... network is king today and Apple isn't much different anyway ...

but I've spent at least a day on 3 simple problems that just didn't work out (on each of them...)
the afforementioned example was one
(crucial - for the 'select state' check of an item failed - data was loaded beyond bounds... the abbreviation of crash)
in 3 days I found at least 2 of that kind - and the VRC stalls look quite similiar
(but VRC is at least 10 times as complex as my test stuff, so I wouldn't blame anyone)

different .NET versions are infamous for incompatibilities and you never know what's installed on the client machine
software companies deliver with .NET Redistributebles from various release dates, so things mix up rather quickly

cheers, Tom

Ah! That's great Tom, so you're our go to guy now if we need to know what's wrong
with something.