int method ( int integer )
{
return ( 42 );
}
int method ( string trigger )
{
return ( method ( Int32.Parse ( trigger ) ) );
}
Gus Gustafson
int method ( int integer )
{
return ( 42 );
}
int method ( string trigger )
{
return ( method ( Int32.Parse ( trigger ) ) );
}
Gus Gustafson
How do you change the date?
Gus Gustafson
A citation would be helpful.
Gus Gustafson
As many of the responders to this post seem to have concentrated on fault and blame, let me state that the primary intent of the proposed organization is the preservation of the benefits of its members. For many of us in this profession, we are journeymen - we move from job to job; not necessarily for higher salaries, but rather because the current job is finished and we seek new challenges. I have held many positions over the 60 years of my career. Unfortunately, at each move, I lose the benefits that I acquired during my tenure in the job I am leaving. I have lost vacation days, sick days, and retirement benefits. Although the challenges of the new job were worth the loss of benefits, during a career the loss is appreciable. The proposed organization would compensate for that loss.
Gus Gustafson
Fallingwater? :)
Gus Gustafson
I firmly believe that programmers should be held accountable for their mistakes (witness the Boeing 737 Max disasters). I am convinced that the only solution to this problem is the certification of programmers by a vendor-independent organization. Although Code Project has indicated that it is opposed to such a certification organization, I believe that the arguments offered were specious. My question is simply "Doesn't the programmer who wrote the software that caused some type of catastrophe share the responsibility for the disaster?" It is for this reason that certification is required. Once such an organization is in place, companies that do not wish to share the blame for a software-based disaster can hire a certified professional. The certified professional should then use certified journeymen and certified apprentices to design and implement the software. I believe that it is time to organize a programmers' association that can provide certification and other benefits not available to programmers today. For example: a stable retirement fund, not affected by the continuous movement of programmers from one job to another; job protection from any number of ills that plague our profession; career guidance and referrals; legal assistance in the case it is needed; and any number of other services. Of course, there would be a cost but, hopefully, a well-spent cost. It is time for programmers to organize, if not to obtain services not available today, but to raise their profession to a recognized standing.
Gus Gustafson
I never suggested sending graphics components to the screen; only that graphics components drawn later will hide graphics components drawn earlier. I had assumed that an off-screen buffer was involved. I mention this in two of my articles: Animated-Controls-using-graphic-layers and Anatomy-of-a-UserControl-SliderControl
Gus Gustafson
Can you be helped by the fact that a filled rectangle will hide any rectangle that it overlaps (or pieces thereof) drawn earlier?
Gus Gustafson
+5 Good thought.
Gus Gustafson
Should WaitOne have been named WaitOn?
Gus Gustafson
As a professional, I don't think that matters. When Hostinger was notified of the problem they should have started the repair. Instead they stood around wringing their hands.
Gus Gustafson
To my knowledge, Hostinger provides a thirty day refund. After that, for any reason even if it's something they've done, there's no refund.
Gus Gustafson
My reason for choosing inmotion was simply that they sponsor updates to FileZilla. I use FileZilla to update the website and I am very comfortable with inmotion's technical support. Please note that as a wizened developer, my questions usually were about the hosting, not what I was hosting. My websites are HTML, JavaScript, CSS, PHP, and SQL. Many hosting outfits are technically challenged when trying to discuss the contents of these websites. Thanks for your thoughts.
Gus Gustafson
:)
Gus Gustafson
I'm sorry, either I was not clear or you misunderstood me. I had just renewed the account with Hostinger for two more years when the problems were detected. I reported the problem to Hostinger about 45 days after the renewal. I never expected any refund to cover a period when everything worked correctly. It was a refund of the newly renewed account that I desire.
Gus Gustafson
I gave some thought to getting the scripts to work with Hostinger. However, if you refer to the original post, I stated that the scripts worked to more than a year, without any problems at all. What's worse, after the move to inmotion, without modification, the scripts worked as before. As I implied earlier, the problem was Hostinger's - not mine.
Gus Gustafson
I will take your suggested course of action. However, I do think that Hostinger should hold itself responsible and make the refund. Thanks for your thoughts.
Gus Gustafson
If any of you are wondering where you should host a website - stay away from Hostinger. Although their prices are competitive their technical expertise is extraordinarily shallow. Their refund policy defies belief. I've been hosting an organization's website on Hostinger for two years. At the end of May 2022, Hostinger decided to move the website to a new server (supposedly part of some maintenance effort). Apparently the transfer completed and I was told to use a new IP address. I use FileZilla and was able to upload new files to the website on its new server. But this website is also used by a Raspberry Pi to download a set of slides that it (the RPi) would display in the organization's lounge. The RPi home directory contains a number of scripts that, once the slides are uploaded to the website, are executed to prepare the RPi for slideshow display (using feh). Part of that preparation is to copy (using wget) the slides into a local-to-the-RPi directory. feh displays the slides in that directory. This makes the slideshow independent of the Internet. But after the transfer, the wget script was broken. So too were all PHP scripts. I advised Hostinger of the problem. Their denials sounded like something a junior programmer might espouse. Of course nothing that Hostinger did was wrong - it was entirely an error in my scripts (scripts that had worked flawlessly for almost one year before the transfer). About a month ago, I decided that Hostinger's inability to fix the problem was forcing me to re-host the website. I went to inmotion. So, Hostinger was unable to fix the problem they caused. Would they refund the two years paid for. No! So I will not use nor recommend Hostinger for any website hosting. Stay away.
Gus Gustafson
My comment still applies. What the user views is a result of an architectural/design decision; what a following programmer sees appears to be the subject of this question. Kornfeld Eliyahu Peter's response is, I believe, the correct one.
Gus Gustafson
I don't believe a "user" has anything to do with the issue. It's the following programmers who are affected.
Gus Gustafson