|
The article is not "our" article. It belongs to the person who wrote it. Articles are contributed by the volunteer community, not necessarily by The Code Project. At the bottom of the article you're talking about you'll find a forum dedicated to that article. Articles are supported by the people who wrote them.
|
|
|
|
|
Hi I wrote a dvd burning utility using the code from imapi2Interop.cs by Eric Haddan in Code Project. It works fine. Thank Eric for posting the code.
I write my data in three sessions (on purpose)so that I can (hopefully) generate a unique id (Sha1 hash using the physical starting and ending offsets of each of the sessions + other stuff), according to what I read the offsets could change if the disc is copied.
I tried using MsftDiscFormat2Data.MultisessionInterfaces but it looks like it is not valid for closed dvd.
Any pointer or idea as to how I may be able to get the start and ending offsets of each of the sessions in the DVD?
Thanks.
|
|
|
|
|
Hello,
take the following scenario:
We have a Windows Forms application called "CallMultiple" which accepts e.g. one string parameter in the Main method.
Now - via a command input - this application is tiggered the first time. It gets the input string "first", and sets a static variable "invocation count" to zero as well as the parameter "first" into a static variable called "invocation type". Both static variables should be public.
With parameter "first" a GUI Window is presented.
The process only ends if somebody clicks the "Terminate" button in displayed GUI Window.
Now there happens a second invocation with parameter value "second".
(The case, that the value "first" is coming again shall not be handled for this question).
Question: is it possible to compare the parameter of this invocation ("second") to the parameter already stored in the first invocation "invocation type" = "first" ?
and if it is not "first" will do something different, e.g bump the static counter "invocation count" and then ends (that is: dispose the process).
Can the waiting process (first invocation) get the counter and display e.g. a message like "application called x times" before it will end (triggered by the "terminate" button in the GUI Windows)
That means: can two processes of the same assembly share data via public static variables ?
Can somebody answer this question.
Many thanks in advance
Wolfgang
|
|
|
|
|
|
What you want is IPC (Inter process communication). There is a section here on CP about that, and one project I like is NetMQ[^], a C# port of ZeroMQ. NetMQ can be used as an IPC system, and handles a lot of the things needed for that for you, making it a lot simpler to, for example, send messages with multiple parts (refered to as 'Frames' in NetMQ).
Depending on the size and complexity of the project, this may be overkill, but it may be useful in other places as well.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Hello,
many thanks for the quick answers.
They gave me valuable hints which I think will allow me
to solve my problem.
Just for your information: the problem is:
I want to control a flatbed scanner (any make).
I want to scan strips of a cine film which should be moved
through the scanner (in sections of about 4 to 20 cm - depending on the width of the scanners TPU) using a (custom built) transport mechanism with a stepper motor controlled by an Arduino UNO board.
The controlling program (FeederControl), which can be invoked by most scanning programs via a function that allows to show just scanned images with a defined image viewer (e.g. IrfanView) by triggering the specified program (in this scenario it will be not an image viewer but the FeederControl) providing the URL/URI of the just scanned image.
If the FeederControl program is invoked, it has to do the move and than has to press the "SCAN" button of the idling scanning program to start a new scanning process.
Than it has to wait until a new request is coming from the ScannerProgram and start the whole thing over again.
if you are interested:
see CineToVidWiki
I have to do the new program, because the old ScanController mentioned in the Wiki does not work successfully under Windows 10 and I have no idea why. It must be a TWAIN problem. And the envisaged solution would avoid to invoke the twain driver as it is done by the ScanController.
This will then only be done by the various Scanner programs.
Another advantage would be: the Scannerprogram can stay open and must not be invoked seperately for each scan, as currently the ScanController does. That means: the whole workflow is driven by the ScannerProgram and not by the FeederControl (which will be a pretty small program).
Many many thanks again
Wolfgang
|
|
|
|
|
Take a look at "single instance application". When you start the application again while an instance is already running, the command line parameters can be passed to the running application.
|
|
|
|
|
static void Main(string[] args)
{
int a;
int b;
int c;
HOME:
Console.WriteLine("Enter Any Number");
a = Int32.Parse(Console.ReadLine());
if
(a <= 0)
do
Console.WriteLine("Number must be greater than 0");
while (a > 0) ;
else
Console.WriteLine("Enter Second Number");
now question is that I want to repeat code until the value of "a" is greater than "0" (zero. how to do this?
|
|
|
|
|
First off, don't use int.Parse - use int.TryParse instead:
int a;
if (!int.TryParse(Console.ReadLine(), out a))
{
...
}
else
{
...
}That way your code won't crash if you mistype a number - int.Parse will throw an exception.
Second, look at your code:
if(a <= 0)
do
Console.WriteLine("Number must be greater than 0");
while (a > 0) ;
If you value is greater than zero it won't even get to the loop!
And if it did, all it would do is print the same line forever...
Probably what you want is something like:
if (a > 0)
{
while (a > 0)
{
...
a--;
}
}
else
{
...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
sorry bro... but i think u prolly didnt get what he is up to..
he needs that the program should not proceed till the user dosent enter a number which is greater than zero..
have a look at my answer
|
|
|
|
|
using System;
namespace blahblah
{
class blah
{
static int a=0;
public static void Main()
{
HOME:
Console.WriteLine("Enter any number:");
a = Convert.ToInt32(Console.ReadLine());
if(a <= 0)
{
Console.WriteLine("The number must be greater than zero");
a = 0;
Main();
}
}
}
}
^^ this works fine
But you gota remove all the parameters in the main function.
this gives the following output:
Enter any number:
0
The number must be greater than zero
Enter any number:
..... so on
|
|
|
|
|
You created an unneccessary and unhelpful recursion. If you do the same if the second value gets entered wrongly the user would have to also enter the first value again.
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
lol really... 
|
|
|
|
|
What happens when the user keeps entering invalid inputs and the stack runs out of space?
|
|
|
|
|
We all get sucked into a hell dimension?
This space for rent
|
|
|
|
|
Hell is other people's code 
|
|
|
|
|
lol this is a command line application.... the console will keep on scrolling down and never run out of space... the space is infinite.
|
|
|
|
|
Much to learn you still have, young padawan.
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
I wasn't talking about the console but the stack. The correct answer to my question was that you'll get a stack overflow exception and your app will terminate.
|
|
|
|
|
I hadn't realised that Console applications rewrote the laws of the stack. Dagnabit, from now on, all my applications are going to be console applications if that's all it takes to avoid stack issues.
This space for rent
|
|
|
|
|
Please do use braces (brackets). As a beginner you shouldn't yet "experiment" with omitting them.
Please do not use labels ("HOME:"). Labels only make sense with the keyword goto and you should never, ever use goto until you exactly understand why I write this and are able to identify the 0,00001% case where goto might be excusable.
I assume you haven't yet learned about creating and calling own methods (which would be the best solution to letting the user retry entering a value).
So here's a comparatively good-style snippet for allowing the user to re-enter a value greater than zero if he entered a wrong value the first time or repeatedly:
Console.WriteLine("Enter any number greater than 0: ");
string input = Console.ReadLine();
int value1;
while (!Int32.TryParse(input, out value1) || value1 <= 0)
{
Console.WriteLine("Invalid input. Enter any number greater than 0: ");
input = Console.ReadLine();
}
Sidenote: In C#, local identifiers should be declared where you first need them, not all at the top of a method.
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
Sascha Lefèvre wrote: you should never, ever use goto until you exactly understand why I write
 Gets my vote!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Sascha Lefèvre wrote: Sidenote: In C#, local identifiers should be declared where you first need them, not all at the top of a method.
I wonder where this habit comes from. I always declare vars at the top of the method.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I think it makes sense from a semantic point of view: You see a declaration and you know it's the first occurence of that identifier. It also saves some lines of code. Why do you prefer the top-declaration?
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
I think it may have come from the days when it was possible to declare a variable multiple times, VB5 allowed that and possibly 6, my milk languages. I think I have broken most of the old habits, annoying to realise some are still in use.
I do recall declaring and enum called Date with a value of 2, screwed up so many things.  It was a long time ago!
Never underestimate the power of human stupidity
RAH
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
