|
Pardon me, shameless plug -> http://www.codeproject.com/vb/net/ClickThroughWindows.asp[^]
You can't make just a single control transparent to the mouse using this technique. It's the whole form, or nothing. Alpha-based mouse transparency doesn't work correctly, at least on 2000 and XP, it doesn't.
If you try to make just a control, like a panel transparent, then put it on a form that doesn't support transparency, it doesn't work. The click still works on the control itself. At best, it would fall to the form the control is on.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
|
RomkaFromUa wrote: I understand, you are a great programmer, but I'm also not just a user.
OK, smartass... I never said I was a "great programmer".
You better look up the definition of "opaque[^]". I can't tell what you want from your orignal description. Opaque and transparent are direct opposites of each other. Do you want a control you can see through? That's transparent. Can't see through it? That's opaque.
Which is it?
I posted the link to the article as a POSSIBLE guide to show you how to make an entire form pass through mouse moves and clicks. For you, it wasn't meant to be a guide to the WS_EX_LAYERED attribute.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
 ))
I see, that not just me dont know English well... cuz sometimes, in my Inet-searching experience, transparent windows meant to be fully transparent in some parts... and I want, as you understand
"Do you want a control you can see through?" - yessss )
+Thanks for terms description)
I'll reply concretely later.......
----------------------------
lalala, I'm from Ukraine
|
|
|
|
|
RomkaFromUa wrote: I see, that not just me dont know English well...
When you stop insulting people and just answer their questions, I'll take you off my blacklist...
You asked a question and, due to English not being your primary language, worded it using conflicting terminology. I THOUGHT I figured out what you wanted, but instead of clarifying, you decided to insult me. Have a nice life!
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Dave, you understood me in a wrong way!
I was talking about other people over Inet, that also dont know English well and so have made me not understand what is the difference between transparency and opacity!
I hope that this thought was written clearly for you and you'll not be angry for me...
People... he talked something about blacklist... if he dont hear me, please make him understand that I dont want to make him angry
Also I hope somebody will help me with my problem, but I begin to see that this problem is unsolveable 
----------------------------
lalala, I'm from Ukraine
|
|
|
|
|
If you want the control to be absolutely transparent, you'll have to draw it yourself. Using the Color.Transparent color won't do what you want, apparently, since setting the BackColor of a control to Transparent only makes the background of the control take on the properties of the controls parent container. It's not truely "transparent". This means that any control under your control will NOT show through in the "transparent" regions of your control.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Hi its a pleasure to see you now.
I DONT want an absolete transparency. I need to control its level. Your last idea (setting BackColor) was tested in the older times, and as you said, it is not what I want (I need to see controls through)
Maybe, now everything is clear with my unperfect English )
But for this time I dont see any abilities to solve my problem
1) set BackColor to transparent value - not good, cuz dont see controls through
2) WS_EX_LAYERED - not good - it works on top-level windows, not child windows , and I need the last variant
3) Regions - also not good - they provide full transparency, not controllable.
Any other ideas - I'm waiting.
----------------------------
lalala, I'm from Ukraine
|
|
|
|
|
If you ned to click on those controls, go back and read my article. It explains what the process is to make the form "click-through" and you can still use transparency. There's even a sample application in it.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Dave, WS_EX_LAYERED does not work with child windows/controls!
----------------------------
lalala, I'm from Ukraine
|
|
|
|
|
No, it doesn't. You also cannot make just a single control click-through. It's the entire form, or nothing.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Ok, I'll try to ask for another variant - more simple.
TRANSPARENT FOR MOUSE MOVES AND CLICKS - dont pay attention to this feature for now.
Just - opaque control 
----------------------------
lalala, I'm from Ukraine
|
|
|
|
|
My current C#.NET project is MDI-based.
I am using a user control that has 10 textboxes. This user control is repeated 20 times on a screen. (that gives 200 textboxes on the screen)
When I refresh the screen, I can see every textbox being drawn to the screen from top to bottom. The desired behaviour is that the screen should appear in a flash without any rollover effect.
Currently, the screen gets refreshed at a rate of 35 milliseconds. We need to minimize this to 2-3 milliseconds.
I found that When one textbox of the usercontrol refreshes, internally Paint Event of that control is raised.
The textbox Paint Event internally raises its container's (user control's) paint event.
Subsequently, the user control raises paint event of all textboxes in it.
So I tried to suppress raising the Paint Event of usercontrol when the textbox is refreshed. (by Override OnPaint and Override OnPaintBackground event).
Also, double buffering is used.
But this has not helped much.
Is there a way we can accomplish a refresh rate of < 5 milliseconds?
|
|
|
|
|
SwEr wrote: Is there a way we can accomplish a refresh rate of < 5 milliseconds?
Don't try to do so much in the painting. 200 textboxes is excessive - do you really need that many on screen at one time? A user can only use 1 at a time, and only look at a couple at a time.
|
|
|
|
|
I think you'll find the problem is that the background is painting over the textboxes before the textboxes are re-drawn.
You should be able to override the PaintBackground event of whatever contains the text boxes, and draw the background yourself without painting over the text boxes.
|
|
|
|
|
SwEr wrote: Currently, the screen gets refreshed at a rate of 35 milliseconds. We need to minimize this to 2-3 milliseconds.
With that level of refresh this window must be display only window (read-only). If that is the case using all those controls is just a bad idea. You might look into just painting that data or something.
led mike
|
|
|
|
|
Each user control, represents a device. The text boxes in the user control would display the devices' dynamic properties. There would be as many user controls as the number of devices. Right now i am assuming only 20, but in reality could be much more. I cannot replace the user controls with a datagrid as the number of properties to be displayed would be different for each device. The user control as such is rendered by the device library. All these user controls are placed in a form container. The entire data received from devices needs to be displayed on one screen (no tabs,etc) as the user needs to continuously monitor it.
Is it possible to handle this at a lower level? (like drawing the data into an off screen version of the Form and then copying it on screen in one shot).
Any thoughts?
|
|
|
|
|
Is it for SCADA, DCS or instrumentation?
Most of these application doesn't use standard form and controls.
You can check out SL-GMS or Wonderware for these kind of instrumentation displaying. I am sure there are others.
|
|
|
|
|
Greetings!
I'm trying to connect to a database and read certain fields from it. I'm unable to read any fields from it and would appreciate your help debugging/fixing the problem.
Here is what I have:
1. A file that acts has the database interface code:
<br />
public class AppDatabaseInterface<br />
{<br />
<br />
private string m_cstrDefaultdbDir = "C:\\";<br />
<br />
private const string m_cstrDBFileName = "DefaultDatabase.mdb";<br />
<br />
private System.Data.OleDb.OleDbConnection m_dbConn;<br />
<br />
public AppDatabaseInterface()<br />
{<br />
System.Reflection.Assembly assm =<br />
System.Reflection.Assembly.GetAssembly(System.Type.GetType("AppDatabase.AppDatabaseInterface"));<br />
m_cstrDefaultdbDir = System.IO.Path.GetDirectoryName(assm.CodeBase.ToString());<br />
m_cstrDefaultdbDir = m_cstrDefaultdbDir.Remove(0, 6);
<br />
OpenDatabase();<br />
}<br />
<br />
<br />
private void OpenDatabase()<br />
{<br />
lock (this)<br />
{<br />
if (m_dbConn == null)<br />
{<br />
m_dbConn = new OleDbConnection();<br />
}<br />
else<br />
{<br />
if (m_dbConn.State != ConnectionState.Closed)<br />
{<br />
m_dbConn.Close();<br />
}<br />
}<br />
<br />
try<br />
{<br />
m_dbConn.ConnectionString = string.Format(<br />
@"Provider=Microsoft.Jet.OLEDB.4.0; Data Source={0}\{1};",<br />
m_cstrDefaultdbDir, m_cstrDBFileName);<br />
}<br />
catch<br />
{<br />
Console.WriteLine("Could not open database");<br />
}<br />
m_dbConn.Open();<br />
<br />
}<br />
}<br />
2. The "Makes" Method
Here's the "Makes" method in the AppDatabaseInterface.cs file
<br />
public string[] Makes<br />
{<br />
get<br />
{<br />
OleDbDataReader dbr = null;<br />
ArrayList Makes = new ArrayList();<br />
<br />
OleDbCommand cmd = new OleDbCommand(string.Format("SELECT * FROM {0};", "Speakers"), m_dbConn);<br />
dbr = cmd.ExecuteReader();<br />
<br />
while (dbr.Read())<br />
{<br />
for (int it = 0; it < dbr.FieldCount; it++)<br />
{<br />
string strField = dbr.GetName(it);<br />
if (strField == "MAKE")<br />
{<br />
string make = (string)dbr.GetValue(it);<br />
bool found = false;<br />
foreach (object o in Makes)<br />
{<br />
if ((string)o == make)<br />
{<br />
found = true;<br />
break;<br />
}<br />
}<br />
if (found)<br />
Makes.Add(make);<br />
break;<br />
}<br />
<br />
}<br />
<br />
}<br />
string[] strMakes = new string[Makes.Count];<br />
int i= 0;<br />
foreach (object o in Makes)<br />
{<br />
strMakes[i++] = (string)o;<br />
}<br />
return strMakes;<br />
}<br />
}<br />
3. The actual UI form
<br />
public partial class frmAppDatabase: Form<br />
{<br />
AppDatabaseInterface m_database;<br />
<br />
public frmSpeakerDatabase()<br />
{<br />
InitializeComponent();<br />
<br />
m_database = new AppDatabaseInterface();<br />
<br />
string[] strSpeakerMakes = m_database.Makes;<br />
<br />
for (int i = 0; i < strSpeakerMakes.Length; i++)<br />
{<br />
cbSpeakerMakes.Items.Add(strSpeakerMakes[i]);<br />
}<br />
}<br />
What I want this portion of the code to do is to fill in the combobox with the various items from the specified field in the database. However, I see nothing.
The Access file is in the \bin\debug directory of the project.
Could you please advice me as to what is wrong?
Thanks!
-- modified at 13:54 Friday 22nd September, 2006
|
|
|
|
|
Are you getting a run-time error or are you just not seeing anything displayed when you are trying to populate your combobox? I haven't analyzed your code thoroughly yet, but try putting a breakpoint in the for loop that populates "Makes" from the db table to see if you're actually getting data out of it. If you ARE getting the correct data out of the table, follow the debugger down until you lose it. Reply back with what you find. (I don't have .NET available right now so I can't plug your code into a project to debug it yourself. ....So help me help you......help me......help you lol)
|
|
|
|
|
Thanks for your reply!
There is no run-time error. The code compiles and runs just fine. The form comes up but the combo box has nothing in it.
I've stepped through the code to make sure that the database connection sees the Access file.
|
|
|
|
|
...I think your problem is that you are executing a query rather and not storing it in an OleDbReader object. (this is all off the top of my head, mind you) If you are in VS, use Intellisense to see what db.ExecuteReader() returns...I think it's an OleDbReader object. You need to store the results in one and read from it instead of your db connection. I don't believe that "db" as you have defined it will work the way you are wanting to to work. You need a companion class to hold the results of a query and read from it. I can help you out with that, but I don't have the files handy. I'll get them real quick and I'll be back.
|
|
|
|
|
Yup...I was right. You need to store your "db.ExecuteReader" results in an OleDbReader object. I referred to a project that I'm currently working on and I think I might be able to help you out a little bit. I've only included the relevant portions of my code, but I accomplished exactly what you are trying to do. I wanted to populate a combobox with the contents of my "category" table. I'm not finished copying (Having to write it down by hand and bring it over...my development computer is not "plugged in" to my network) I'm going to go back, get more code and place it here in an edit. I'll let you know at the end of this post what I'm going to be bringing back next post
...a little bit of explanation. I have 2 classes (clsDatabase & clsQueryResults) that provide a layer of abstraction away from ADO.NET. This allows me to separate my application logic from database management commands.
The form code:
private void form_Load(object sender, System.EventArgs e)
{
ArrayList mCategoriesToDisplay = Manager.getAllCategories();
foreach(clsManager.clsCategory cat in mCategoriesToDisplay)
{
this.cbCategory.Items.Add(cat.Title);
}
}
"clsManager" code ...I use "clsManager" as a mediator to perform network and assembly linkage. If I were developing a desktop app, this would not be needed...just thought it might be helpful to explain why this layer of abstraction is even present
clsCategoryList mCategoryList;
.
.
.
public ArrayList getAllCategories()
{
return mCategoryList.getAllCategories();
}
"clsCategoryList" is basically my own way of holding my category objects. getAllCategories returns an ArrayList of clsCategory objects
public ArrayList getAllCategories()
{
string sql = "Select * From Category";
clsQueryResults resultSet = new clsQueryResults();
resultSet.Open(mDatabase, sql);
while(!resultSet.EOF)
{
clsCategory category = new clsCategory();
category.RestoreStateFromQuery(resultSet);
Categories.Add(category);
resultSet.NextRecord();
}
return Categories
}
The code I will bring you in my next post will be what happens when we move closer to ADO.NET as well as what happens inside the actual "clsCategory" object. ...clsCategory is the only place along the "data chain" that can actually interface with a clsDatabase object and a clsDatabase object is the only thing that can actually communicate with Access.
inside "clsQueryResults"
public void Open(clsDatabase database, string sqlQuery)
{
mProvider = database.getProvider;
if(mProvider.Equals("OLEDB"))
{
if(database.State == System.Data.ConnectionState.Open)
{
mOleReader = database.ExecuteQuery(sqlQuery)
}
}
else if(mProvider.Equals("SQLSRVR"))
{
}
NextRecord();
}
public void NextRecord()
{
if(mProvider.Equals("OLEDB"))
{
mEOF = !mOleReader.Read();
}
}
public bool EOF
{
get
{
return mEOF;
}
}
"clsDatabase" stuff
private OleDbConnection mDatabase = null;
.
.
.
public clsDatabase(string connectionString, string provider)
{
databaseProvider = provider.ToUpper();
connection = connectionString.ToUpper();
if(databaseProvider.Equals("OLEDB"))
{
mDatabase = new OleDbConnection();
mDatabase.ConnectionString = connectionString;
}
}
public OleDbDataReader ExecuteQuery(string sqlQuery)
{
OleDbCommand OleCmd = null;
if(mDatabase.State == System.Data.ConnectionState.Open)
{
OleCmd = new OleDbCommand();
OleCmd.Connection = mDatabase;
OleCmd.CommandText = sqlQuery;
}
return OleCmd.ExecuteReader();
}
"clsCategory"
.
.
.
public void RestoreStateFromQuery(clsResultSet resultSet)
{
this.Title = resultSet.GetColumnValue("CategoryTitle");
}
I did not include clsResultSet's "GetColumnValue" method...I left a little bit for you to do for yourself. Look up OleDbDataReader on the MSDN to find out how you should define this method. You're going to be looking specifically for "GetOrdinal" and "GetValue". I hope this helped out a little bit....actually I hope it helped a lot.
-- modified at 17:18 Friday 22nd September, 2006
|
|
|
|
|
Wow... thanks, mate! You're a huge help... I really appreciate this!
I just figured out that making the following change in my AppDatabaseInterface.cs file did the trick for me:
<br />
if (!found)<br />
alMakes.Add(make);<br />
but your approach on the whole seems better and I'm going to look into it.
Thank you very much!
N.
|
|
|
|
|
You're not using an object oriented design are you? I assume from your variable names that you're doing something with sound equipment?? Typically, you would do something like the following
public class clsSpeaker
{
private string mMake;
private string mModel;
public Speaker()
{
mMake = "";
mModel = "";
}
public void RestoreStateFromQuery(clsResultSet rs)
{
this.mMake = rs.GetColumnValue("SpeakerMake");
this.mModel = rs.GetColumnValue("SpeakerModel");
}
public string Make
{
get
{
return mMake;
}
}
public string Model
{
get
{
return mModel;
}
}
}
...so now, you can just instantiate your clsSpeaker class inside your UI, Deserialize it from your database query, and then do the command that I included in my previous post labeled as "form code." It makes the code much more legible and bug tracing is a lot easier because your code is properly compartmentalized.
btw, put your code in "pre" tags instead of "code" tags...It's a lot easier to read. (Pre tags are what I used to post my code in this thread)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
