Jump to content

EZE85

Members
  • Posts

    35
  • Joined

EZE85's Achievements

Newbie

Newbie (1/14)

10

Reputation

  1. Hey folks Im wondering what stats determine the level of risky match theyre willing to be part of? I want the Funker in a scaffold match but he wont do it and you cant set the risk any lower.So what is the check the game is doing? I can then tweak that stat to get round it. We all know Middle Aged and Crazy Funker would have done it so its annoying to not be able to run the risk.
  2. Direct link to Microsoft page for the download: https://www.microsoft.com/en-gb/software-download/windows10 Currently waiting on it to complete to see if it works. FIXES THE PROBLEM!
  3. <p>Ive been clicking the update, but theres no update apparently available and it says that I have the following</p><p> </p><p> Version 1909</p><p> Installed 28/08/2019</p><p> </p><p> When I know it did an update last night and again this morning... #isnottechy</p>
  4. Hi Adam. Is it possible *not being a coder* to replace the scroll bars with value boxes? A tool tip could inform you what the range is?
  5. <p>Amusing tidbit from i-programmer:</p><p> </p><p> </p><blockquote data-ipsquote="" class="ipsQuote" data-ipsquote-contentapp="forums" data-ipsquote-contenttype="forums" data-ipsquote-contentid="52965" data-ipsquote-contentclass="forums_Topic"><div>There's a problem for applications based on Visual Basic for all Windows machines that have installed the cumulative updates for August. The issue, raised by Microsoft, says that apps may stop responding if they use VB6, VBA, or VB Scripting Edition.<p> </p><p> The information, which has been added to the Knowledge Base pages for the August Update for all the major versions of Windows from Windows 7 onwards, reads:</p><p> </p><p> "After installing this update, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an "invalid procedure call error."</p><p> </p><p> vbsicon</p><p> </p><p> Microsoft seems remarkably calm about having done this to every single installation of Windows and to billions of users.</p><p> The Workaround section says:</p><p> </p><p> "Microsoft is presently investigating this issue and will provide an update when available."</p><p> </p><p> Well, that's all right, then.</p><p> </p><p> The issue was also posted as the final item after things that were obviously more important such as a problem if you attempt to rename files on a cluster shared volume as a CSV owner node from a process that doesn’t have administrator privilege. Obviously, this is going to cause headaches for a lot more people than the tiny percentage of developers who've used such minority languages as Visual Basic or VBA.</p></div></blockquote><p> </p><p> And then in March on mobilize.net</p><p> </p><p> </p><blockquote data-ipsquote="" class="ipsQuote" data-ipsquote-contentapp="forums" data-ipsquote-contenttype="forums" data-ipsquote-contentid="52965" data-ipsquote-contentclass="forums_Topic"><div><a href="https://www.mobilize.net/blog/windows-update-kills-vb6-apps1" rel="external nofollow">https://www.mobilize.net/blog/windows-update-kills-vb6-apps1</a></div></blockquote>
  6. Wouldn't we have an issue with *lots* of other programs eventually if we roll back the update for just the few apps in visual basic?
×
×
  • Create New...