Not really... because none of us have a clue what you're talking about. What is it? In plain English.Quote:
Can we get back to the OP, in which I am trying to work towards???
Printable View
Not really... because none of us have a clue what you're talking about. What is it? In plain English.Quote:
Can we get back to the OP, in which I am trying to work towards???
It looks like you're making an ActiveX control. Are you trying to pass it off as a new language?
Everyone reading this thread is puzzled.
In case you're competing with the AI thread, you're far from getting there.
moti's a seasoned troll and you've nothing on him.
There aren't too many threads that require me to take an asprin after reading, but this was sure one of them...
--That makes two or more of us...
However it was an ActiveX Control but then I just rewrote to a Form, instead and then working from there. Also I wrote it into my IDE, and then working as an Express and Ultimate Editions of it, at the same time. Is this really neccessary, to do or not???
Actually why not download following the link in my signature: "QuickDirector Express" in the section under: "QuickDirector Stuff"...
-- Thanks for the Input$, I am going to check it out right about now!!
The Link is now Refreshed, Relinked and then it works right about now, in deed. That was a few very intense moments, working out what was wrong. I had a space in the link feeder on the Forum Signature!! I didn't realise that, part of the fact...
-- hehe := Same here ,, at least my machine didn't blow up this time. Only joking...
Posting in an epic thread :bigyello:
-- hehe ,, yes it really is, isn't it???
Oh yeah !
-- So right about now. Getting back to the OP...
Has anyone been able to download my products and if they work, please tell me if they do so. If they don't work, please tell me and then I will then be able to get on to it right, at some point in time...
Well seeing that this is inside the General ChitChat Forum, I am going to ask: Does anyone Like or Dislike my Member Signature on this Forum??? I have been able to remove all of the Compiled Coded Internet Links, therefore it is now totally safe for people to use also there is a compiled section of the Webpage. But then I cannot let loose all of my Source Code, then. But that is my way of thinking, anyway...
I tried going to your main page which worked but doesn't contain anything useful except the links at the top. Unfortunately, every link returns a 404 page not found error so there's not much to look at at the moment.
I like your website, but I think each page should have music when it loads. That will make it even better.
Thanks
-- Actually, I'm working on a Splash Screen for when it loads the screen, so then that could be where I add the music, cool!! Thanks for the Input$...
Unfortunately thismeans I'm not going to try out your stuff. Don't get me wrong, I can see loads of perfectly good reasons why people don't like to share their code (the obvious one being that you don't want anyone to steal it) but the flip side for people like me is that you're essentially asking me to install something on my machine with absolutely no way of knowing it's safe to do so. It could be anything. I've got all sorts of stuff on my machine I can't afford to lose so the risk's just too great, even if I trust you.Quote:
CodeBank Page: Coming Really Soon...
If you can find a way of providing that assurance without exposing your code I'd be happy to try stuff out. I can't think of a way of providing that assurance without seeing the code though.
Debug the EXE file, with an External Debugger but then you have to run it on some kind of machine...
Here is some of Source Code, it's the CodeWindow Form and also the MSDN Library. Also included is the MSDN Documents that appear inside the MSDN Console...
-- Please note: When I say Source Code and MSDN Library, I am refering to the one that I am going to GIVE to Microsoft...
I suppose I'm late to the party, but this "new VB" that you were referring to... I think it came out already. It's called "VB.NET" and it's been around for... only 10 years now, I think?
Anyway, subscribed!
Damn, I've no longer got VB6 installed and can't find my old disk. I could have sworn I still had it. Anyway, I downloaded your stuff and opened it up in notepad (boy that took me back) and I think I can start to understand what you're trying to do.
Essentially, you seem to be writing an alternative IDE that's got some extra features in, so it'll create place holders for subs automatically and it's got some winsock connecivity built in, that sort of thing. Is that right? If so I applaud the effort but I do think you're going the hard way about it. You've got an awful lot of code there that just mimics stuff that was built into Visual Studio already, the code colouration for example. That's alot of effort when you could have just written add ins for Visual Studio, getting all of it's functionality for free while adding your own features on top.
If you're open to some criticism on your coding style, two things jumped out at me. 1. Alot of your variable are declared at form level when they're only used within a single method. You should always declare variables at the lowest scope possible. 2. You've got at least one 'On Error Resume Next' in there. Get rid of it and handle your errors properly.
NNNNNNNNnnnnnnnnnnooooooooooooooooooo!!!!! :p
It's not absorbing an error; it's absorbing all errors. Don't get me wrong, I can see the argument for absorbing the occasional error you genuinely know you can ignore but you ought to know what the error is first. Absorbing a "File Not Open" Error when closing a file would be a good example. But On Error Resume Next is saying, I don't care what error occurs, I'm going to ignore it. The very least you should do in VB6 is use On Error Goto, check the error code and issue a resume next from the error handler if it's an error you really don't care about.
And just 'cause I can't resist it:-
There was an On Error Resume Next
Which made some developers quite vexed
Shaggy's not bothered
but the errors hovered
and came back to haunt Funky Dext...
... er
While hiding all errors in a go
Causes trouble and hides bugs also
The point of my text
Which was missed by vexed Dex
Was: Only hide those exceptions you know.
I can only think of one situation where quietly swallowing an exception made sense, but there IS that one situation: Exceptions raised by invalid UDP packets can typically be ignored.
God this is such an epic thread :bigyello:
Well, you could do an inline error handling for the errors you expected, where the On Error Resume Next would be a perfectly justified way of handing errors. It's like executing a statement and then checking the error code or status code on the next line to check if the last statement executed without errors.
Sorry to post something serious. I am not entirely sure it's right to do that.
.
I know absolutely nothing about that so can't really comment. Let me see if I can clarify where I'm coming from a bit because I'm not sure whether we're arguing the same point or not. I'll probably get the syntax wrong so bear with me.Quote:
Exceptions raised by invalid UDP packets can typically be ignored
This is obviously wrong:-
That's just turning error handling off. I imagine we're probaly in agreement on that though.Code:'Program starts Here
On Error Resume Next
...
'Loads of lines of code
This isn't as wrong but I would argue is still bad practice:-
I used to come across that alot in my VB6 days but I still think it's bad because you don't actually know that the error being thrown is that the file is already closed. The error could be something completely different and this will carry on regardless. I guess there may be some situations where a particular line of code can only throw one type of error and you're happy to ignore it, but even then you don't know the underlying implementation won't change at some point.Code:...
On Error Goto MyHandler
'Various bits of code I'm handling correctly
...
On Error Resume Next 'Skip any errors because I don't care if the files already closed
File.Close
On Error Goto MyHandler
'More bit of code I'm handling correctly.
I would argue that this is correct:0
Here you're making sure the error is the one you want to consume before you consume it. Having a separate handler may or may not be apropriate, depending on the situation, but the point is to check the error first and make sure it's the one you think it is.Code:On Error goto MyGeneralHandler
...Various Lines of code being correctly handled
On Error goto myFileCloseHandler
File.Close
On Error goto MyGeneralHandler
... more lines of code being correctly handled
MyFileCloseHandler:
If Error.code = "File Already Closed" 'Or whatever the error code for that was
Resume Next
MyGeneralHandler:
'Do whatever error handling you'd normally do here
I've seen that argued a lot and disagree I'm afraid. It means your just ignoring any error you weren't expecting... and they're the really dangerous ones. I guess you could check for any error after every line of code but that seems awefully innefficient to me.Quote:
Well, you could do an inline error handling for the errors you expected, where the On Error Resume Next would be a perfectly justified way of handing errors.
The Shaggy v Funky Rhyme Battle
Played out 'fore the VBF cattle
The puns were displaced
by formed rhymes in their place
But I aint got a final line that'll...
...scan correctly
Turns out I'm not very good at limericks. And I don't really think the VBFers are cattle but, hey, you try coming up with a rhyme for battle just after you've eaten lunch.
I'm in agreement with FD on this... I've seen cases were apps failed in a spectacular way because at the top was (correctly) the On Error Goto errHnadlerXYZ .... then in the middle of the routing someone snuck in an OERN ... to handle a specific event, then FAILED to reset the original error handler. Things became even more complicated as we're going through the error handler to find out what was going wrong, not knowing there was an OERN... it was justbad juju all around.
-tg
In general, I too, agree on all those points. My position is this:
1) I know of one or two situations where that would be ok.
2) I didn't download the code in question, nor do I have the means to look at it, so I'm not going to.
Considering that #2 is True, I can't categorically state whether the practice in this case is wrong. However, this part is certainly true:
3) I can probably find a nit to pick with just about anything.
As #3 is clearly true, I think I shall say no more about it other that this: It is a very rare situation where it is acceptable to quietly swallow an exception, but they do exist. Try as I might to find an errant situation where it would make sense to Catch as exception...End Try.
Funky D called VB folks Cattle
He thought it to be idle prattle
It was not his end
To people, offend
So on him, I clearly won't tattle.
I'm willing to bet that's a particular problem by the end of a hiking trip.Quote:
I can probably find a nit to pick with just about anything.
Show off:)Quote:
Funky D called VB folks Cattle
He thought it to be idle prattle
It was not his end
To people, offend
So on him, I clearly won't tattle.
Gee sorry that I fell asleep, because of the members posting on my Thread!! This is the first night's sleep for about since Feburary '12!! I now usually sleep in the day time, not at night because of the time thing on this Forum...