|
I create combo box dynamically
<br />
CComboBox *combo;<br />
combo = new CComboBox;<br />
CRect rt(10,0,100,10);<br />
combo->Create(WS_CHILD|WS_VISIBLE|WS_VSCROLL|CBS_DROPDOWN, rt, this, IDC_COMBO3);<br />
but when I click on the drop down arrow, the drop list don't appear. Only a thin narrow black line is shown below. How can i extend the drop down list?
thanks.
|
|
|
|
|
If you are using Visual studios go into the Resource view, and find you dialog box. open the box then put the cursor over the down arrow that would normally open the list. This will cause a outline of your drop-down list box to show up make the outline larger, for some reason the default setting "even though it looks big enough to show information" is so small it will not display anything.
|
|
|
|
|
I can't customise it through controls and resource view, the combo box is created dynamically , not in resources.
|
|
|
|
|
george ivanov wrote:
CComboBox *combo;
combo = new CComboBox;
CRect rt(10,0,100,10);
Make the height more I believe.
CRect rt(10,0,100,300);
this is this.
|
|
|
|
|
|
I have a VS.net C++ Project that requires certain DLL's exist on the users system to run. As part of the project I would like to detect the users OS and install the dll's in the required system folder(s) when the user starts up the application. Can I do this or should I just create an installation disk to handle it?
Thanks.
Jerry
|
|
|
|
|
If you have statically linked your program to the dlls, then you will need an installation program I believe.
If you are loading the dll files dynamically using LoadLibrary(...), then you can have the dll files in the exe as resources, and copy/install them onto the system if they are needed.
this is this.
|
|
|
|
|
khan++ wrote:
If you have statically linked your program to the dlls, then you will need an installation program I believe.
No, you cannot link statically to dynamic link libraries. SLL's are compiled libraries that will be linked together with your program. It will make your executable larger...
DLL's however are linked to at runtime. When you run your program, DLL's can be loaded at startup, on demand or manual. This requires extra files (DLLs) to be shipped with your product.
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
Bob Stanneveld wrote:
DLL's however are linked to at runtime. ...
Exactly. I used the wrong words. Thanks for the correction.
this is this.
|
|
|
|
|
He probably should have said 'implicitly' linked to the DLL.
Static Linkage - Traditional LIB files - MAkes EXE larger.
Implicit Linkage - DLL Files - Exe not necessarily larger, but won't run if DLL cna not be found and loaded.
Dynamic Linkage - DLL Files - Your EXE does LoadLibrary and GetProcAddress to load the DLL and call functions. With this method, your own EXE could possibly deploy DLL.
|
|
|
|
|
Hello,
Why would you wan't to place the DLL's in the system folder? Most people hate it when 3rd party libraries are placed in those folders..
Anyway, I think that it is better to make an installation disk and do some checks when the DLL's are needed. Don't install the DLL's when you detect an error, but inform the user and let him take appropriate actions. Make sure that you have the DLL's ready on your installation disk, so the user can copy them when he / she needs them.
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
Also, the OS hates it. The OS might hate it so much, that the user running the program will not even have access rights to copy files to the system folder! That is a lot of hate 
You could put the folders into a location ALL users have access to and then investigate "App Paths" registry entries for your EXE(s) to set up that folder as a location where DLL will be searched for loading.
|
|
|
|
|
I think that developers should keep the DLL's in the application folder. I really hate to see one application have different folders in multiple system folders.
IMHO one should set a registry key for a DLL that is installed and applications should check that DLL before installing, etc., etc.. This way, the files are manageble by the user. Also this technique allows different versions of DLL's with the same name to exist on the same system, thus avoiding DLL hell!
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
I need to multicast a bitmap image over the network with UDP and can't get it to work. Can someone please help me with full VC++ code to do this?
BoB
|
|
|
|
|
i got a response for my previous query about a thread variable and i got a feeling that i hav'nt explained the problem very clearly..so let me tell my problem again.
In my application i've to access a hardware and get some data from it, for which the vendor has supplied a BSP and few API calls.He says that for MFC applications i've to create an object of a class called TLV_STORE, which contains lot of static members associated with the board Library and ensure its lifetime overlaps all calls to the library function across different classes.
i've created the object in the InitInstance function(in the Heap using new operator) of the Class derived from CWinApp and i'm able to access the API calls of the board only from that class(i.e.when i try to access the API from a class derived from CDialog i'm getting Debug Asertion error).
is there any other place where i can declare the object so that it becomes visible to all the classes and i can access the API calls from different classes within in the application?
it will be really great if anyone can help me out in this.
rajeev
|
|
|
|
|
You can declare the variable as extern in stdafx.h
Implement it in some .cpp file.
In stdafx.h:
extern TLV_STORE g_Store;
In somefile.cpp:
TLV_STORE g_Store;
Initialize it somewhere in the program before using it.
this is this.
|
|
|
|
|
Hello,
Make a singleton for it:
class Single_TLV_STORE
{
public:
static TLV_STORE* Instance();
};
static TLV_STORE* Single_TLV_STORE::Instance()
{
static TLV_STORE TLVStore;
return &TLV_STORE;
}
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
-- modified at 9:04 Friday 16th September, 2005
|
|
|
|
|
Respected
All
How i can load a bitmap in Picture box ,,plz help with full VC++ code.
and also how i can refresh my dialogbox b/c some probelms are coming on device context.
david
|
|
|
|
|
CBitmap b;<br />
b.LoadBitmap(IDB_BTIMAP1);<br />
m_Static.SetBitmap(b);
You also have to set the "Type" to "Bitmap" in the Resource Editor.
About refreshing the dialog:
RedrawWindow();
this is this.
|
|
|
|
|
I'm Developing an application in which i need to create an object of the structure TLV_STORE and it should be visible to all the classes in my application.
i've created an object using "new" operator in the InitInstance and freeing it in the Exit Instance ,but the rest of my classes are unable to access certain functions because the object of TLV_STORE is not visible to them.
is there any other place where i can create the object so that it is alive & visible to other classes?
it will be really great if someone can help me out in this.
rajeev
|
|
|
|
|
1)Whats the meaning of "Thread variable" here ?
2)When you declare an Object of X class in InitInstance() it DOES not mean other classes must know this single instance of X class
3)
a) You have to include this following function in all your other classes
void SetMyObject(CXObject* obj)
b) And you must include a (private)member variable of X class object to be used by SetMyObject()
c) The definition of SetMyObject(CXObject* obj)
{
myPrivateXObj=obj;
}
Now ciao !!!! All your classes can use the Single Instance created at InitInstance() and can be deleted at ExitInstance()
redindian
|
|
|
|
|
rajeev82 wrote:
is there any other place where i can create the object so that it is alive & visible to other classes?
if you make it global, everyone can see it.
or, since everything can get to your CWinApp onject (via AfxGetApp), you can make that variable a member of, add some accessor methods to, your CWinApp class.
Cleek | Image Toolkits | Thumbnail maker
-- modified at 13:51 Friday 16th September, 2005
|
|
|
|
|
Hi all!
Would you help me to solute this problem.
here is my problem.
I changed my project from Japanesse to English (I only convert Strings).
I use VC++ 6.0 and Window XP(Enlish) to Compile two Release and debug verstions:
+ For English WindowXP , all of them run well.
+ For Japanesse WindowXP , only debug version run well but release version don't run.
Many thanks.
-- modified at 5:06 Friday 16th September, 2005
|
|
|
|
|
Check the Project setting of Debug and release .
Find out what dependency is missing in Release but not in debug
redindian
|
|
|
|
|
Hallo!
I have checked it.
My problem is here.
In Japanese Window OS, release version doesn't run. but it run well in English version OS.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
