For now you can still navigate to C# filter[^], that is until they remove it. I don't really understand why they removed the ability to filter by language, this was one of the best features on the site if you ask me. :omg: :omg: :omg:
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
I have to disagree with you here; vote rigging has been around, since the dawn of democracy, so saying that voting needs to be democratic, doesn't mean you don't have to prevent vote rigging. And as CodeProjects voting system describes it, it to has it's counter measures to handle bad votes, and you also posted that high rep members have more saying than low rep members, so why not say, you can't vote untill "you're 18 year old" AKA "one week old member", that to, would be a good counter measure to handle vote rigging AKA "sign-up and vote, and never hear from that member again". Just saying... ;)
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
True, but still, it would help the voting system, since this would remove the "in effect" votings of an author, that want to promote his or hers article, with an fake account.
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
Newly created accounts should not be able to vote for an article.!! I often see (or guess/have suspicion) that authors, creates accounts to up vote their own articles. couldn't we make it so that, newly created accounts can't vote, untill they are an week old or something ?:confused: When I say this, its because I see some articles that are not fit for an 5 stars, but still gets it from 1 or more users that were created the same date as the article... :^) :^)
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
Same here :doh: :doh: :doh: :doh: :doh:
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
The Picturebox I believe.
PictureBox pictureBox1 = new PictureBo();
pictureBox1.Image = System.Drawing.Image.FromFile(@"");
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
Some info to search for him, couldn't find him on CP :mad: Following IDs Google plus ID: 113305855818953113069 Facebook ID: ErHardikChauhan
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
I have NO issue downloading from the site... must be on your side og the cable :( :doh:
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
I have suggestion. like when we recieve an email notification about an member posting something in the Comments and Discussions in one of our articles, it would be nice to have that in the topbar as well. A bit like facebook notification about replies a.s.o.
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
Thanks I will let him know this, lets see if it works ;) Thanks for the reply
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
I have a colleague, that has a bit of trouble creating a UDF heres there code but it fails:
CREATE FUNCTION GetData(@Param int)
RETURNS TABLE
AS
RETURN
IF @Param = 1
SELECT * FROM Emp
ELSE
SELECT * FROM Offices
END
The function shall return different table based oppon the condition of the @Param value. Can someone help ???
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
Ohh and by the way its your background collection that has to change, and when it does, just reset the Virtual item count on the listview, then it will reload, all visible items (from index, to index) from the background collection. ;)
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
Yes and No, Virtual mode is definitely for log events, Its the fastest way of getting data out on the GUI. Just force the listview to reload the single Item when it changes ;) But that might takes some Native calls ;)
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
Have you checked the innerException of the Exception('Exception has been thrown by the target of an invocation') ??? whats it saying ???
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
Didnt see m8, sry ;)
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
Virtual mode is very easy to use and code... just look at the guidline i gave you from microsoft, it shows you the way. But u need to know that virtual mode has its limits, with what it can do, compared to normal mode. ;)
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
Thats Easy. just use the listview in virtual mode m8 ;) I have some listviews with over a million entries, and my app dont freeze at all. ;) Just remember to use cached items that also ups the preformance ;) Heres the guideline from MSDN http://msdn.microsoft.com/en-us/library/system.windows.forms.listview.virtualmode.aspx[^] Happy codeing
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
Have you considered using the ProcessCmdKey overload or event ??? instead of keypress event
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
Always use System.Runtime.InteropServices.Marshal.SizeOf method to ensure platform independency.
With great code, comes great complexity, so keep it simple stupid...:-\ :-\
Its not that simple. please provide an sample code from where you get the error. else im unable to help you.
With great code, comes great complexity, so keep it simple stupid...:-\ :-\