I have this annoying bug in MS Expression Web 4 SP2, weird GUI quirks: you can see in the picture: like parts of the display isn't being painted. I had this before, and solved it by uninstalling something, but the problem is that I don't remember what it was... (I installed Exp.Web in fresh Win7 PC, and step by step installing everything, until this problem came up.)
Anybody came across this issue maybe ?
The problem is a program called FileBox eXtender. It's excellent program I use to pin windows to have them always on top (never be hidden by other windows), because it does its job and it's free. Unfortunately, MS-Expression (Web, Blend, etc...) doesn't get along with it, so I excluded it (somewhere in FileBox-eXtender's options) and now it's o.k.
Related
I installed Racket 8.5 on my MacBook (MacOS Ventura Beta) and ran into a number of problems:
the application windows don't close on the cross, even the ones that are considered additional menus and shouldn't work that way anyway. Add video
In projects from my computer, the functions do not work correctly. And this error appears even if I move the author's code into my Racket in a clean project. For example, from a project downloaded from the Internet, where the author writes:
empty-scene 100 100 "blue"
In his project everything works fine, this function is in the Racket documentation.
If I write this function in my project, Racket gives me an error;
empty-scene: expects only 2 arguments, but found 3
I tried to find information about this on the Internet, I reinstalled Racket and downloaded different versions of the program, but the problem persists.
Has anyone encountered similar problems? Are there any tips on how to fix it?
I have no idea about the window thing: this doesn't happen on macOS 11 and I suspect is an artifact of running it on some beta version of macOS.
The arguments are because you're not in fact using 2htdp/image but htdp/image, which provides a different version of empty-scene. This is clear from looking at your video.
Also, please provide a description, in text of what is needed to reproduce problems like this: images and videos are just not a useful thing.
I'm coming back with results! Your messages are confirmed. It turns out that everything was affected by the beta version of MacOS. After rolling back to Big Sur, both problems resolved.
Thanks so much Shawn and ignis-volens for looking at the problem from the outside and helping me solve it 🔥
I ran into an issue where my second monitor with decent resolution, was showing a poorly rendered VS2019.
Disclaimer: If somebody would port the features I need in VS2019 to VSCode that'd be great.
Anyway, here is a pic that sums up my issue and since I had to comb through the annoyingly fixed-but-not-fixed, yet locked, tickets on MS to find clues to my answer I'm sharing here.
Here is my secondary, 27" monitor, with poor rendering. This happens to be the ONLY program that does this... VSCode looks great and is readable, Outlook, Gimp, they all look fine. Only VS2019 is giving my eyes pain.
Main/Built-in Monitor looks just fine though. I'd prefer to work with more screen space though.
In VS2019 GOTO: Tools > Options >> Environment > General, and look for "Optimize rendering..." Note: This screenshot is from after I'd found and applied the the fix.
It will be grayed-out and unselected if requirements are not met by your system, along with a message, "Requires NET 4.8 and Windows 10 minimum build 1803". I then mistakenly installed NET 4.8, and nothing changed (and the checkbox was still locked indicating requirements were not met).
More searching lead me to the 4.8 Dev Pack. Here is a link to it:
NET 4.8 Developer Pack
Finally, after another reboot, I opened up VS2019 and the rendering looks something like modern... and the checkbox automatically checked itself.
For me the accepted answer didn't change anythig, turns out it was caused by scaling on Windows (on main monitor it was set to 125%), after changing it to 100% everything looks normal
For me, I just move the VS window to the blurry monitor. Close VS. Open VS again and all looks good.
I recently programmed a Windows Form Application on one laptop, however, when I attempt to run the executable on my client's PC it won't open. There are no error messages generated, it just won't open.
The only thing in use that wasn't built into VS2015 was Telerik UI for winforms and the application is a standalone exe.
Any suggestions?
I finally got this sorted a couple of days ago. After a LOT of fiddling about I realised that it was indeed to do with the references. After consulting the Telerik Documentation (as Chris suggested) I realised that, indeed, the dlls were stored in the GAC (something I'd never heard of) and not actually automatically packaged with the software. So I editted the program file options so that they were included and problem solved! Thank You all for your help and sorry the original question was so badly written, I had no idea what data it would have been relevant to include
One of my duties at my job is to enhance and maintain a mature VB.Net windows application used internally by my company. We run 8 computers at the small company that each runs the app with no problems.
Recently we replaced one of the computers with a pretty standard notebook running Win 7 Professional with SP1 and for some reason, it won't display message boxes displayed using the normal MessageBox.Show("Message") method.
The vendor who sold us the computer says it must be the program, and I kind of sympathize with that view, but the fact is we have 8 other computers that all display their message boxes just fine.
Thought I'd post the issue here to see if anyone else has run into this and, if so, did they find a resolution?
I'm going to paint outside the lines a little bit and answer my own question with sort of a non-answer.
We battled that computer for about a week and a half and finally gave up and reinstalled the OS. Problem solved. Not really an answer because we still don't know what was going on or why reinstalling the OS fixed it.
Reinstalling was really an act of frustration/desperation as much as anything else. In the end we were just thankful the problem went away and we could move on. Figured I'd get this off of the unanswered questions list since I'm not really waiting for or expecting an answer at this point.
I've inherited a lot of custom made software for an office, and, while managing it, I've found it performs differently from machine to machine.
I mean, some controls get painted in weird ways in some machines but well in another, or just work differently, like in some machines clicking something selects it, and in the next machine clicking the same thing makes it editable.
I suspect, of course, of the myriad of DLL the software loads.
Why does it happen? Is there any way of avoiding it?
Edit:
All the machines are Windows XP SP3, Internet Explorer 8
"get paint in weird ways" to me means things like a control being painted 300 or 400 pixels bigger in a machine than in the others (overlapping part of the GUI).
I would suspect that some COM components are the issue (COMCTL32 would be my first guess), and that it isn't really a VB.NET problem. Versioning in the .NET world has been made so that the typical DLL hell issues shouldn't happen as they did before, but there are always some relics around...
Without more info I doubt that there will be a final answer to your question. You may want to start your troubleshooting by comparing Windows, Service Packs and IE versions.
Step 1. Ensure all machines have the exact same updates applied. This goes beyond the service pack. Run Windows Update on each machine and apply everything you can. I suspect you have radically different patch levels across the board.
Step 2. Ensure all machines have the native screen resolution set. This is more important for flat panels than the ancient CRT monitors.
Step 3. Look at the video drivers. Make sure you have the latest ones for those machines.
Step 4. Make sure the exact same version of your app really is deployed across all of the machines. If there are external dependencies, verify those are the same as well.