How to make changes to a Dialog persistent

new Apache OpenOffice.org mail list to replace this list

executing a dialog without blocking the program

Announcing "BNF4OOo - Managing Backus-Naur-Forms with OpenOffice"

missing setSelectedItem() method in XComboBox interface

XButton, XFixedText, etc (Graphical components)

INFO: New home and EOL of this mailing list in the near future

Re: Constant values for Function arguments

I just realised that I sent the last message privately, sorry for
that. Here's the same thing (with some additions) but to the list
instead:

2011/8/18 Thomas Krumbein <thomaskrumbein <at> openoffice.org>:
> Hey Johnny,
>
> honestly, a lot of your questions/things are "basics"...

Yes, I know. So that's why nobody replies, I suppose. Maybe I'd be
better off sending them to the users' list instead, then. I'll do that
next time. Thanks for the warning. We guitar players are not too
bright…

> VALUE, STRING, FORMULA and DATETIME are reserved words in Basic and
> cannot be used as constant or variable names. Ever thought about this?

 Well, I know STRING is (it turns blue when I type it).
 But why did it work in my other example? And why did the monitor show
 the right values?

 But I'm sure going to try your suggestion, the one about not using
 those names. Thanks!
 I was originally going to use the original values, like
 ”com.sun.star.sheet.CellFlags.STRING”, but all those long (or broken)
 lines are so hard to read, so I like to keep it short, but not too
 short…

 Yes, I am a beginner (I will probably always be) and yes, I have
 troubles understanding English some times, which makes it even harder
 for me, since almost all information I can find is in English.

 Best regards

 Johnny Rosenberg
 ジョニー・ローゼンバーグ

>
> Try to put a character in Front (i.E. nValue, or myString)  and
> everything works as expected....
>
> Best regards
> Thomas
>
>
> Am 18.08.2011 12:52, schrieb Johnny Rosenberg:
> Here's another delicate problem that's easy to work around, but still
> very strange:
>
> Module 2:
> ———Code starts below———
> REM  *****  BASIC  *****
>>
>> Option Explicit
>>
>> Public Const VALUE=1
>> Public Const STRING=4
>> Public Const FORMULA=16
>> Public Const DATETIME=2
>>
>> Sub HelloWorld
>>       Print "Hello world!"
>> End Sub
>> ———End of code———
>>
>>
>> Module1:
>> ———Code starts below———
>> REM  *****  BASIC  *****
>>
>> Option Explicit
>>
>> Sub Main
>>       Dim A
>>       A=VALUE+STRING+FORMULA
>> End Sub
>> ———End of code———
>> Run Main and you will get an error message at ”A=VALUE+STRING+FORMULA”.
>> If you run step by step (Ctrl+F8 in the BASIC IDE) and stop at that
>> line and then hover your mouse pointer over VALUE or STRING or
>> FORMULA, you can clearly see its values, but obviously this doesn't
>> help. Dimensioning A as Variant, as I did, doesn't help either. If you
>> look at VALUE, STRING or FORMULA in the variable monitor (or whatever
>> it's called in English), the window at the bottom left, you can see
>> that they are Variant/Integer and you can see their correct values.
>>
>> So now, let's move the constant definition to Module1:
>> Module 2:
>> ———Code starts below———
>> REM  *****  BASIC  *****
>>
>> Option Explicit
>>
>> Sub HelloWorld
>>       Print "Hello world!"
>> End Sub
>> ———End of code———
>>
>>
>> Module1:
>> ———Code starts below———
>> REM  *****  BASIC  *****
>>
>> Option Explicit
>>
>> Public Const VALUE=1
>> Public Const STRING=4
>> Public Const FORMULA=16
>> Public Const DATETIME=2
>>
>> Sub Main
>>       Dim A
>>       A=VALUE+STRING+FORMULA
>> End Sub
>> ———End of code———
>>
>> Now Main in Module1 works as expected, but take a look in the monitor
>> again. Those constants appears in exactly the same way this time as
>> before, the only exception is that this works.
>> I would be very grateful for an explanation about this. Is there
>> REALLY a logical reason for it to be this way or should I report this
>> as a bug as soon as possible?
>>
>> Of course I can define those constants in every module, but isn't one
>> of the points by declaring as Public that I can reach them in all my
>> modules? Well, in this case I can; I just can't use them, at least not
>> when adding them to each other.
>> ”A=VALUE” works in both my examples, but obviously not
>> ”A=VALUE+STRING+FORMULA” for some reason I am sure absolutely nobody
>> can explain, so please prove me wrong here…!
>>
>> :D
>>
>>
>> Kind regards
>>
>> Johnny Rosenberg
>> ジョニー・ローゼンバーグ
--

-- 
-----------------------------------------------------------------
To unsubscribe send email to dev-unsubscribe <at> api.openoffice.org
For additional commands send email to sympa <at> api.openoffice.org
with Subject: help

Constant values for Function arguments

Here's another delicate problem that's easy to work around, but still
very strange:

Module 2:
———Code starts below———
REM  *****  BASIC  *****

Option Explicit

Public Const VALUE=1
Public Const STRING=4
Public Const FORMULA=16
Public Const DATETIME=2

Sub HelloWorld
	Print "Hello world!"
End Sub
———End of code———

Module1:
———Code starts below———
REM  *****  BASIC  *****

Option Explicit

Sub Main
	Dim A
	A=VALUE+STRING+FORMULA
End Sub
———End of code———
Run Main and you will get an error message at ”A=VALUE+STRING+FORMULA”.
If you run step by step (Ctrl+F8 in the BASIC IDE) and stop at that
line and then hover your mouse pointer over VALUE or STRING or
FORMULA, you can clearly see its values, but obviously this doesn't
help. Dimensioning A as Variant, as I did, doesn't help either. If you
look at VALUE, STRING or FORMULA in the variable monitor (or whatever
it's called in English), the window at the bottom left, you can see
that they are Variant/Integer and you can see their correct values.

So now, let's move the constant definition to Module1:
Module 2:
———Code starts below———
REM  *****  BASIC  *****

Option Explicit

Sub HelloWorld
	Print "Hello world!"
End Sub
———End of code———

Module1:
———Code starts below———
REM  *****  BASIC  *****

Option Explicit

Public Const VALUE=1
Public Const STRING=4
Public Const FORMULA=16
Public Const DATETIME=2

Sub Main
	Dim A
	A=VALUE+STRING+FORMULA
End Sub
———End of code———

Now Main in Module1 works as expected, but take a look in the monitor
again. Those constants appears in exactly the same way this time as
before, the only exception is that this works.
I would be very grateful for an explanation about this. Is there
REALLY a logical reason for it to be this way or should I report this
as a bug as soon as possible?

Of course I can define those constants in every module, but isn't one
of the points by declaring as Public that I can reach them in all my
modules? Well, in this case I can; I just can't use them, at least not
when adding them to each other.
”A=VALUE” works in both my examples, but obviously not
”A=VALUE+STRING+FORMULA” for some reason I am sure absolutely nobody
can explain, so please prove me wrong here…!

:D

Kind regards

Johnny Rosenberg
ジョニー・ローゼンバーグ
--

-- 
-----------------------------------------------------------------
To unsubscribe send email to dev-unsubscribe <at> api.openoffice.org
For additional commands send email to sympa <at> api.openoffice.org
with Subject: help

ReDim driving me crazy again…

I edited a lot of code yesterday, one of the rows I did NOT edit was
this one, which occurs at the top of a subroutine:

ReDim NDice(1 To 6) As Integer

It is defined in another module as:
Public NDice(1 To 6) As Integer

The error message I get is (translated from Swedish):
”BASIC syntax error:
The NDice variable is already defined.”

Yes, I know it is, that's one of the points by using ReDim, isn't it?

Before doing some heavy editing there was no complaints on this line
at all, and as I said, this is NOT one of the many lines I changed.

So obviously some of my other edits caused this, but where to start
looking? What can I possible have done to cause this?

I just hate when these things happen, when there is an error message
telling me that I can't do something that I should be able to do. Like
if I got an error message for the line ”If a=b Then”, and the error
message says: ”BASIC syntax error: a and b are already compared”…
--

-- 
-----------------------------------------------------------------
To unsubscribe send email to dev-unsubscribe <at> api.openoffice.org
For additional commands send email to sympa <at> api.openoffice.org
with Subject: help

Custom types drives me nuts – this can't be happening… can it?

I was editing some code I have, actually a game with dice and stuff,
but that doesn't matter, I suppose.

So I ran into a problem, and I copied the troubling part of the code
to a separate document for test driving.
However, the test code runs perfectly, but not within the game of mine!

I ran the game on another computer but another version of
OpenOffice.org (actually the first computer runs LibreOffice 3.3.3),
but the results were exactly the same.

Here's the test code. I have a message box after almost every
statement so I can see what happens. I added some extra comments in
the code.

REM  *****  BASIC  *****

Option Explicit
Option Compatible

Type DieStatistics
	Value As Integer
	Count As Integer
End Type

' The variable DiceFreq, declared below this comment, tells us which
two die values that are most frequent. For example, if the six dice
are 133455,
' DiceFreq will contain:
' DiceFreq(0).Value: 5 (the most common value is 5)
' DiceFreq(0).Count: 2 (2 dice have the value 5)
' DiceFreq(1).Value: 3 (the second most common value is 3 – in this
case there are two of both 3 and five, but higher value has priority)
' DiceFreq(1).Count: 2 (2 dice have the value 3)
' This makes it very easy for us to calculate things later,
calculations that are not present in this short example though.
Private DiceFreq(1) As DieStatistics '

Sub Test0
'	NDice tells us how many there are of each die value. In the above
example, NDice(4)=1, since there are 1 die with the value 4.
	Dim NDice(1 To 6) As Integer, i As Integer

'	Here we set the values of NDice for an example where this is known
to fail, that is what NDice would contain if the dice were 112345
'	NDice(1)=2, NDice(2)=1 and so on.
	For i=2 To 5
		NDice(i)=1
	Next i
	NDice(1)=2
	
'	Here's where I calculate the values for DiceFreq by going through
NDice from 6 to 1.
	For i=6 To 1 Step -1
		If NDice(i)>DiceFreq(0).Count Then
			DiceFreq(1).Count=DiceFreq(0).Count
			DiceFreq(1).Value=DiceFreq(0).Value
				MsgBox DiceFreq(0).Value & ": " & DiceFreq(0).Count & " st." & Chr(13) & _
				DiceFreq(1).Value & ": " & DiceFreq(1).Count & " st."
			DiceFreq(0).Count=NDice(i)
			DiceFreq(0).Value=i
				MsgBox DiceFreq(0).Value & ": " & DiceFreq(0).Count & " st." & Chr(13) & _
				DiceFreq(1).Value & ": " & DiceFreq(1).Count & " st."
		ElseIf NDice(i)>DiceFreq(1).Count Then
			DiceFreq(1).Count=NDice(i)
			DiceFreq(1).Value=i
				MsgBox DiceFreq(0).Value & ": " & DiceFreq(0).Count & " st." & Chr(13) & _
				DiceFreq(1).Value & ": " & DiceFreq(1).Count & " st."
		EndIf
	Next i
	MsgBox "Final reults:" & String(2,Chr(13)) & DiceFreq(0).Value & ": "
& DiceFreq(0).Count & _
	 " st." & Chr(13) & DiceFreq(1).Value & ": " & DiceFreq(1).Count & " st."
End Sub

Now, while this works perfectly as a stand-alone subroutine, it
doesn't work in the game. What happens in the game is that everytime I
change the value of DiceFreq(i).Value or DiceFreq(i).Count, BOTH
instances are changed, for example if I set DiceFreq(0).Value to 5,
DiceFreq(1).Value is also set to 5 and I just can't figure out why!

In the game the corresponding subroutine is called from another
module, but I simulated that too in my test, but still it ONLY fails
in the game.

I can upload my game document (the debug version) somewhere if needed.

What on earth could possibly cause this? I'm just out of ideas!

Help…?

Kind regards

Johnny Rosenberg
ジョニー・ローゼンバーグ
--

-- 
-----------------------------------------------------------------
To unsubscribe send email to dev-unsubscribe <at> api.openoffice.org
For additional commands send email to sympa <at> api.openoffice.org
with Subject: help