Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.

Quickwin combo boxes

Intel_C_Intel
Employee
890 Views
I've got a project converted from CVF (which is totally debugged and in distribution) which I'm trying to get going in IF 8. There are some issues regarding libraries and calling convention options which I've submitted to support.
Now I find that combo-list boxes in dialogs do not blank out the edit box--it is filled with a long string of blanks and garbage, which dso not affect the selection process or operation--it's just ugly. I've tried setting things in various ways, but to no avail. Has anyone else encountered this? Any suggestions?
0 Kudos
2 Replies
Jugoslav_Dujic
Valued Contributor II
890 Views
Well, I'll suggest a replacement...

Download and install my Xeffort library. Then, if you want zero changes in your source code, do the following:

- add "Xeffort.lib" to your linker options
- create a replacement DFLOGM (IFLOGM?) module and insert it into your project:
MODULE DFLOGM
USE XFLOGM
END MODULE DFLOGM
(the replacement module is called XFLOGM). (If you want to revert to the default version later, don't forget to delete DFLOFM.mod from your Debug folder).

It's supposed to do the same thing as DFLOGM/IFLOGM and more (and better) and be 100% source-compatible (except for few minor incompatibilities listed in Tools/Xeffort Help -> XFLOGM2.0/Known Incompatibilities).

Please let me know about possible problems and/or incompatibilities.

Jugoslav
0 Kudos
Paul_Curtis
Valued Contributor I
890 Views

I have converted much Win32-F90 code from CVF to IVF and did not encounter any problems with list/combo boxes. However, this will explicitly clear out listbox content:

SendControlMessage (hwnd, controlId, LB_RESETCONTENT, 0, 0)

where hwnd is the (parent, dialog) window handle and controlId is the specific listbox control element being addressed.
This code would be inserted in the dialog's proc function as needed (for example, as part ofyour response toWM_INITDIALOG), which you may not have access to if you're using "quickwin".
0 Kudos
Reply