I am using PB9, I don't like a garbage characteristics, I wrote the program, if a program error, compiled through, he suggests that couldn't save, save, cause I got half a day's code can't save, don't want to close all closed, is rubbish, if they need to set up, in order to save?

CodePudding user response:

I think this is a very good garbage, prevent errors, in case of open no next time.

CodePudding user response:

I think this is rubbish, compile next time don't find it, I used the VB, VC, DELPHI, code whether rightly or wrongly, can save, if I am in a hurry, don't want to get up, want to save on the garbage, you can't save, you angry don't angry!

CodePudding user response:

This is no way to PB, when saving will compile this object, the compiler is not through, can't save,

(this is the tortoise ass, you want to change, can only buy PB)

You are in a hurry, and selection error function/event, annotations, preservation,

The next selection, cancel the annotations, change again,

CodePudding user response:

Skilled, you will find that this function is not garbage, but very good function,

CodePudding user response:

With reference to the upstairs feeling must be correct

CodePudding user response:

Must be correct grammar can save ~ ~

CodePudding user response:

If have something, can put the code selection, all comments, can save, have time to see where to write the wrong, your good,

CodePudding user response:

Syntax error can't save this is rigorous

CodePudding user response:

refer to the original poster HDJSJZG response:

I am using PB9, I don't like a garbage characteristics, I wrote the program, if a program error, compiled through, he suggests that couldn't save, save, cause I got half a day's code can't save, don't want to close all closed, is rubbish, if they need to set up, in order to save?

Compiled through the code, you can solve by commenting out/* */comments//line, it passed the compilation

CodePudding user response:

I also use VB, before suddenly with PB has just began to also feel very not adapt, now slowly think this set is very necessary, save the error code is just at the time of leaving a little meaning, using VB to keep down the error code, often before the next open, even after a long time to open, and compiled into the executable file, and then come back to find errors, is very troublesome thing, I also like to use especially on error resume next this code,,, ha ha,,,

Later with the error code stored in PB, and each time the run to save a code, if there are any bugs wrote some infinite loop or to crash the PB, error code is not preserved, it is not hard to write code from scratch, just a waste of time, difficult from a lot of code to find out an error in the code, though PB have errors, but also often and VB, tell you the wrong place, may be associated with other places, this only as a reference

Changes, but still have a bit of PB code, don't remember is run once after or after the save, want to use CTRL + Z to undo changes wouldn't work, so I often still keep some code in the text, if the original poster must temporarily leave, can also be copied out in all the problematic code stored, deleted again, save the PB, and then exit the
Do not have much impact