In der PureBasic ID hab ich da folgendes gemacht:
Wie kann ich das in der jaPBe IDE umsetzen?Argumente: "%TEMPFILE" "D:\developing\PureBasic\IDE & Compiler\Compilers\PB_EditorOutput.pb"
(X) Warte bis Werkzeug beendet
Wie kann ich das in der jaPBe IDE umsetzen?Argumente: "%TEMPFILE" "D:\developing\PureBasic\IDE & Compiler\Compilers\PB_EditorOutput.pb"
(X) Warte bis Werkzeug beendet
You cannot use it with arguments as a plugin, but as tool (plugins don't take arguments, but rely on the plugin interface).Leonhard hat geschrieben:Ich bin gerade dabei, ein PlugIn für jaPBe zu schreiben. Dabei soll bei jedem Compilieren / EXE-Erstellen mein PlugIn mit 2 Parametern gestartet werden: 1. der Name der Input-Datei (Source-Datei) und 2. der Name + der Output-Datei (die Datei, die geparst wird). Dabei soll die Orginal-Datei nicht verwendet werden.
In der PureBasic ID hab ich da folgendes gemacht:Wie kann ich das in der jaPBe IDE umsetzen?Argumente: "%TEMPFILE" "D:\developing\PureBasic\IDE & Compiler\Compilers\PB_EditorOutput.pb"
(X) Warte bis Werkzeug beendet
jaPBe manual hat geschrieben:Arguments
These are the command line parameters for your program. jaPBe supports the following placeholders:
%PATH
The path of the current file.
%FILE
The file name inclusive the path of the current file.
%TEMPFILE
The path and name of the file that jaPBe creates as a copy. Very handy if you want, that nothing will be changed on the original.
%CURSOR
This will be replaced by the current cursor position, in the form of LINExCOLUMN.
%WORD
Contains the word currently under the cursor.
%JAPBE
This will be replaced by the jaPBe main window handle.
%SCI
This will be replaced by the Scintilla window handle.
Trigger (only available for Plugins, or for Tools if 'Wait until tools Quit' is checked)
You can select when the tool or plugin should be executed. Any number of tools or plugins can have the same trigger, they will all be executed when the trigger event happens. The order of their execution depends on the order they appear in the list.
jaPBe Start : the tool will be executed right after jaPBe has been fully started.
jaPBe End : the tool will be executed right before jaPBe ends. Note that all open sources have already been closed at this time.
Before Compile/Run : the tool will be executed right before the compiler is called to compile a source code with F5/F6.
After Compile/Run : the tool will be executed right after the compilation is finished, but before the executable is executed for testing.
Before Create EXE : the same as for the "Before Compile/Run" trigger applies here too, only that the triggering event is when the user creates the final executable (F7).
After Create EXE : the tool is executed after the compilation to create the final executable is complete.
Source loaded : the tool is executed after a source code has been loaded into jaPBe.
Source saved : the tool will be executed after a source code in jaPBe has been saved successfully.
Code: Alles auswählen
StartDrawing( ScreenOutput() )
dummy()
StopDrawing()
..
Code: Alles auswählen
If InitSprite() = 0 Or InitKeyboard() = 0 Or InitMouse() = 0 Or InitSound() = 0
MessageRequester("Error", "Can't open DirectX 7 or later, mouse-, input- or sound-device", 0)
End
EndIf
If InitSprite3D() = 0
MessageRequester("Error", "Can't open DirectX 7 sprite-support or later (initsprite3d)", 0)
End
EndIf
End
Also in den Projekteinstellungen ist absolut kein Include angewählt. In den Einstellungen zu jaPBE ist ebenfalls kein Include gewählt. Die Definitions hier im Screenshot:Volker: schau mal in Deinen Einstellungen welche Includes und Deklarationen
da aktiviert sind.
Möglicherweise wird die InitSprite3d() Funktion mit einer anderen
Prozedure "überladen"