New version
#1When will we have the new version? The other IntelliCAD "maker" has just released his package?
#2
Our policy for update versions is to not release the product until we have had time to look it over and also to pass it on to our moderators for their review also. We hope to have it available for download in 7 – 10 days, possibly sooner if everything seems to be testing out alright. I apologize for the delay but we feel it is in the best interest of our customers.
Melodie
Melodie
#3
It sounds like the *other* cad distributor is having problems such as:
Xref:reload etc
Snaps, fly over +
Selection box not behaving.
This is disturbing since the xref issue is new, icad 2k did not exhibit this sort of behavior.
Plz keep us updated, I for one trust your distro more than the *other*.
thx.
b
Xref:reload etc
Snaps, fly over +
Selection box not behaving.
This is disturbing since the xref issue is new, icad 2k did not exhibit this sort of behavior.
Plz keep us updated, I for one trust your distro more than the *other*.
thx.
b
#4
Thank you for understanding our position, it is nice to know we have your support. I just had a call from Corporate Headquarters and was informed that the ITC is still working on the program and has fixed several problems over the last two days. We have asked them to notify us when the program is ready to be released and then after a short evaluation period, for our moderators and myself, we will announce the update on this forum.
Again .. Thank you,
Melodie
Again .. Thank you,
Melodie
#6
Hello J.,
I very much appreciate your offer to help test but as the owner is out of town right now I am not in a position to give you an answer at this moment. I do apologize, but this is not my call. Currently we only have moderators and tech support beta testing, which will only last for 1-2 days. I will bring this up at my next meeting, which will take place any day now, and if there is any others allowed to be included you will be the first one I contact. Please be aware that in some cases the version you test may be more troublesome than the one you were previously using. I believe the gentleman at the Cadopia’s forum has just recently posted about why this happens. This would be a risk you would have to assume to beta test. Should be able to pinpoint a better time frame within the next day or two but I am hoping to have an updated version out in less than 7 days.
Melodie
I very much appreciate your offer to help test but as the owner is out of town right now I am not in a position to give you an answer at this moment. I do apologize, but this is not my call. Currently we only have moderators and tech support beta testing, which will only last for 1-2 days. I will bring this up at my next meeting, which will take place any day now, and if there is any others allowed to be included you will be the first one I contact. Please be aware that in some cases the version you test may be more troublesome than the one you were previously using. I believe the gentleman at the Cadopia’s forum has just recently posted about why this happens. This would be a risk you would have to assume to beta test. Should be able to pinpoint a better time frame within the next day or two but I am hoping to have an updated version out in less than 7 days.
Melodie
#8
Melodie,
Are the below paragraphs true? have you heard anything to this effect? Im glad to hear that this is taking place, even if it is a bit overdue. It was my understanding that this was the underlying purpose of creating the ITC. Please provide some clarification and information.
Thank you,
Braan
A most frustrating and bewildering phenomena seems to be repeating
itself with each development cycle; namely, the fixing of some bugs
creates new ones. Why does this happen? Is there no way of preventing
it?
ITC consists of many members (about 5,000 or so non-commercial and 50 or so commercial). Each member can submit changes. Until now, there were no checks to see if a check in broke somebody else's fix. The complex linetype bug is a case in point. We have the fix ready, just that it conflicts with one of the changes Bricsnet has put in so we had to back out the fix.
The good news is that after learning about the details of the old process recently, we have put a new process in place that will fix such problems in future. The results of these changes, as I mentioned before, will start appearing in September. BTW, we now require as part of the ITC membership agreement that a SINGLE code source to be used by all ITC members. The penalities are much more severe for not checking in code and claiming that my version is better than yours...
Yes, I have just been elected President of the ITC in July. You will see consistent version names, numbers, copyright messages, and other good changes (3rd party applications support) in the coming months.
--Surya
Are the below paragraphs true? have you heard anything to this effect? Im glad to hear that this is taking place, even if it is a bit overdue. It was my understanding that this was the underlying purpose of creating the ITC. Please provide some clarification and information.
Thank you,
Braan
A most frustrating and bewildering phenomena seems to be repeating
itself with each development cycle; namely, the fixing of some bugs
creates new ones. Why does this happen? Is there no way of preventing
it?
ITC consists of many members (about 5,000 or so non-commercial and 50 or so commercial). Each member can submit changes. Until now, there were no checks to see if a check in broke somebody else's fix. The complex linetype bug is a case in point. We have the fix ready, just that it conflicts with one of the changes Bricsnet has put in so we had to back out the fix.
The good news is that after learning about the details of the old process recently, we have put a new process in place that will fix such problems in future. The results of these changes, as I mentioned before, will start appearing in September. BTW, we now require as part of the ITC membership agreement that a SINGLE code source to be used by all ITC members. The penalities are much more severe for not checking in code and claiming that my version is better than yours...
Yes, I have just been elected President of the ITC in July. You will see consistent version names, numbers, copyright messages, and other good changes (3rd party applications support) in the coming months.
--Surya
#10
Hello Braan,
This was the post that I was referring to earlier. It is a good explanation on why there have been instances that the newer releases can sometimes cause more problems than the older versions or sometimes they seem to fix certain bugs but others pop up. While my expertise does not include programming I find Mr. Sarda’s explanation makes perfect sense. In a perfect world all fixes would work in harmony but that is currently not the case.
My understanding on the process is that the ITC has always taken all the fixes that were submitted and included them in the source code that goes back out to the members. Our company in turn compiles the program and include the add-ons such as VBA and Image Enabler that make up our different packages while including our version numbers and various things that pertain to our individual company (logo’s and opening graphics come to mind.) We than perform a short testing period before releasing it to our customers. It is during this testing period that some of the conflicts arise that were not known before.
The change in the way that the fixes will be handled reflect the positive growth in the ITC and I for one am very happy to hear that they have came up with a solution to this problem as it is a shame that such things as Mr. Sarda’s complex linetype fix should have to be left out because of conflicts with others. The ITC has done a tremendous job of bringing this program together for all to share since the beginning and is growing stronger every step of the way along with the IntelliCAD program. I have only been involved with IntelliCAD for a short period of time but am very impressed with the changes that have already been made. If the people that feel negatively about the program would only look back and see all the improvements and fixes that have come to past they may then realize that at this rate it will not be long before the bugs will be few and far between.
Yes, I have heard that there will be another release in September - October. The release that is currently coming to past was mainly to correct the conflicts that were arising from bringing in new features, again because of what is stated above. When I receive more information on this I will post a message on this forum.
I am very glad to hear that the penalties for not sharing code have been increased. The ITC evolved from this concept of sharing code among members and it has always been their intention to publish one single code that was in turn to be used by all. No one commercial member was to have something more or better than the other. I commend them on becoming stricter on this policy.
I hope I have answered any questions that you have had. As I stated before, I am not a programmer so my knowledge of bringing together all the different fixes is limited. Thought I would start out with VBA so I have been following along with the new tutorials that John is graciously supplying us, I think they are fantastic.
I would also like to take the opportunity to thank Mr. Sarda for so clearly explaining the situation and also to congratulate him on being elected as President of the ITC Board.
Melodie
This was the post that I was referring to earlier. It is a good explanation on why there have been instances that the newer releases can sometimes cause more problems than the older versions or sometimes they seem to fix certain bugs but others pop up. While my expertise does not include programming I find Mr. Sarda’s explanation makes perfect sense. In a perfect world all fixes would work in harmony but that is currently not the case.
My understanding on the process is that the ITC has always taken all the fixes that were submitted and included them in the source code that goes back out to the members. Our company in turn compiles the program and include the add-ons such as VBA and Image Enabler that make up our different packages while including our version numbers and various things that pertain to our individual company (logo’s and opening graphics come to mind.) We than perform a short testing period before releasing it to our customers. It is during this testing period that some of the conflicts arise that were not known before.
The change in the way that the fixes will be handled reflect the positive growth in the ITC and I for one am very happy to hear that they have came up with a solution to this problem as it is a shame that such things as Mr. Sarda’s complex linetype fix should have to be left out because of conflicts with others. The ITC has done a tremendous job of bringing this program together for all to share since the beginning and is growing stronger every step of the way along with the IntelliCAD program. I have only been involved with IntelliCAD for a short period of time but am very impressed with the changes that have already been made. If the people that feel negatively about the program would only look back and see all the improvements and fixes that have come to past they may then realize that at this rate it will not be long before the bugs will be few and far between.
Yes, I have heard that there will be another release in September - October. The release that is currently coming to past was mainly to correct the conflicts that were arising from bringing in new features, again because of what is stated above. When I receive more information on this I will post a message on this forum.
I am very glad to hear that the penalties for not sharing code have been increased. The ITC evolved from this concept of sharing code among members and it has always been their intention to publish one single code that was in turn to be used by all. No one commercial member was to have something more or better than the other. I commend them on becoming stricter on this policy.
I hope I have answered any questions that you have had. As I stated before, I am not a programmer so my knowledge of bringing together all the different fixes is limited. Thought I would start out with VBA so I have been following along with the new tutorials that John is graciously supplying us, I think they are fantastic.
I would also like to take the opportunity to thank Mr. Sarda for so clearly explaining the situation and also to congratulate him on being elected as President of the ITC Board.
Melodie