|
I believe that the user's machines also need to have the COM OCX registered on their machines. From your message, it sounds like you have the Interops on their machines (which can not be registered), but it is not clear if the OCX is on their machines. If not, put the OCX on their machines and register the OCX and, hopefully, that will resolve the issue.
|
|
|
|
|
We've ran into some minor issues (fortunately nothing that can't be refactored) with a design for DAL and BLL in a project. We have a set of repository and service classes that deal with different domain model entities and so on.
We are looking to have a common (standardized) way of accessing those classes from client code. This is an ASP.NET web application. I was the first one to start the design and I instantiate my services as private static read only fields in each page whenever I need to use a particular service class' functionality, in example:
public partial class NewAsset : System.Web.UI.Page
{
private static readonly _catalogService = new CatalogService();
protected void Page_Load(object sender, EventArgs e)
{
Asset asset = _catalogService.FetchById(3);
}
}
The other developer created however a "master" class for the services and exposes them as public properties, so he has something like:
public class Service
{
private static CatalogService _catalogService;
public static CatalogService Catalog
{
get
{
_catalogService = _catalogService ?? new CatalogService();
return _catalogService;
}
}
}
Then in a page:
public partial class NewAsset : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
Asset asset = Services.Catalog.FetchById(3);
}
}
My approach will create more objects, although there's always one per page. The second approach would always use a single object instance, but somehow I don't like how he used properties for that. The service classes are not singletons themselves, there's no real factory pattern (unless something like this with properties could be considered as one..), it seems weird but at the same time I can't tell for sure that it's bad. I know where he comes from, as he doesn't have to instantiate the single services in each page...
Do you think that one way is better than the other? If so, then why?
|
|
|
|
|
Pawel Krakowiak wrote: Do you think that one way is better than the other?
Yes, obviously.
Pawel Krakowiak wrote: If so, then why?
Don't know. It depends on what is going on in CatalogService and associated aspects of the ASP.NET environment.
led mike
|
|
|
|
|
led mike wrote: Yes, obviously.
Aw, it doesn't help. 
led mike wrote: Don't know. It depends on what is going on in CatalogService and associated aspects of the ASP.NET environment
Service talks to a repository which retrieves and stores data in the database. Furthermore the service enforces business logic rules, sometimes of course it just passes the call to the repository if there's nothing specific to do. It may use some session state variables as well. I think it's a standard thing, some people may call it a CatalogManager.
|
|
|
|
|
Pawel Krakowiak wrote: Service talks to a repository which retrieves and stores data in the database.
So if that object will use a Database connection then hopefully it is designed to use connection pooling. If not it should be. That would be one primary concern and is therefore handled with connection pooling not within the scope of instancing the CatalogService objects.
Based on what you have posted it's possible that the idea of making CatalogService a singleton into the premature optimizations are the root of all evil [^]category.
Now that what the object does is somewhat known I will also comment that the singleton like code you originally posted does not appear to conform to best practices. Given there is no need to ensure a single instance the lack of correctness will likely not result in any problems.
led mike
|
|
|
|
|
I posted the same question to ASP.NET forums and someone said to be careful with the second approach (the "master" class) as this brings thread safety issues to the table. I think it may be a valid reason not to do this, but so far it's the only one I got.
As for the singleton part - nay, I wouldn't plan to turn the services into singletons, I personally don't see a need for this. It's just that second approach which looks to have only one instance per the whole application.
|
|
|
|
|
Pawel Krakowiak wrote: as this brings thread safety issues to the table.
Yes, that is what I was referring to in my last post
Pawel Krakowiak wrote: It's just that second approach which looks to have only one instance per the whole application.
Yes. It is a non standard approach which produces a Singleton like design.
If you are interested you can find a long discussion on Singleton on the c2.com site I linked to in my last post. You will find the thread safety issue being discussed there.
led mike
|
|
|
|
|
I am attempting to recreate the behavior that Outlook does when a new message comes in. I would like a popup (form) to be displayed as topmost however not to have focus.
I am using a windows form to manage a series of messages that arrive on the fly. When a new message arrives I use ThreadPool.QueueUserWorkItem() to queue the message for creation of a popup (a simple windows form that is stylized). I would like the popup to come to the front however not take focus from the user. I have attempted to use several Win32 API's including SetWindowPos, SetForegroundWindow, ShowWindow to solve this problem. I can get topmost or focus to work, but not in conjuction. Does anyone have experience with this that may be able to point me the right direction?
|
|
|
|
|
Member 3922930 wrote: I would like a popup (form) to be displayed as topmost however not to have focus.
Member 3922930 wrote: I have attempted to use several Win32 API's including SetWindowPos
Well setting form.Topmost to true works for me.
led mike
|
|
|
|
|
Just set the TopMost property to true.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
Topmost of course makes the form come to the foreground, however it also gives it focus. As stated I dont want the form to have focus. Similar to how outlook comes to the foreground, however it does not take focus away from where you are typing.
|
|
|
|
|
You might have to somehow remember what control you are at before you have the form come up. Use TopMost to get the form on top, then set the focus back to where you were.
Also, don't down vote people who are trying to help you. It'll just piss them off and be less inclined to helping you in the future.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
My aplogizes. I miss read it. I thought it was similar to other sites, asking if the answer was the correct one.
Im not sure if remembering where the user came from is something that can be reasonably done. I would just like to not take focus away. Even if I kept track of where the user came from (say IE webpage) I am not sure I would be able to put the cursor back in the exact box where they were.
It appears this is possible at some level as Outlook does it.
|
|
|
|
|
No worries. Think of the numbers as being like number of stars 
Not sure if you already saw this, http://bytes.com/forum/thread448993.html[^], even though it is in VB6, it shouldn't be hard to implement in C#
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
Zocrates wrote: however it also gives it focus. As stated I dont want the form to have focus.
No, that's what I meant in my post. At least it works as you describe on my system (XP Pro, VS2005)
I tried with both Mozilla and Notepad in full screen and my form came to top but focus remained with the previous window (Mozilla or Notepad)
led mike
|
|
|
|
|
Hrm. You have a main form that creates another thread to populate a second form? And the form is always on top of each screen yet doesnt have focus? This doesnt seem to be the case when I try this.
|
|
|
|
|
I tested this with a C# Winforms and an MFC application.
1) Main dialog launches and sets a timer to like 10 seconds
2) I manually bring another application like Mozilla or Notepad to the top and give it focus
3) Main dialog timer event fires where my code creates a second form or dialog. During 2nd window initialization topmost is set
4) 2nd window appears on top of Mozilla or Notepad but Mozilla or Notepad maintain focus.
led mike
|
|
|
|
|
I made a test app like you mentioned above and I get the desired action. However when I add in the code to make this form being called by a new thread it no longer has the desired result.
I am using ThreadPool.QueueUserWorkItem(new WaitCallback(DisplayPopup), test) to create a new thread so the program can continue executing while the popup sits on the screen.
|
|
|
|
|
Zocrates wrote: However when I add in the code to make this form being called by a new thread
I don't know what that means "make this form being called by a new thread"?
Your forms must be manipulated from a GUI thread not a worker thread. You use Invoke to do that.[^]
led mike
|
|
|
|
|
The popup is a new form. The main thread processes the main form. The second form (popup) is managed by a different thread.
|
|
|
|
|
I was able to find a solution.
I was able to remove the dependency on the ThreadPool by using the modeless Show() instead of modal ShowDialog(). This allowed my program to continue to process while the popup was still showing. This handled the none maximized screens.
For the maximized screens I overrode the 'ShowWithoutActivation' property of the popup form.
All this of course with TopMost set to true.
|
|
|
|
|
Hrm. Actually it doesnt seem to work everytime. It works in both full screen mode and normal mode. Then it will stop working. Then I resize a screen or something and it works again....
|
|
|
|
|
It appears to be working on both full screen and normal screen until I close one of the popups(forms). Then the very next one will take focus away. After that it will begin working properly until I close one of the popups.
|
|
|
|
|
Hey guys
I have an MDI form that has a panel across the top for displaying business information. Whenever any of this panel is updated..I get this nasty bleeding effect where i can see through the borders of the labels etc. Has anyone ever seen anything like this?
|
|
|
|
|
Not seen this but have you tried calling its Invalidate() method to force a redraw?
If it's the panel's child controls that are the problem call Invalidate(true)
DaveBTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
