|
Hi!
Not quite sure what you mean by "Binary/Byte" - every file (no matter if it is a jpg or a doc or something else) is just a bunch of bytes in a certain order.
The only meaning implied on this stream of bytes is the one given by applications that can interprete the data in a given way.
When you try to load a .doc file into your favourite image processor (probably having to rename the file to do so), it'll choke on the data because it cannot be interpreted as an image.
Anyway, you can read any file into a byte array using classes from the System.IO namespace and then get a base64 string from this array using Convert.ToBase64String().
This base64 string is something you can write to a text file (i.e. a file with all of its bytes in the limited range of printable characters).
The way back is straightforward: Read the base64 string from the text file, convert it to a byte[] with Convert.FromBase64String() and write the array to a binary file.
Regards,
mav
--
Black holes are the places where God divided by 0...
|
|
|
|
|
Thanks for the reply.
I meant about the Byte/Binary is the Byte data type.
What I want is to convert a FILE to Byte, meaning instantiate the Byte data type with the contents of the File. Like:
Byte[] ByteArray = [Byte_of_File] //Is this even possible O_o?
I want it this way because I want to do some modifications on the Byte_of_File itself and after some modifications, I want to write it as a text file. (Filestream?)
After that, I want to reverse the process by reading the text file(Filestream), saving the contents of the text file to a ByteArray, undoing the modifications, and export them back as a workable file.
Am I talking junk or is this possible?
Thank You
|
|
|
|
|
Ian Uy wrote: Am I talking junk
Yes
|
|
|
|
|
Ouch.
But Sir, is this possible to do even it its "junk"?
Thanks.
|
|
|
|
|
You can READ bytes from a file. There's no conversion.
Simply use "byte[] byteArray = System.IO.File.ReadAllBytes(fileName);".
|
|
|
|
|
Thanks for the reply.
How can I do the reverse proccess? I mean, from byte to file. Thanks.
|
|
|
|
|
Perhaps there is a method with a name that is the opposite of Read. Write perhaps?
|
|
|
|
|
Ian Uy wrote: I am wondering if there is a way to convert a certain file(.EXE,.JPG) to Binary/Byte
The files are already binary data. All files are always binary data, even text files are binary data. It's only when you read a text file as text that it becomes text, otherwise it's only bytes.
Reading a file is quite easy:
byte[] data = File.ReadAllBytes(@"c:\test.jpg");
Ian Uy wrote: For example, I have a certain Picture.jpg. I want to convert it to binary/Byte, and save it as a TEXT FILE.
You can't save binary data as text. If you want the binary data as text, you have to convert it, for example using base 64:
string dataText = Convert.ToBase64String(data);
Each character (which is a 16 bit unicode character) now contains 6 bits of information. Now you can save the string as a text file.
(Note that the text will be encoded to binary format (usually using utf-8 encoding) when saved as a file, as files always are binary.)
When you have read back the text file as a string, you can convert it back to the original data:
byte[] data = Convert.FromBase64String(dataText);
---
single minded; short sighted; long gone;
|
|
|
|
|
Thank you for the reply Sir Guffa.
Now that I have the data back to byte array. By using this:
byte[] data = Convert.FromBase64String(dataText);
How can I turn it back to c:\test.jpg
Thank you again. 
|
|
|
|
|
Take a look at the File.WriteAllBytes method.
---
single minded; short sighted; long gone;
|
|
|
|
|
I have written a report to print labels which works quite well as long as a full sheet is to be printed. Unfortunately in the real world people rarely print full sheets of labels. Instead they need to be able to specify a column and row to begin printing.
The label report is actually a horizontal report that prints three rows then moves to the next column prints three rows and so on. The names and addresses are pulled from a SQL Server 2005 database.
Is there a way to send printer codes to the printer to position the print head before printing begins?
I've even thought about using dummy records to get the printer to skip to the right record, but I'm not sure how to do that or if it would even work.
Any suggestions are appreciated.
|
|
|
|
|
Roger CS wrote: Any suggestions are appreciated.
I suggest you do some reading about how to do printing[^]
|
|
|
|
|
Anyone here who actually knows how to do what I'm asking about?
|
|
|
|
|
Your description isn't very clear, so I'm guessing at it too. How about this[^].
|
|
|
|
|
Dave Kreskowiak wrote: Your description isn't very clear
I’ll try to be clearer. I am printing mailing labels. The sheet of labels has 3 columns and 10 rows (for a total of 30 labels). Normally people don't need to print exactly 30 labels or multiples of 30. Instead they may need to print 10, then later 6 more and so on. If the user starts with a fresh sheet and prints 10 labels, there will be 20 labels remaining. The next time the user prints labels they need to start printing at label 11. For this reason, the program allows the user a way to enter the row and column at which to start printing labels. In this case the user would enter row = 4 and column = 2.
I want to know how to start printing labels at row 4, column 2.
The information in the labels is pulled from a SQL Server 2005 database using a select query.
Thanks for the pointer to the KB article!
Roger
-- modified at 17:35 Saturday 13th October, 2007
|
|
|
|
|
led mike wrote: I suggest you do some reading about how to do printing
Yup, you were right. Everything I needed to know was there... I just had to extend PrintDocument and add some functionality.
Thanks,
Roger
|
|
|
|
|
Roger CS wrote: Thanks
See I did actually now something about it 
Seriously though, one can never go wrong reading documentation. Even if it does not present your immediate solution you still gain knowledge.
|
|
|
|
|
How are you printing the labels now? Direct sending ESC keys to printer or using print document?
|
|
|
|
|
I wrote a report. I was just printing the report. I hadn't gotten any further than that when I posted this question. What I have learned since then is that I can print lables using the PrintDocument class. I just need to extend the functionality to meet my requirements.
|
|
|
|
|
HI,
I made a Form.
When a button is clicked, the main thread starts a timer and does some heavy tasks. When the tasks are finished, the main thread stops the timer.
What the timer does is just to update a textbox (like a progress bar to indicate the progress of the main thread). But the textbox is NOT updated until the main thread finishes its tasks (a pop-up dialog is shown and the main thread waits for a button-click in the dialog).
Would anyone help please?
Thanks!
|
|
|
|
|
|
Hi!
What you describe is just the way it is. The main thread is the only one responsible for updating the UI, i.e. triggering the controls to paint themselves.
Then the main thread is busy doing other things, the controls are not repainted.
When you write that you use a timer, then this information is not enough. There are at least 3 different timers I know of in the BCL, one doing its work on the main thread (System.Windows.Forms.Timer) and the other two working on separate threads (for example, System.Timers.Timer).
If you say that your UI isn't responsive while the timer is running, I guess you're using the first one.
The solution for this kind of problem is to let the "heavy task" run in a separate thread, thus freeing the main thread for updating the UI.
But beware - you cannot update your UI from a different thread than the main UI thread directly. You'll have to use Invoke() or BeginInvoke() for this.
Regards,
mav
--
Black holes are the places where God divided by 0...
|
|
|
|
|
Yes, I am using the Form's timer.
Thanks a lot for your help!
|
|
|
|
|
Hi all,
I have several methods, with many different signatures, that I would like to allow the user to cancel in the middle of their operation. This wouldn't be a backgroundworker situation, however---these are methods in my library that are called synchronously from a certain thread, and need to operate synchronously (i.e., the calling thread should be waiting on them to finish), then canceled from the UI thread. Also, since these methods by default operate just by a method call, and not any other invocation, I don't want to make them all conform to the backgroundworker's dowork event handler signature.
So, is there some kind of built-in way to do this, perhaps with an attribute? How would the method check that it's time to cancel? How can I specify, preferably at compile time of course, that only methods x, y, and z can be canceled?
Otherwise, my solution is as follows:
- If you want to call the method normally (without canceling capabilities), just call it.
- If you want to call a method in a cancelable fashion, call
object Controller.PerformOngoingOperation(method, string id, params object[] args); another thread can later call Controller.CancelOngoingOperation(string id).PerformOngoingOperation checks that the method passed (more on that later) has the appropriate OngoingOperationAttribute; if so, it invokes it. It also stores in an internal dictionary a map from ids to boolean "should cancel now" variables.- The method in question finds its ID. This is kludgy... it involves reflections to find the calling method, check if the calling method is
PerformOngoingOperation, and if so, ready the id parameter. - It then uses this id to performs a series of checks throughout its operation against that
internal map from ids to "should cancel now"; if at any point the should-cancel bit is true, it finishes what it's doing and returns. - Then,
PerformOngoingOperation will return the results of the method, whether canceled prematurely or not. So it acts just like invoking the method (good for users!), but can allow cancellation. - The should-cancel bit is set by
Control.CancelOngoingOperation(string id), with consequences as above.
IF the above approach is reasonable---and it's very nice from a user's perspective, except for the upcoming detail---then I have a question. How should I pass the method to PerformOngoingOperation? Is there any way to do so without awkwardness? What I mean is that, as far as I can tell, I want to use a delegate. This necessitates that the user of my library declare a new delegate type for every method he wants to call in a cancelable fashion! And he can't even declare delegate types locally; he has to pollute his class with them. Like this:
class C
{
delegate int annoying(int param1, bool param2, string param3);
void Method()
{
string id;
int retVal = (int)Control.PerformOngoingOperation(new annoying(Library.Object.Method), out id, param1, param2, param3);
}
}
I suppose an alternative is requiring that the delegate be of type MethodInvoker (basically void return type, no parameters), and forcing the user to do this:
int retVal;
string id = Control.PerformOngoingOperation((MethodInvoker)(new delegate() { retVal = Library.Object.Method(param1, param2, param3); }));
But that's awkward at best.
Ideally I would like to have something like this instead:
string id;
int retVal = Control.PerformOngoingOperation(Library.Object.Method, out id, param1, param2, param3);
Is that possible?
-Domenic Denicola- [CPUA 0x1337]
“I was born human. But this was an accident of fate—a condition merely of time and place. I believe it's something we have the power to change…”
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
