MMEX Discussion Forum

Vadim wrote:I've found a critical BUG for one minute of using mmex (in debug build click on "Notes" column's header).

I have fixed the problem in svn 699

Vadim wrote:Use Debug builds in your work, mates! It's not a proposition, it's requirement.

I love the project anymore

After start debuging all seems ok, but when I closed the app I have got the following message:

BTMMHOOK 30.10.2009 08:49:29 Thread<0FD8> Hook DLL loaded
"mmex.exe": Загружено "C:\Program Files\DigitalPersona\Bin\DpOSet.dll"
BTMMHOOK 30.10.2009 08:49:39 Thread<0FD8> Hook DLL unloaded
Detected memory leaks!
Dumping objects ->
{1742} normal block at 0x01402EF8, 48 bytes long.
Data: <( , > 28 00 00 00 00 00 00 00 18 2C 16 00 FF FF FF FF
Object dump complete.
Программа "[4024] mmex.exe: Машинный код" завершилась с кодом 0 (0x0).

This leak is well-known for me I will find this leak in the future I think.

So, what should we do now. We have this weekend to test 0.9.5. No more changes in branch except bugfixes if we find ones. If everything will be ok, the head revision of branch will be final release of 0.9.5 on next week.

We need to change the "check for new version" link back to Codelathe's webpage. I would do it myself, but I just don't have the time to do so due to work constraints.

I fixed the "check for new version" links.
Its checked in into 0.9.5

If all don't mind we will publish 0.9.5 this week. So, I vote to publish release. Nikolay, elliswr and madhan, what is yours conclusion?

Hi Everybody,

It's seems stable.
I'll check again tonight, then will check translations.

Let's do it.

It does look stable.

All translation files has been updated. svn 721.
Thanks.

So, revision 721 is 0.9.5 final
https://moneymanagerex.svn.sourceforge. ... ases/0.9.5
Now we should build mmex for different OS and upload binaries on sourceforge.

I built Ansi and Unicode setups for Windows, but I don't know how to upload them to sourceforge (or I don't have rights to do that).

Binaries will be hosted here at codelathe.com site, please send me the binaries after building directly to me. I will update the new release in the site.

Release is going up. Windows is done. Mac PPC is done. I need Intel and builds for Linux.

Intel builds will come over next couple days. I have to muck around with new targets to build from branch source again. Sorry for everyone waiting on that.

ok No problem. I won't send out the release announcement till we get the Linux and Mac builds up.

Please note, there can be no more checkins into 0.9.5. We have already built the binaries.

Hi Madhan,

For my oppinion we should fix bugs then recreate binaries.
Stupid bug: http://www.codelathe.com/forum/viewtopic.php?f=5&t=714

Regards

And one more problem:
http://www.codelathe.com/forum/viewtopic.php?f=5&t=715

PS The problem is actual for 0.9.6.0 (trunc) too.

Nikolay, it appears these bugs were found after we released to 0.9.5. I think I am going to rollback to 0.9.4.2 till we resolve these issues.

Is someone planning to work on them?

This bug bug: viewtopic.php?f=5&t=714

I cannot recreate on Mac, but this may be due to me changing the control from wxStaticBitmap to wxBitmapButton because the wxStaticBitmap did not show up at all on Mac. So I'll change it back to wxStaticBitmap and continue to play with the code to see if I can get it to work on wxMac.

I've fixed both bugs (http://www.codelathe.com/forum/viewtopic.php?f=5&t=714, http://www.codelathe.com/forum/viewtopic.php?f=5&t=715). So, I can build setups for Windows again. This release will be marked as 0.9.5.1. The real critical fix done for popup menu. We should publish 0.9.5.1. immediately.

Quick turnaround on those fixes, but this re-breaks the led on Mac, and wxstaticbitmaps still do not show (where as the wxbitmapbuttons did), so I don't guess we will address this for 0.9.5, I'll add it to the roadmap for 0.9.6

I understand that my "fixed" means reverted changes. Apply these changes to trunk later and try do not change control's type if it's possible.

Two questions...

Were the changes to wxLED actually necessary? It seems from the descriptions of the problems that the change to wxLED should not have any effect. Vadim, can you reinstate those changes to check (I don't have windows either) so we can have the LED working correctly.

Secondly, I think that this whole problem of the viewing transactions control would be solved if we went to a wxListBox instead of the rightarrow button and creating a menu on click. It mimics the behavior of a listbox anyway when you click on it, is there any good reason why it is not a listbox to begin with? This should get rid of the problem once and for all and we could have it working on both systems in this release.