common-controls

Common Controls on a Transparent Window?

天涯浪子 提交于 2020-01-16 18:00:09
问题 While there are lots of variations of the question, there doesn't seem to be a specific answer to a simple case of wanting to use built-in common controls on a transparent window using Win32. I don't want the controls to be transparent, I just want the border around it to be transparent. I can't believe MS didn't update the .dll's to handle transparency when they added it, but I guess they forgot? Is there a specific method that works. A button can get close with WS_EX_TRANSPARENT, but flaky

Could not find file 'Microsoft.Windows.Common-Controls, Version=6.0.0.0, Culture=*, PublicKeyToken=6595b64144ccf1df,

自闭症网瘾萝莉.ら 提交于 2019-12-30 08:50:44
问题 I'm trying to integrate this library into my application. At first it crashed with Unable to find an entry point named 'TaskDialogIndirect' in DLL 'ComCtl32'. so I uncommented <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*" /> </dependentAssembly> as was recommended here. Now the application won't compile with the following message: Could not find file

Is it possible to lock memory used by common controls in my application?

雨燕双飞 提交于 2019-12-25 09:20:04
问题 I'm writing an application that encrypts its data. It can then display it unencrypted using the app's UI after a user enters password. My goal is to minimize exposure of plaintext data while in RAM. For that I want to prevent swapping it to disk as much as possible. I know that I can adjust my process's working set (by calling SetProcessWorkingSetSize API) and then lock those sensitive pages in RAM (by calling VirtualLock.) That, in theory, should minimize the chances of it being written to

Is it possible to simulate tri-state checkboxes in Microsoft TreeView Control 6.0 (MSComctlLib.TreeCtrl.2)?

走远了吗. 提交于 2019-12-24 00:53:10
问题 I'm using the Microsoft TreeView Control 6.0 in Microsoft Access. It seems to work very well, except that it doesn't seem to have a greyed out state, indicating that some, but not all child nodes are checked. I've looked into using my own images to simulate the checkboxes, but if I do this, I then have to remove the real checkboxes or it looks like I have two checkboxes for each item... but then I don't have any checkboxes and I can't work out how to handle a click on the images. I can find

TVITEM LPARAM to store string

给你一囗甜甜゛ 提交于 2019-12-13 04:07:02
问题 I've got a treeview listing files that are dropped upon it. When I make a new treeview item, I'd like to store the address of the file as a string in that item, and retrieve it for various nefarious purposes at a later point in time. Looking at the TVITEM structure in Microsoft docs, apparently LPARAM is the place to store a value: lParam Type: LPARAM A value to associate with the item. So, I have gone ahead and done that: TVITEM tvi; tvi.mask = TVIF_TEXT; tvi.pszText = const_cast<char *>

Are native Windows Controls still used in .NET GUIs?

主宰稳场 提交于 2019-12-10 17:54:17
问题 Is the stuff that is displayed when you create a GUI with WinForms or WPF still based on the native controls like Common Controls or any of the system provided Window Classes or is everything that is displayed "custom" drawn by the framework? Note: I'm not talking about stuff like a file dialog, but GUI that was actually implemented with WinForms or WPF. And yes, this is purely out of interest. 回答1: User HighCore commented: WPF Uses an "HWND" for the Window objects, but then all other objects

Imagelist with alpha blend icons loses Transparency

僤鯓⒐⒋嵵緔 提交于 2019-12-09 12:56:00
问题 Here is (more or less) a related question: Delphi - Populate an imagelist with icons at runtime 'destroys' transparency. I have tested @TOndrej answer. But it seems I need to have visual styles (XP Manifest) enabled for this to work (version 6.0 of Windows common controls will be used - which I don't want right now). I add the Icons at run-time via ExtractIconEx and ImageList_AddIcon . Apparently setting ImageList.Handle to use System Image-List handle, does not require XP Manifest. so even

Common controls are not properly painted when I resize window

五迷三道 提交于 2019-12-01 16:16:52
问题 INTRODUCTION: I am creating tab control with child dialog boxes as pages. I have Visual Styles enabled via #pragma comment. I have also called InitCommonControlsEx and #pragma comment( lib, "comctl32.lib" ) as well. Initially, when window loads, dialog and its common controls have proper background, please see image below: During resizing things are not so consistent -> background starts to mismatches visibly. I will provide screenshot below: You can clearly see that checkbox and static

Once and for all: how do I get a fully transparent checkbox, button, radio button, etc. in Windows API, and not with a black background?

我的梦境 提交于 2019-11-28 02:24:12
First, sorry if I sound arrogant/rude here. All right, so everyone has run into this by now (I hope); I just haven't found any adequate answer anywhere . We start with a Common Controls 6 manifest and case WM_CTLCOLORSTATIC: if (/* window has WS_EX_TRANSPARENT */) { SetBkMode((HDC) wParam, TRANSPARENT); return (LRESULT) GetStockObject(HOLLOW_BRUSH); } and give our labels WS_EX_TRANSPARENT . They become transparent; so far so good. Now we have to add that style to our checkboxes (because checkboxes respond to that and not to WM_CTLCOLORBTN for some reason). And... the checkboxes become black!

Once and for all: how do I get a fully transparent checkbox, button, radio button, etc. in Windows API, and not with a black background?

核能气质少年 提交于 2019-11-27 04:56:03
问题 First, sorry if I sound arrogant/rude here. All right, so everyone has run into this by now (I hope); I just haven't found any adequate answer anywhere . We start with a Common Controls 6 manifest and case WM_CTLCOLORSTATIC: if (/* window has WS_EX_TRANSPARENT */) { SetBkMode((HDC) wParam, TRANSPARENT); return (LRESULT) GetStockObject(HOLLOW_BRUSH); } and give our labels WS_EX_TRANSPARENT . They become transparent; so far so good. Now we have to add that style to our checkboxes (because