PureBasic Forums - English

gnozal , you are great, change nick to GNOZAL
best regards
tom

Hi Gnozal,

With lasts updates I get a message, a COMPILATION ERROR:

It says: "Could not compile form!", "Error: Line 9 -Bad parameter tupe, number expected instead of string".

Why?
Now with your update with Help, help file is showed and it flashes as it is refreshing all the time. Program doesn't find the preferences file and it's impossible work.

Can you help me please? I have reinstalled the PB and the PureForm w/o success. I don't know what can I do.

My OS is Spanish XP.[/img]

Jordi wrote:Hi Gnozal,
With lasts updates I get a message, a COMPILATION ERROR:
It says: "Could not compile form!", "Error: Line 9 -Bad parameter tupe, number expected instead of string".
Why?

You are probably generating code for the wrong PB version, i.e. generating code for PB3.94 and trying to compile it with PB4.02.
Check 'Generate PB4 code' in setup.
If this is not the case, please post your form (use Edit -> Copy project to clipboard and paste it in your post between code tags)

Jordi wrote:Now with your update with Help, help file is showed and it flashes as it is refreshing all the time.

Can't reproduce. What are the steps to get this ?

Jordi wrote:Program doesn't find the preferences file and it's impossible work.

Can't reproduce this. Seems to work here : PureFORM loads and saves it's ini file correctly.

Hello gnozal,

after enabling syntax coloring for code view in the preferences-dialog, PureFORM crashes with the following message:
Greetings ... Kiffi

Kiffi wrote:Hello gnozal,
after enabling syntax coloring for code view in the preferences-dialog, PureFORM crashes with the following message:

Thanks for the report.
Sadly, I cannot reproduce it (even with a fresh installation). Looks like some scintilla function was called even though scintilla wasn't initialized.
Anyway, I have uploaded a new version ; does it fix the crash ?
If not, could you please post the steps necessary to produce the error ?
Thanks.

gnozal wrote:Sadly, I cannot reproduce it (even with a fresh installation). Looks like some scintilla function was called even though scintilla wasn't initialized.

I think, the crash is a result of reading an invalid registry entry. Perhaps i've
started PB3.94 earlier to test 'old' code. The bug doesn't appear, when the
PB-IDE4 was opened before starting PureFORM. (ts-soft gave me this hint).

Greetings ... Kiffi

Hi,

The problem is starting PureForm, I can not do anything, program start, show all the windows and help and then it is refreshing all the time. If I try to close the help, automatically opens again, getting the focus so I can not do anything.

My PB is 4.02 and I have done a new installation in another PC with the same result. I don't know what can I do.

Can you send me an INI file?

Thanks for your help.

Jordi wrote:The problem is starting PureForm, I can not do anything, program start, show all the windows and help and then it is refreshing all the time. If I try to close the help, automatically opens again, getting the focus so I can not do anything.

Weird ! It's like your F1 key is pressed all the time ?!

Jordi wrote:Can you send me an INI file?

Here is the default generated ini file generated on my PC (1280x1024 screen) :

PureFORM.ini wrote:;PureFORM (c) gnozal
[Options]
FORM_GridIsActive = 1
FORM_GridIsVisible = 0
FORM_GridValue = 5
FORM_IsPBVer4 = 0
FORM_MarkSelectedGadget = 1
FORM_RememberWindows = 1
FORM_ProjectSaveConfirmation = 0
FORM_CaptureGadgetDelay = 100
FORM_IncludeBinary = 0
FORM_SyntaxColoring = 0
FORM_LoadKeywordsFromPurebasicEXE = 0
FORM_IsUndoActive = 0
FORM_AskConfirmationForDeleteGadget = 1
FORM_GadgetEnumerationMode = 1
FORM_EnableEditableSpinGadgets = 0
FORM_CompilerPath = C:\PureBasic400\Compilers\PBCompiler.exe
FORM_SnapToGridDuringGadgetMove = 0
FORM_ShowOnlyActiveWindow = 0
FORM_StickyWindows = 0
FORM_PBAny = 0
FORM_ActivateDefaultColors = 0
FORM_UseScintillaInCodeView = 1
FORM_MultilanguageSupport = 0
FORM_AddCodeTags = 0
FORM_UseJaPBeInCodeInject = 0
FORM_LoadSyntaxColors = 0
FORM_ReloadSourceInJaPBe = 0
FORM_DontEnableWindowInvisibleInFORM = 1
[History]
[Windows]
Window_CodeViewX = 376
Window_CodeViewY = 727
Window_CodeViewW = 896
Window_CodeViewH = 242
Window_GadgetViewX = 0
Window_GadgetViewY = 116
Window_GadgetViewW = 368
Window_GadgetViewH = 485
Window_WindowListX = 1088
Window_WindowListY = 350
Window_WindowListW = 184
Window_WindowListH = 350
Window_GadgetPropX = 0
Window_GadgetPropY = 628
Window_WindowPropX = 904
Window_WindowPropY = 0
Window_GadgetBarX = 904
Window_GadgetBarY = 350
Window_GadgetGroupsX = 500
Window_GadgetGroupsY = 400
FORM_StartOpenGadgetProp = 17526624
FORM_StartOpenWindowProp = 17526640
FORM_StartOpenCodeView = 17526592
FORM_StartOpenGadgetView = 17526608
FORM_StartOpenWindowList = 17526768
FORM_StartOpenGadgetBar = 17526736
[LastProject]
FORM_ProjectName =
FORM_LoadLastProject = 0
[DefaultColors]
TextColor_0 = -1
BackColor_0 = -1
TextColor_1 = -1
BackColor_1 = -1
TextColor_2 = -1
BackColor_2 = -1
TextColor_3 = -1
BackColor_3 = -16777216
TextColor_4 = -1
BackColor_4 = -1
TextColor_5 = -1
BackColor_5 = -1
TextColor_6 = -1
BackColor_6 = -1
TextColor_7 = -1
BackColor_7 = -1
TextColor_8 = -1
BackColor_8 = -1
TextColor_9 = -1
BackColor_9 = -1
TextColor_10 = -1
BackColor_10 = -1
TextColor_11 = -1
BackColor_11 = -1
TextColor_12 = -1
BackColor_12 = -1
TextColor_13 = -1
BackColor_13 = -1
TextColor_14 = -1
BackColor_14 = -1
TextColor_15 = -1
BackColor_15 = -1
TextColor_16 = -1
BackColor_16 = -1
TextColor_17 = -1
BackColor_17 = -1
TextColor_18 = -1
BackColor_18 = -16777216
TextColor_19 = -1
BackColor_19 = -1
TextColor_20 = -1
BackColor_20 = -1
TextColor_21 = -1
BackColor_21 = -1
TextColor_22 = -1
BackColor_22 = -1
TextColor_23 = -1
BackColor_23 = -1
TextColor_24 = -1
BackColor_24 = -1
TextColor_25 = -1
BackColor_25 = -1
TextColor_26 = -1
BackColor_26 = -16777216
TextColor_27 = -1
BackColor_27 = -1
TextColor_28 = -1
BackColor_28 = -1
TextColor_29 = -1
BackColor_29 = -1

Update

Changes :
- fixed a bug in code translation feature when #PB_Any was used in source code

Hi Gnozal,

Thanks for your new update, but I am not lucky.

Program starts, show Help, a messagebox saying:
"Compiler Version Mismatch!

PBCompiler reports version 4.02
Code Generation is for PB 3.94

Please correct your settings"

Click on accept and again this messagebox is showed. Then I close it and show the help file, close it and again splash...

Please help me.

I have installed on a "clean PC" in c:\Purebasic and all was OK but with c:\Archivos de Programa (in my notebook) not run OK.

Thanks.

Hi again
I have changed the line:

"FORM_IsPBVer4 = 0"

in your INI to

"FORM_IsPBVer4 = 1"

and messagebox with warning doesn't appear but the help files yes, it's impossible to close because all the time it's opened and go to Introduction, it's like F1 it's clicked all the time yes.


Thanks for your support.

gnozal
Then I compile project with imagegadget last version give err:
It's use by default my temp dir

Molchyn wrote:gnozal
Then I compile project with imagegadget last version give err:
It's use by default my temp dir

Code: Select all

DataSection ;>
  Image_ImageGadget_4:
 ; ORIGINAL FILE NOT FOUND : ""
  IncludeBinary "C:\DOCUME~1\MYDIR~1\LOCALS~1\Temp\_tc\PureBasic\Examples\Sources\Data\PureBasic.bmp"
EndDataSection ;<

This means that there is no image specified for ImageGadget_4 (null string), so PureFORM replaces it in the generated code with a bitmap from the standard Purebasic installation.
If you have specified an image for the ImageGadget and still get this problem, please post your project (Edit -> Copy project to clipboard ; Paste into your post between code tags).

Jordi wrote:Hi again
I have changed the line:
"FORM_IsPBVer4 = 0"
in your INI to
"FORM_IsPBVer4 = 1"
and messagebox with warning doesn't appear

Note that you don't have to change the ini file.
You can use :
Menu 'Setup' ->'Generate PB4 code'
or
Menu 'Setup' -> 'Preferences' -> 'Code' tab -> 'Generate PB4 compatible code'

Jordi wrote: but the help files yes, it's impossible to close because all the time it's opened and go to Introduction, it's like F1 it's clicked all the time yes.

Sorry, I really can't reproduce this problem. The help file is only displayed if the F1 key is pressed, so I don't understand why this happens ... Try to rename the help file, so it cannot be opened anymore. I will see if I can change anything.