Madcollection V2.5.8.0 For Delphi Bcb Incl Source-ssg
MadExcept is a great piece of work and using it has ironed out a number of bugs in our software.Thanks for the feedback!:-) I do though wish that you'd use a standard installer that let the user choose where to put the files rather than defaulting to (in my case) C:Program Files (x86)madCollectionThe installer does ask you for the target path. However, it only asksif madExcept isn't installed yet. Once you have it installed, theinstaller will afterwards only update to new versions and silentlyreuse the path you selected when you first installed madExcept.If you want to change the installation path, simply uninstallmadCollection completely and then install it again. The installershould then ask you again for the desired target path.-www.madshi.nethigh quality low level Delphi componentsextended exception handlingAPI hooking, DLL injection. In article, Mathias Rauen wrote: The installer does ask you for the target path. However, it only asks if madExcept isn't installed yet. Once you have it installed, the installer will afterwards only update to new versions and silently reuse the path you selected when you first installed madExcept.
If you want to change the installation path, simply uninstall madCollection completely and then install it again. The installer should then ask you again for the desired target path.Thanks for the explanation. IMO it would be better to ask every time,presenting the previous installation path as a default.-Tony Bryer, Greentram Software Pty Ltd, Melbourne, Australia'Software to build on' http://www.greentram.com.
IMO it would be better to ask every time, presenting the previous installation path as a default.It might be a matter of taste. But personally, I dislike updateprocedures which ask me all the little details another time which Ialready answered the first time I installed the product. So I made theinstaller behave the way I personally prefer it.Imagine you install XE6 Update Pack 1, and it asks you for theinstallation path? Would you actually be courageous enough to darechange the path there? Would you really trust the installer to not onlyinstall the new files in the new path, but to also move all theunchanged files and update all registry keys etc to reflect the pathchange? Personally, I would not trust any installer to do such a pathchange. I'd bet that at least half of the installers out there wouldscrew up such a path change.
The safer way should be to uninstall thesoftware from the old path and then reinstall it with a new path. Andthat's exactly how you can change the installation path with myinstaller, too.Just my personal opinion, of course.-www.madshi.nethigh quality low level Delphi componentsextended exception handlingAPI hooking, DLL injection. Mathias Rauen wrote: It might be a matter of taste.
Mad Collection V2.5.8.0 For Delphi Bcb Incl Source-ssg 2017
But personally, I dislike update procedures which ask me all the little details another time which I already answered the first time I installed the product. So I made the installer behave the way I personally prefer it.Nothing wrong with that, except that -IMO- it wouldn't hurt if there were asingle editbox showing where it will install (update) and a button to forfolder dialog to change it -if the user really wants to.This wouldn't -technically- asking the user anything and it would also serveto inform the user exatly where it is updating. The safer way should be to uninstall the software from the old path and then reinstall it with a new path. And that's exactly how you can change the installation path with my installer, too.I agree.
I have seen a number of apps that do exactly that when updating. Ithink VLC is one such app.But, is it so hard to start an uninstall routine (asking the user first, ofcourse) before upgrading (to another path)? In article, Mathias Rauen wrote: It might be a matter of taste. But personally, I dislike update procedures which ask me all the little details another time which I already answered the first time I installed the product. So I made the installer behave the way I personally prefer it.That's why we work for ourselves - no boss telling us to do it his way!-Tony Bryer, Greentram Software Pty Ltd, Melbourne, Australia'Software to build on' http://www.greentram.com. it wouldn't hurt if there were a single editbox showing where it will install (update)True.
Maybe I'll add that in a future version. and a button to for folder dialog to change it - if the user really wants to. is it so hard to start an uninstall routine (asking the user first, of course) before upgrading (to another path)?Supporting that would be possible, and not really allthat hard. But then, as with every potential newfeature / improvement I have to balance the potentialbenefit to the development time/cost.
And in this caseI think the benefit is too small to be worth the effort.In all the 14 years of madExcept nobody has ever askedme how to change the installation path. Tony was thefirst one. My general rule of thumb is that I usuallydecline feature requests I'm not convinced about myself,unless I get the same feature request at least 2-3times from different users on different occasions.-www.madshi.nethigh quality low level Delphi componentsextended exception handlingAPI hooking, DLL injection. On 2014-05-14 17:49:51 +0000, Mathias Rauen said: It might be a matter of taste. But personally, I dislike update procedures which ask me all the little details another time which I already answered the first time I installed the product. So I made the installer behave the way I personally prefer it.I prefer that upgrades work as you've described as well.When an upgrade asks me where to install it (even showing an existinginstall path), it makes me wonder if I'm actually upgrading an existinginstall (which is what I want), or installing the new version inaddition to and separately from an existing version - Not usually whatI want.i.e. If it's an upgrade, just upgrade without asking me anything.
If Iwant to do a fresh install, I can uninstall the existing version first.I also find it confusing when an upgrades gives you the path and folderof an existing installation, then warns you about the chosen folder notbeing empty. Such warnings often force me to completely uninstall theprevious version, unless the install instructions indicate that suchaction is not necessary.-Kevin Powick.
I do though wish that you'd use a standard installer that let the user choose where to put the files rather than defaulting to (in my case) C:Program Files (x86)madCollection The installer does ask you for the target path. However, it only asks if madExcept isn't installed yet. Once you have it installed, the installer will afterwards only update to new versions and silently reuse the path you selected when you first installed madExcept.
If you want to change the installation path, simply uninstall madCollection completely and then install it again. The installer should then ask you again for the desired target path.My main gripe with the installer is that it's slightly confusing as to what isselected and what isn't. Does white indicate selected or black? You can switch the installer into simpleextraction mode by using one of the followingtwo methods:(1) Press and hold 'Ctrl' while the installeris starting. When the component selectionform appears, you can release the key.
Nowthe installer will ask for a path to extractto and do nothing but extract.(2) The following command line parametersare supported:-extractOnly-path=.-silentUsing just '-extractOnly' has the same effectas pressing 'Ctrl'.-www.madshi.nethigh quality low level Delphi componentsextended exception handlingAPI hooking, DLL injection. Hi there,here's a beta build with XE7 support:(installer 2.7.9.6)A new official release should be coming at the end of thisweek or at the beginning of next week. The current betashould already be stable enough for your release software,though.Best regards, Mathias.-www.madshi.nethigh quality low level Delphi componentsextended exception handlingAPI hooking, DLL injectionHi Mathiasgreat info. Thank you very much!My pleasure!Unfortunately there was some debug code left in thebeta build which stopped.ESB Consultancy. is pleased to announce the latest release of our huge collection of components and routines that aim to make Data Entry and Manipulation easier for the Developer and their Customers.for VCL v6.4.0. adds support for.Delphi XE6. (and.C Builder XE6.) as well as includes improvements to our ComboBox (optional variable widths added to drop downs), more measurement conversions, etc.This is a free upgrade for existing customers.
The 'subsets' have also been updated -.ESBPCS-Lite for VCL.,.ESBPCS-Calcs for VCL.,.ESB.We are glad to announce Localizer 4.0.0 release.Localizer is a localization/globalization tool kit for applications written in CodeGear (Borland) Delphi or C Builder. Using it you can get one executable file that supports as many languages as you want.Localizer can process all string resources in your project: properties of components on forms, resource string constants, VCL messages and messages from third-party packages.
You can also change size and position of the controls in different languages.Support fo additional language(s) can be added without recompilation of the projec.We are switching over to 32 bit environment. With 16 bit I can use Wisqland Sqledit without any problems. With 32 bit I can use Wisql32 ok but Ican not ping with Sqledits as the ping option is greyed out. Does anyonehave and suggestions?Thanks in advance,Paul.We are switching over to 32 bit environment. With 16 bit I can use Wisqland Sqledit without any problems. With 32 bit I can use Wisql32 ok but Ican not ping with Sqledit as the ping option is greyed out.
Does anyonehave and suggestions?Thanks in advance,PaulHP Authorized Customer wrote: We are switching over to 32 bit environment. With 16 bit I can use Wisql and Sqledit without any problems. With 32 bit I can use Wisql32 ok but I can not ping with Sqledit as the ping option is greyed out.