|
Try surrounding the detail section with a group section. Define grouping field based on in which case you want to have a new age and set NewPageAfter to true for the group footer
Hope this helps,
Mika
|
|
|
|
|
I may try that thanks Mika
Life - Dreams = Job
TheCardinal
CTC-RDG
|
|
|
|
|
Hi ,
I have created custom print dialog and included preview button in it.
I have used PrintPreviewDialog class to show the print preivew box and used my onPrintPage() evnt to process each page n print.
Problem is when i click on print settings button in print dialog and then if i go for Preview button , preview is done within a minute. But if i click the preview button without making any changes to page settings , it take nearly 5 mins to show a preview of 10 pages.
Please help to resolve the problem. I cudnt find how come print preview generates the page faster if i open and close the pagesettings dialog???
Thanks in advance..
Please reply as soon as possible!!!!!!!!!!!
|
|
|
|
|
i need to poll for a new hardware (Non Plug and Play device<</i>/b>) connected to the serial port, can anyone give me the sample code or any links..
please reply asap.. )
thanks and regards
skvs
|
|
|
|
|
Open the port and see if it responds...
|
|
|
|
|
okay, thank you..
|
|
|
|
|
i want to make a font in gdi+ .
which i can defiend the font's height and width .
in the .net ,it is imposiable to set a value to the font's height or width.
please help me !
from vevi
|
|
|
|
|
is anyone can help me?
from vevi
|
|
|
|
|
Dude, you need to have patience. If someone can help you, they will.
"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
"Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
|
|
|
|
|
He became impatient after only 20 minutes too..
Regards,
--Perspx
Don't trust a computer you can't throw out a window
-- Steve Wozniak
|
|
|
|
|
Perspx wrote: became impatient after only 20 minutes
More the reason to delay replying with real helpful stuff, too
"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
"Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
|
|
|
|
|
you can create cutome font using System.Graphics
I think there is a font and fontfamily class. Try to Googling you will get your answer.
|
|
|
|
|
please think about a little with the question .
if i use google can find the answer,i would not be ask it in here .
if you did't know please dont reply!!
from vevi
|
|
|
|
|
|
hi,
eyes and face detection can be done. so i was thinking
if anyone knoe how to do for nose and mouth detection?
thanks
|
|
|
|
|
You should search for some already done research on facial detection and look at some algo's best results wise.
then u will get your answer
|
|
|
|
|
It's an interesting problem. I'd consider this approach:
1. Use your existing algorithm to get the bounds of the face.
2. Replace each pixel with a number proportional to the variance in the neighborhood of that pixel. (There will be more variance in the regions of the eyes, mouth, and around the nose.)
3. Use the Open operation (Erode morphological operator followed by Dilate) to eliminate stray isolated pixels with high variance.
4. Use the Close operation (Dilate morphological operator followed by Erode) to fill in the gaps.
5. You should have four regions remaining: Two eyes, nose, and mouth.
(This is more interesting than what I'm working on now!)
|
|
|
|
|
I believe it is tradition/convention to organize source files in a project so each class is contained in one .cs source file. Correct?
I am writing several static utility classes with about 10-20 methods each. And each will have about four (4) overloaded methods so the static class definition (and the .cs source file) is getting pretty lengthy.
Should I keep to the one-class, one-source-file convention, or is there a better way to organize my project in the Solution Explorer?
|
|
|
|
|
you can try to chop it to small files and create a partial class
Life - Dreams = Job
TheCardinal
CTC-RDG
|
|
|
|
|
Yes, definitely a good idea to keep one class per file as good programming practice. Um... Tradition? No. We (those at my company) like to strictly adhere to this rule and leave the partial class definition to automatically generated code only. Actually using it is IMHO a bit unsavory to read but preferable to a single file mess. You can use the #region directive to collapse source code sections together for convenience.
Hope that helps
Scott P
“It is practically impossible to teach good programming to students that have had a prior exposure to BASIC: as potential programmers they are mentally mutilated beyond hope of regeneration.”
-Edsger Dijkstra
|
|
|
|
|
Partial classes are great for segregating related functionality into discrete files. For instance, I only put generated code into the main form file, and anything added manually into a separate file(s). For instane, all code related to a BackgroundWorker object would go into a separate file.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997 ----- "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
ssclaire wrote: I believe it is tradition/convention to organize source files in a project so each class is contained in one .cs source file. Correct?
It all depends.
I have files with one class and files with several classes and one class spread across multiple files. The key for me is to organize files in a logical, clear way. Having too many files can be as distracting and confusing as having few files with too much code in each.
Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke
|
|
|
|
|
Don't worry about the length until the file gets to around 1000 lines of code. After that, you could try to find logical places to separate the code, and create partial classes.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997 ----- "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
One class per source file is a good default convention, but a good programmer knows when to break the rules to improve clarity and simplicity.
For example, it may be more maintainable to combine a few related classes that are only used together in the same file. Ask yourself: "What organizational structure would *I* prefer to work on when maintaining this system?"
|
|
|
|
|
Thanks, folks. Good answers to my question.
|
|
|
|