Not sure if this is even an acceptable question, but I figured it's an IDE so...
I'm trying to write a small program in qb4.5, which has happily worked on my computer (XP SP3) for a while now. For some reason though it is now sluggish and error-prone. As the title reads, if I try to open a file then QB crashes out. A virus recently attacked my registry (among other things), and after removing it and fixing many entries there are probably some entries that I haven't corrected that may affect this.
I believe that QuickBasic uses the MSDOS edit command for its IDE. Presumable that program is affected by the virus. If that is the case, you should have problems opening other files in EDIT too.
I believe that QuickBasic uses the MSDOS edit command for its IDE
The QuickBASIC IDE (-> QB.EXE) is a self-contained application. QuickBASIC doesn't use the MS DOS editor (EDIT.COM) as an input screen. The QB IDE offers several features you won't find in EDIT.COM, for example a SUB/FUNCTION browser, live syntax checking, compile+launch menu, ...
The styling of the QB IDE looks very similar to the appearance of EDIT.COM but it's a different application. In fact, one can run QB.EXE in DOSBOX without even having EDIT.COM installed.
Related
I'm using this plugin for intelliJ
Database Navigator
I just wanted a simple tool to check my sqlite database, now that the firefox plugin I use is no longer working with the latest firefox update.
Sad!
Anyway, the plugin is good... except it seems to have added it's own "clever" sql checker, that finds all the sql in my java files, and then tells me if there are problems with the sql.
All well and good, but this
slows down editing those java files
doesn't work, finding phantom errors
isn't needed. Who struggles with writing sql?
So right now I have a bunch of red "tick" marks down the side of any java file with sql in it, as the plugin imagines up issues where there are none. I'd like these to just go away, I don't need code telling me if my code works - any ideas
how?
Here is an example of this thing:
I don't want the sql "string" to be treated as special, I don't want "analysis" performed on it, I can write working SQL.
Every time i load this class, the ... whatever it is takes up time looking at all the strings, and then makes EVERYTHING red on the sidebar. I don't want to disable all inspections on this page, as I do like to see when my java code has an error.
I know it is possible to tell intellij to stop looking at strings, I had this setting before - and then my laptop was stolen, thank you thieves - and now I have setup my environment again, I don't have my notes on how to resolve this issue.
The strings are "analyzed" when they are used in some methods of the package java.sql.
Click on a string and press Alt+Enter to expand the suggestion list
Select "Language Injection Settings" to open the configuration dialog for "SQL"
Uncheck all the checkboxes, press "OK" and all errors must be gone
Technical note: Settings are stored in <USER>/<.IDE_VERSION>/config/options/IntelliLang.xml
I recently upgraded from PhpStorm 6 to PhpStorm 7. Delighted to see all the improvements, but it runs awfully slow on my low-powered netbook. The delay between typing and seeing text appear is often 5-6 seconds and gets worse as line count increases. It is unusable at this stage.
How can I improve the general IDE speed and responsiveness?
Edit 2017: You may first want to try experimenting with allocating PhpStorm some more RAM if available. Do this by
Going to Help -> Edit Custom VM Options
Change -Xms and -Xmx to be something reasonable for your hardware. I have -Xms512m and -Xmx2048m on an 8GB RAM laptop.
Restart PhpStorm.
If you want to see how much RAM PhpStorm is currently using, you can go to File -> Settings and search for and enable show memory indicator.
Original answer: I made some changes to increase the responsiveness of the IDE. I'm sure there are more things one could do, but I found these to improve the performance to well within usable margins. From most effective to least:
Disable language injections: File -> Settings -> Language injections. Untick as many boxes as you're comfortable with. HTML was the real killer for me.
Disable inspections: File -> Settings -> Inspections. Untick as many as you don't need.
Disable unused plugins: File -> Settings -> Plugins. Untick unused.
These changes brought down both the startup time and significantly increased responsiveness of the IDE in general.
Add these to your phpstorm.exe.vmoptions or phpstorm64.exe.vmoptions file, at the bottom:
-Dawt.useSystemAAFontSettings=lcd
-Dawt.java2d.opengl=true
Solid speedup to the point that the editor is now actually usable.
I will for the life of me just never understand why people create editors in Java.
If you need to speed up PhpStorm right away, turn on Power Save mode.
(File > Power Save Mode or using "Hector the Inspector" icon in the IDE status bar). This mode turns off on-the-fly code inspections
This way you can finish what you have started, and later decide what code inspections to deactivate.
OUTDATED IF YOU USE A VERSION MORE RECENT THAN 2017.1 :
The most effective way to speed up new phpstorm version is an experimental feature that is going to be shipped by default in phpstorm 2017.1. Until that you can activate it on jetbrains products (webstorm, phpstorm etc.)
Click on Help => Edit custom properties
Add editor.zero.latency.typing=true
Close and open again the application.
For me the change typing is not laggy anymore.
Other tricks didn't helped me or not in a noticeable way.
Try removing unnecessary files from your project.
I had 3k+ *.html log files inside my project and that slowed down typing terribly when the 'Project' tab was open. (Hiding the project tab or turning off the PHP Plugin does also speeds up PHPStorm, but obviously those are not viable trade-offs.) (I'm using PHPStorm 2016)
In my case, PhpStorm wasn't slow at all - a bug in my monitor driver introduced severe lag, and it just happened that I dedicated that monitor to PhpStorm. If you've read this far, try PhpStorm on a different monitor, it would've saved me a lot of time.
It is possible that it will help to increase the maximum memory allocation for PhpStorm beyond its default.
For mine, it was capped at 2GB. I know you asked about a windows machine, but for mac users reading this, you can change this by opening PhpStorm without opening a project. Then hit Configure > Edit Custom Properties and change the xmx value to a higher limit.
Try to exclude the C:\Program Files\JetBrains\PhpStorm 2020.1\plugins\ folder to the windows firewall exclude directories, that will make the phpstorm run faster and indexing will be quick.
Windows firewall thinks that malicious software has been installed with lot of jar files. This solution has worked for me. But I have excluded my project laravel folder too
Possible Solutions
Use and older version of phpstorm that your machine fully supports
Disable the unwanted plugins
Disable the unwanted inspections and intentions
Disable the unwanted browser support by pressing ctrl + alt + s then Tools > Web Browsers >
I want to use F# for some very basic tasks for which I previously used batch files. I can associate fsx files with fsi.exe and run it just by double clicking them. That's great so far.
However, sometimes I might want to dive into the code deeper and debug things. When I open the fsx file within Visual Studio I can't run it and I also can't select the lines and use "Send to interactive", though.
It seems to me as if those commands only work if you set up a full F# project. That seems to be cumbersome (as an batch file replacement). I wonder which is the right approach? I want to have my cake and eat it! I want a simple file that I can change quickly but I also want the ability to use the analyze things with Visual Studio on demand.
UPDATE
I just figured out you can open the interactive console at "View\Other Windows\F# Interactive" and after that you do have the "Send to Interactive" command.
I'm still lacking the ability to run the code and set breakpoints, though..
As you already discovered, you don't need to create project to use the F# Interactive console.
I believe that features like debugging are a lot less important when you use F# for interactive development (or scripting), because you can quite easily evaluate code step-by-step to analyze its behaviour just by sending individual commands to FSI. So I don't feel the need for debugging in F# Interactive very often.
Although this isn't really a supported feature, you can debug code in a script file when using just F# Interactive. The trick is to attach the debugger to the fsi.exe process that's running behind the F# Interactive.
Just go to "Debug" -> "Attach to Process" and then select "fsi.exe". Then you should be able to place brakepoints in the fsx script file and the code running in F# Interactive will break. As I said, this is not really supported, but it generally works well for code in functions. I don't find this as useful often, but it may be useful now and then.
I'm seeing a strange build bug a lot. Sometimes after typing some code we receive the following build error.
Class 'clsX' must implement 'Event PropertyChanged(sender As Object, e As PropertyChangedEventArgs)' for interface System.ComponentModel.INotifyPropertyChanged'.
And
'PropertyChanged' cannot implement 'PropertyChanged' because there is no matching event on interface 'System.ComponentModel.INotifyPropertyChanged'.
Those error should never go together! Usually we can just ignore the exception and build the solution but often enough this bug stops our build. (this happens a lot using Edit and Continue which is annoying)
We're using Vb.net and c# mixed in one big solution.
Removing the PropertyChanged event and retyping the same code! sometimes fixes this.
Question:
Has anyone else seen this problem and has some suggestions how to prevent his?
We're using a code generator that causes this error to surface but just editing some files manually triggers this exception too. This error occur's on multiple machines using various setups.
Someone had the same exact issue discussed here. It sounds like there is an issue with this build picking up an old version of a binary. I would try the following in order:
Verify all assembly references use project references where possible within the Visual Studio solution.
Disable build parallelization in case there is some weird file locking issue with concurrent project builds. Go to Tools -> Options, Projects and Solutions -> Build and Run, then set "maximum number of parrellel project builds" to 1. Not the best solution but it may help narrow down the problem.
Disable the Hosting Process in case it's locking some file causing an assembly to not get rebuilt correctly. For C# project go to Project Properties, Debug tab, and uncheck "Enable the Visual Studio hosting process". For VB.NET project you'll need to Unload Project, Edit the project file, and add <UseVSHostingProcess>false</UseVSHostingProcess> to the PropertyGroup of each configuration. Again, not the best solution but you probably won't notice a difference.
Lastly, try doing a Clean + Build to try and resolve the issue when it occurs (I know this is not a fix but it's easy enough to do), also Rebuild may be slightly different than Clean + Build so try the latter if the former doesn't work.
As I can not comment due to lack of appropriate points.
But I would like to share one of my experience:
In an aspx.cs page I was working, used to compile fine and some time gave mysterious error of a variable not defined or function not defined or sometime variable or the function defined two times. I changed possibly each and every variable and function name but there seemed no effect , but after entering a simple space or a new line at any place in the file used to solve the compile error. At one time I tried to save the file (in a different encoding as i am used to experiments) and found that the file was not saving in the correct encoding (i.e. the ansi encoding because the file had a unicode character ), I removed the unicode character and that compile error didn't bothered me again.
This unicode character problem could be (not a hard and fast rule) there so you could check it.
Nuke & restore using source control (TFS instructions here):
Make sure you have everything checked in
Exit Visual Studio
Rename the project directory to .Bak (effectively deleting it)
Reopen Visual Studio and in source control:
Get Specific Version
check 'Overwrite... not checked out' and 'Overwrite ... even if local version matches'
Re-open project
Another problem: Make sure some source files are not newer than the current date (or your date is set back). Often this happens in apps where you are doing logic that requires certain things to happen differently on certain dates. You change your clock to test it, make a revision to the source with the date advanced, set the date back, and viola, rebuild does not rebuild that file.
You say 'typing it in again' - can you try just saving? After 40 years since MULTIX the .net build still decides what has changed by checking the file timestamp.
good luck!
When you get the error, is it always on the VB calling C# side, or vice-versa, or does it work both ways?
If the answer is either of the first two situations, try building the "callee" project within the solution before building the "caller" project to see if it stops the situation.
Also, just in case it may jog something for you to think about, does this error crop up when you change a VB file or a C# file, or is there no correllation?
Oh, and sorry this looks like an answer instead of a comment, I cannot post comments yet (need 50 rep).
I'm new to VB6 but i'm currently in charge of maintaining a horror of editor like tool with plenty of forms, classes, modules and 3rd party tools all chunk together like the skin faces on that guy in the texas chainsaw massacre...
What i don't understand is why i get different results when i run the app in debugging mode, vs when i compiled it and run it on my devevelopment pc vs when i installed it on a different pc.
Yes i know i'm dumb, so please direct me to where i can find out more about this. I'm hoping to find out something like different linking, registry related etc connection that i'm simply not getting right now, i.e. something like wax on, wax off :P
The main pain in the neck is when i'm trying to debug some errors from my QA and i need to find a spare pc to test this on plus i can't directly debug because i don't know where the code is if i do it that manner.
Thanks.
i run the app in debugging mode vs when i compiled it and run it on my
devevelopment pc
When you compile you have the option of compiling to native code or pcode. The debugger runs using pcode only. Under rare circumstances when you compile to native code there will be a change in behavior. This particular is really rare. I used VB6 since it's release and I may get it once or twice a year. My application is a complex CAD/CAM creating shapes and running metal cutting machine and has two dozen DLLs. Not a typical situation. At home with my hobby software I never ran into this problem.
There are another class of errors that result from event sequencing problems. While VB6 isn't truly multi-tasking it has the ability to jump out of the current code block to process a event. If it re-enters the same block for the new event interesting things (to say the least) can result. I think this is the likely source of your problems as you software is an editor which is a highly interactive type of software.
In general the problem is fixed by reordering the effected areas. You find the effected area by inserting MsgBox or write to a text file to log where you are. I recommend logging to a text file as MsgBox tend to alter behavior that are timing or multi-tasking related.
Remember if a event fire while VB6 in the middle of a code block and there a DoEvents floating around then it will leave the code block process the event and return to the original code block. If it re-enters the same code block and you didn't mean for this to happen then you will have problems. And you will have different problems on different computers as the timing will be different for each.
The easiest way to deal with this type of issues is create some flag variables. In multi-tasking parlance they are known as semaphores or mutexes. WHen you enter a critical section of code, you set it true. When you leave the routine you set it to false. If it is already true when you enter that section of code you don't execute it.
when i installed it on a different pc.
These are usually the result of the wrong DLL installed. Most likely you have an older version while the target has a newer version. I would download the free Virtual PC and create a clean Window XP install to double check this.
If your problem is event timing this too can be different on different computers. This is found by logging (not MsgBox) suspect regions.
If you can display a screen shot or the text of your specific errors then I can help better.
The first thing to check would be the versions of all the dlls that your app depends on - including the service pack version of the VB6 dll.
Have you any more specific details about what's behaving differently?