Main > Software Forum
Johnny 5 only support 10 joy buttons? (fixed), but file/open not work?
Howard_Casto:
No you said you changed your preferred langauge to english, which isn't the same as what I suggested.
However if you have tried my suggestions without english as the default langauge and it works, with respect, then it isn't a bug and is working just at it should.
Just as a Japanese video game won't work on a US pc without japanese langauge sets and sometimes japanese code conversions, you are going to have trouble unless your US plugins are installed.
I know you are unfamiliar with vb, but what I've been trying to tell you is I have absolutely no control over how vb prints out really long numbers. It isn't a ini file thing either.... if I were to just use a ascii print it would give the same number. I can convert the value into another format, but then it gets rounded and thus the placment is far less accurate.
Now I can manually go back after the fact and replace the "," with a "." but you said in your reply that this didn't have any effect until you turned on english as the default language, which understandably you shouldn't have to do. Since I can't alter it manually then there really isn't any other way to fix it. Now if you happen to run across a solution I'll be glad to add it, bt my searches haven't turned up anything. This is exactly what those code conversion packs you can download for xp are for. They do the heavy lifting so programmers don't have to code specific functions for each region.
Probably the only reason you've seen this on cpviewer and my app is because they are both skinnable and that is the one type of app in which really long numbers are used (percentages of the screen tend to get messy). Only when one of these values are stored to a text file and loaded does this issue turn up because it's a printing thing. If you are to create and use such values internally they will work just fine.
I tried it in danish and I can replicate the error, I just can't do anything about it. The problem appears to be that my program uses american vb controls and american controls can't handle EU style values. Internally the numbers get read fine, but if you try to apply them to a control, even if you pass it through a variable first it fails. This seems to be a core error as the program doesn't error out, rather it just quits. It's quite common in any visual studio 6 langauge to have regional issues just like this. This is why m$ no longer officially supports vs6.
Space Fractal:
hmm, I can just tell the control seen to been buggy, since the control didden't actuelly check wich formats it use (wich would been very prettty simple)..... (im dosen't know you use a microsoft, or a third party component). That all.
Cpviewer from http://www.cpviewer.emuchrist.org/ seen to work fine (mostly because it use integers values, not floats). But it seen, it dosen't support if I remapped some controls in some games (like pinball games).
But have a some trouble with http://www.mameroom.com/CPKD_info.asp (but I remember it works, it some time I used it)....
Maybe saving to a binary file would been better than store as text, or upgrade visual basic?
Howard_Casto:
Ironically, to get j5 to work well I had to keep using vb6 and not upgrade to .net.
.net offers a ton of cool new things and easier code. Unfortunately, it also has the most useless form controls I've ever seen. You think vb6's are bad, in .net you can't even make the background of a label transparent! Not only that, but you can't print a form unless it's visible, and even then it's a screen grab, cursor and all, meaning I would have to re-write the entire core if I wanted to keep the "-justprint" feature. The same issues are found on images too. What's the point of natively supporting pngs in .net if the background of the control can't be set to transparent?
Mind you I could have easily coded the whole thing in DirectX, but I was asked to make the app as compatible as possible when I was building it and a directx version would be video card dependant and require more resources.
I don't think binary will work either. The problem is visual basic itself is using the EU format internally and auto converting it to EU when Danish is the default langauge. This is why manually changing the commas to periods didn't work for you initially. The controls on the form, however are all expecting the american format. Stranger still if I calculate a number internally(without reading it), it appears in the American format. Makes no sense to me either, but I didn't write the thing.
If you are able to get it running with the xp plugins installed though, then I'll consider it ok as-is.
headkaze:
Using GDI+ would be the way to go if you were to go with .NET, although I'd assume it would be alot of work to port everything over. GDI+ still dosn't support the PNG's alpha channel though, you can set a transparent colour key though.
The GameEx Theme Editor was written using VB.NET, and was my first major program written in .NET. It was based on an assignment I did for Graphics Programming at Uni.
Feel free to check out the source. It's pretty crap but was helpful getting started on the Theme Editor. If your gonna keep up with things you will probably have to give up VB6 and move to .NET eventually. I used to code in VB6 and now that I've moved to .NET (I actually prefer C# now) I can't stand VB6 anymore. It will probably happen to you to!
Howard_Casto:
--- Quote from: headkaze on May 30, 2006, 06:55:37 am ---If your gonna keep up with things you will probably have to give up VB6 and move to .NET eventually. I used to code in VB6 and now that I've moved to .NET (I actually prefer C# now) I can't stand VB6 anymore. It will probably happen to you to!
--- End quote ---
heh I doubt it. Right now I'm being forced to upgrade one of my helper apps to .net because it can do something that vb6 can't (which hasn't happened to me in 3 years!) The vb6 version was very tiny and had maybe half a page of code. I ran it through the upgrade wizard, so far the amount of code has tripled, and I still haven't gotten it completely working yet. .net is great for programs that don't need a gui, so i might eventually switch my wrappers over to it, but the graphical interface, especially the default form controls are pure crap. Even if they'd just fix the form controls I'd happily jump ship. But when I don't have an image control and I can't make the background of labels transparent... bah!!!
Dk is mostly direct-x, so eventually it will be ported when vista can no longer handle vb6 and everone is actually using vista. But actually dk will be an easy port because it doesn't use any user controls.
Navigation
[0] Message Index
[*] Previous page
Go to full version