FiveTech Support Forums

First, a comment. The guidance provided on this forum is amazing. I have been working through several challenges, reading older posts, etc. and most of my questions have been answered.

I am studying moving from xBuilder to UE Studio project with a very large application. I've reviewed the samples people posted and have my files configured as suggested.

I was able to get a build. I do have a problem with some functions apparently not supported so I created dummies for those. I can work with that for now and get some workarounds later.

My main problem is that none of my bitmaps show up. I use them on button bars, screens, etc. My guess is I'm missing a file ( ? lib ) or .dll
My second huge problem is the program is much slower then the xCC build with xBuilder
The third problem is this. From the main window, I call a dialog with an xBrowse. Clicking on an entry in the browse will bring up a multi-folder dialog. In this build, it crashes the program with a windows message that it stopped working.

With all things going on, someone may well say "hey you need ...."

Your comments are appreciated.

TimStone wrote:My main problem is that none of my bitmaps show up. I use them on button bars, screens, etc.

TimStone wrote:My second huge problem is the program is much slower then the xCC build with xBuilder

Memory option ? Where ?

In your resource editor.

EMG

There in lies the problem ... no resource editor. I pretty much handcode the .rc file now ... I get much better alignment, etc.,

I'm calling bitmaps created in Axialis. In the .rc it is simply TEST BITMAP "Test.bmp"

Can you show a little sample of the problem?

EMG

Tim,

Please use this tool to inspect your EXE and check that your bitmaps are inside it (resources folder):

peinfo.exe yourapp.exe

http://www.fivetechsoft.com/files/software/peinfo.exe

Yes, all bitmaps are in the resource in the .exe.

It may be the format of the bitmaps. I suggest trying one of the bitmaps provided by FWH to see if it works.

Regards,
James

My second huge problem is the program is much slower then the xCC build with xBuilder