djandruczyk wrote:
I found the problem!!
It's winblows XP. I have a fix in my current tree, abut a temporary workaround is to to right click on the icon on the desktop, select Properties, pick the "Compatibility" Tab and select "Run this program in compatibility mode for" and select Windows 98/Me.
This is ONLY needed as a workaround for XP users, and only for megatunix 0.9.5-0.9.7.
0.9.8 will have a fix in that prevents this problem..
It's caused by unicode text and my validator puking all over it. The fix is currently in CVS and will come out with 0.9.8 in a few days.
NOTE: This problem should NOT affect Win2k, and older systems.
I have XP and everything installed and works fine for me.
the bug happens when you highlight and type over a textentry value, 0.9.5-0.9.7 will tend to trash it and display garbage charactors.
using the normal +/- q/w, Pgup/Pgdn hotkeys will work normally however..
OK so it wasn't working right after all.
Everything looked good, but I haven't tried to make changes, but when I did try I got garbage characters.
89,88,87 Conquest TSI
1971 Jeep CJ5
MS2-V3.57 with map daddy, software 3.4.2 with EDIS on a Mitsubishi 2.6l turbo.
using Tuner Studio V3.0.28 / megalog viewer V4.1.17 and Shadow Dash V1.5.02
djandruczyk wrote:
the bug happens when you highlight and type over a textentry value, 0.9.5-0.9.7 will tend to trash it and display garbage charactors.
using the normal +/- q/w, Pgup/Pgdn hotkeys will work normally however..
OK so it wasn't working right after all.
Everything looked good, but I haven't tried to make changes, but when I did try I got garbage characters.
0.9.8 addresses this.. You can still use 0.9.7 but you'd need to use the hotkeys instead (q/w +/- Pgup/Pgdn)
I just gave your sugestion a try and everything so far works as advertised no funny characters and every spin button works now I feel better now knowing that maybe I am not cursed thanks for your hard work and sorry to be a thorn a your side.
Cant wait till the next release!!!!!!
thanks 71jeep
Allen....
I just gave your sugestion a try and everything so far works as advertised no funny characters and every spin button works now I feel better now knowing that maybe I am not cursed thanks for your hard work and sorry to be a thorn a your side.
Cant wait till the next release!!!!!!
thanks 71jeep
Allen....
No problem I'm glad it worked. The next issue will be getting people to follow instructions to get 0.9.7 uninstalled (another bug, that hoses permissions on 2K/XP for mtx files making it not properly uninstallable). It's an easy fix, but 99.95% of people seem to never read the instructions...
Thanks to jsmcortina who spotted another memory leak , this time in the GTK+ runtime. So all your Win2k/XP users should DOWNGRADE your GTK+runtime from 2.10.7 to 2.10.6.
The bug is only in GTK+-runtime 2.10.7. It'll cause megatunix to consume about 2-3MB/second when on the runtime display tab eventually causing a crash.
djandruczyk wrote:The bug is only in GTK+-runtime 2.10.7. It'll cause megatunix to consume about 2-3MB/second when on the runtime display tab eventually causing a crash.
Yes. I've witnessed that too many times. I had given up until 0.9.8, but I haven't been able to try that version out yet. Looks like Tunix isn't the problem. Good work.
djandruczyk wrote:The bug is only in GTK+-runtime 2.10.7. It'll cause megatunix to consume about 2-3MB/second when on the runtime display tab eventually causing a crash.
Yes. I've witnessed that too many times. I had given up until 0.9.8, but I haven't been able to try that version out yet. Looks like Tunix isn't the problem. Good work.
MegaTunix DID have a memory leak in 0.9.7 on ANY tab, caused by the internal debugging code that would leak about 300KB/sec., So upgrading megatunito 0.9.8 nd downgrading GTK+ to 2.10.6 (win32) should solve all current memory leak issues.
Problem is, when i try to burn to ecu in rev limit settings, it doesn.t Values stay red, and when i read from ecu, it brings back the old values, so they are not being stored when i click the store permanantly button.
RickRST wrote:0.99, works nicely with my 4 bar map sensor
Problem is, when i try to burn to ecu in rev limit settings, it doesn.t Values stay red, and when i read from ecu, it brings back the old values, so they are not being stored when i click the store permanantly button.
Hi res extra code, XP
you MUST HIT ENTER, when entering values.. if they are RED they are NOT SENT to the ecu yet...
If you were hitting enter, I need to know the EXACT controls that were not working (screenshot helps)
I feel better now knowing that maybe I am not cursed 
thanks for your hard work and sorry to be a thorn a your side.