I'd stick with a mutex in that case. You'll run into race conditions if you try to pass arguments between opening windows because you have no idea what order the loads are going to complete in.
As far as detecting multiple selections, just use FindWindowEx et.al. to just ask the explorer responsible for the launch if there were multiple selections.
tring mutexName = "e50cf829-f6b9-471e-8d9f-67eac3699f09"; bool grantedOwnership; //we prefix the mutexName with "Local\\" to allow this to run under terminal services. //The "Local\\" prefix forces this into local user space. //If we want to forbid this in TS, use the "Global\\" prefix. Mutex singleInstanceMutex = new Mutex(true, "Global\\" + mutexName, out grantedOwnership);
try {
if (!grantedOwnership) {
Application.Exit();
}
Application.Exit will kill any secondary instances
FindWindowEx and company to find the actual window, and then you'll need to get an IAccessible from the hWnd, then just use that interface to examine it.
BTW, be really careful that you don't have any code paths that don't release the mutex if you crash - otherwise it's lights out until next reboot.
VB.NET and C# are mostly just wrappers over the .NET Framework. String interpolation is purely done in C#, so the actual runtime execution isn't going to change.
Sure. So we're looking at 3 builders being instanciated, with their respective outputs ultimately concatenated (using yet another builder?) - my point is that it's abusive...
I never had a C64. Wanted one as a kid, but we got a TRS80 IV instead. Probably worked out for the best, because I had to learn BASIC to program stuff because there were like 2 games for it.
I hope they bust the drug/insurance companies up, like Roosevelt busted railroad, oil, and a couple other industries, but capitalism, with all its faults, is good enough for me.
I am working on a script to write an array formula to a large number of cells. I have a code that works, but is very slow. Any thoughts on how to speed it up? Here is a small amount of the code as it is written now. It repeats itself down to row 17.
Sub make_sheet()
Dim m As Integer
Dim h As In...
@Hosch250 There was an interesting proposal I heard the other day to just have the government buy drug companies. It turns out it's cheaper at current market caps to buy them than it is to pick up medicare\medicade and cover emergency services for the indigent.
@Mat'sMug @Comintern @ThunderFrame Stuff keeps clicking for me. Even though I still have Sub MakeThingsPretty and lngResponsesinFile, my reusable variable names are disappearing and I am comfortable enough with methods that I already know how I will use RD's fake folders.
Null is returned from excel range object. I'm not at a pc now but I think .mergearea is one if there is a mix of merged and not. Also found in ado recordsets. So we test for isnull.
I ran a Macintosh emulator on an Amiga, which let me create larger windows than a Macintosh could display. Saving Pascal work would also save window coordinates, so the window was then off the screen on the Macintosh with no way of resizing it.
I have another "What's the proper way to do this?" question
So I've been sorting my methods by level of abstraction, I guess. I have my god macro, and then it calls methods, and sometimes those methods call their own methods.
If I have a variable (an array, in this case) that needs to be used in multiple lower level methods, should I store the variable in a higher level method and pass it to each lower level function, even if it has little to do with the higher level method stuff?
I know storing a separate copy in each lower level method is wrong because then if you need to change the variable you have to change each copy of it.
But is there a better practice I should be considering?
@puzzlepiece87 It starts wit one variable, and then pretty soon it's 2, and 3, and so on. Whether you have 1 variable that is reused by other methods, or 5000, those variables constitute your model. Create a model class, assign the model the properties and state it needs, and then pass the model to your functions.
@puzzlepiece87 You presumably already do something like that when you have a reference to an Excel.Range or Excel.Worksheet. If you pass a Range reference to a function, to tidy column widths, you're already passing a model, but that model just happens to be one defined by Microsoft.
You can use Send To for this. It supports multiple files.
I am working on a script to write an array formula to a large number of cells. I have a code that works, but is very slow. Any thoughts on how to speed it up? Here is a small amount of the code as it is written now. It repeats itself down to row 17.
Sub make_sheet()
Dim m As Integer
Dim h As In...
VBA Rubberducking
VBA Rubberducking