Date   

Re: File - reminder.txt

Marcello
 

Thanks Svein,

Microsoft defines the COLORREF as: 0x00bbggrr

Marcello




On Tue, Sep 24, 2013 at 5:17 PM, Leslie Baker <leslie@...> wrote:
 

Svein,

I not an expert, but shouldn’t the value be 6 digits, not 8??

Eg: “00FF00”  (R G B)

 

... Leslie

 

 

From: bb4w@... [mailto:bb4w@...] On Behalf Of svein
Sent: 24 September 2013 15:52
To: bb4w@...
Subject: Re: [bb4w] File - reminder.txt

 

 

Maybe some info here.

 

 

Svein

 

> I am trying to set the text colour to BLUE for an editbox by issuing the following command:

>      ColorRef=&00FF0000

>     SYS "SetTextColor", TextHdl%, ColorRef

 

 



Re: File - reminder.txt

 

Svein,

I not an expert, but shouldn’t the value be 6 digits, not 8??

Eg: “00FF00”  (R G B)

 

... Leslie

 

 

From: bb4w@... [mailto:bb4w@...] On Behalf Of svein
Sent: 24 September 2013 15:52
To: bb4w@...
Subject: Re: [bb4w] File - reminder.txt

 

 

Maybe some info here.

 

 

Svein

 

> I am trying to set the text colour to BLUE for an editbox by issuing the following command:

>      ColorRef=&00FF0000

>     SYS "SetTextColor", TextHdl%, ColorRef

 

 


Re: OT: Yahoo neo groups

dai_m_leeds
 

 I've just been Neo'd, and I can't say it's a particularly pleasant experience.


I note that the "Temp" folder in the "files" area doesn't seem to link correctly, though others do (I haven't tested them exhaustively).


I'd assumed we'd still be able to use this as a file repository, though it sounds like even that is problematic...


D



---In bb4w@..., <yahoo@...> wrote:

--- In bb4w@..., <bb4w@...> wrote:

> I have had to change a number of URLs on my web
> pages that pointed to files in Yahoo Files areas Those URLs don't work
> any more. I have had to change them to point to the *folder* containing
> the file of interest, rather than direct to the file itself.

Oh.  If you can't any longer link directly to the file then I agree it's effectively unusable as a respository for things like updated libraries.

 

Richard.


Re: OT: Yahoo neo groups

Richard Russell
 

--- In bb4w@..., <bb4w@...> wrote:
> I have had to change a number of URLs on my web
> pages that pointed to files in Yahoo Files areas Those URLs don't work
> any more. I have had to change them to point to the *folder* containing
> the file of interest, rather than direct to the file itself.

Oh.  If you can't any longer link directly to the file then I agree it's effectively unusable as a respository for things like updated libraries.

 

Richard.


Re: OT: Yahoo neo groups

J.G.Harston
 

Ian Wade G3NRW wrote:
> In my experience of the new neo groups, Yahoo have indeed "mucked
> things up", good and proper.

It's a complete mess. One of the Yahoo Groups I'm subscribed to still
has the easily-navigable web front end, the other ten have changed to the
neo front end, and there doesn't seem to be any pattern to it.

--
J.G.Harston - jgh@... - mdfs.net


Re: OT: Yahoo neo groups

Ian_Wade_G3NRW
 

___Original Message_________________________________________
From: yahoo@rtrussell.co.uk
Date: Mon, 23 Sep 2013 Time: 09:10:01

-- In bb4w@yahoogroups.com, <bb4w@yahoogroups.com> wrote:
With immediate effect, and until further notice, this is no longer the
 'official' support group for BBC BASIC for Windows.
I've seen a couple of slightly strange reactions to this announcement.  One
person said that I had "closed down" the group - which of course I haven't -
and another that the group's Files area is "not available anymore" - when
(at least as far as I know) it is.
OK, I admit it. I was the one who misread your announcement and assumed
you were closing down the group. I stand corrected!


 
Unless Yahoo have mucked things up even more than I thought, it should
still be possible to upload a file to the group and publish a link to it, for
example on the Conforums board.
In my experience of the new neo groups, Yahoo have indeed "mucked things
up", good and proper. I have had to change a number of URLs on my web
pages that pointed to files in Yahoo Files areas Those URLs don't work
any more. I have had to change them to point to the *folder* containing
the file of interest, rather than direct to the file itself.

I think it's called progress...

--
73
Ian, G3NRW


Re: OT: Yahoo neo groups

Richard Russell
 

--- In bb4w@..., <bb4w@...> wrote:

> With immediate effect, and until further notice, this is no longer the

> 'official' support group for BBC BASIC for Windows.

 

I've seen a couple of slightly strange reactions to this announcement.  One person said that I had "closed down" the group - which of course I haven't - and another that the group's Files area is "not available anymore" - when (at least as far as I know) it is.

 

Unless Yahoo have mucked things up even more than I thought, it should still be possible to upload a file to the group and publish a link to it, for example on the Conforums board.

 

Richard.


Re: CB_ADDSTRING problem

Richard Russell
 

--- In bb4w@..., <kairosmedia@...> wrote:
> what affects the "sometimes" in your above sentence?

 

I don't know; I'm not sure that even Microsoft knows!  It is probably a combination of circumstances such as the version of Windows, whether it's 32-bit or 64-bit Windows, and your display drivers.  If drivers are involved then of course it may well be hardware- and vendor- specific.

 

If you wish to continue this thread please take it to the Conforums message board.

 

Richard.

 


Re: OT: Yahoo neo groups

Richard Russell
 

The dire 'Neo' Groups Experience is making this group (and the other Yahoo! groups I frequent) unusable.  In particular two major bugs are causing problems:

 

1.  Posted messages are often invisible, or only partly visible, or can only be seen by clicking on the ellipsis.  Even when messages are visible, they are often blank in the summary page.

 

2.  Posted messages which are identified as possibly spam are disappearing entirely rather than appearing as messages requiring approval.  If a message you have posted has never appeared on the group this is probably why.

 

With immediate effect, and until further notice, this is no longer the 'official' support group for BBC BASIC for Windows.  I will not be regularly monitoring it nor responding to queries posted here.  If you require support, please post your question to the BB4W message board at http://bb4w.conforums.com/

 

Richard.


Re: CB_ADDSTRING problem

Kairos <kairosmedia@...>
 

At 12:22 21/09/2013, you wrote:


--- In bb4w@yahoogroups.com, <kairosmedia@swissmail.org> wrote:
It works fine on all XP machines, it works fine on SOME Windows 7
machines, it doesn't work on some Windows 7 machines.
As discussed previously here, the wide-character (W suffix) API functions sometimes require the buffer you supply to be word-aligned (i.e. at an even memory address). If you haven't already done so, modify your code to ensure this and let us know if it helps.

I will try that, but I am also curious as to why it works on some machines and not others....what affects the "sometimes" in your above sentence?

Thanks

Nick


Re: CB_ADDSTRING problem

Richard Russell
 

--- In bb4w@..., <kairosmedia@...> wrote:
> It works fine on all XP machines, it works fine on SOME Windows 7


CB_ADDSTRING problem

Kairos <kairosmedia@...>
 

Hi

I have an app which uses, among other things, a dropdown box. I populate this with:

SendDlgItemMessageW

It works fine on all XP machines, it works fine on SOME Windows 7 machines, it doesn't work on some Windows 7 machines.

In cases where it works, SYS "SendDlgItemMessageW....CB_ADDSTRING...." returns 1

In non-working cases it returns 0

I can only assume that it has something to do with system-specific items - like comctrl32.dll or comdlg32.dll - these are loaded aut0matically by BB4W

QUESTIONS:

-- Can I easily see what version of these DLLs have been loaded by BB4W?

-- Are there any other system-specific items I should check?

I should say that both the working and non-working Windows 7 are 32 bit...and another non-working Win 7 is 64 bit

Thanks

Nick


Re: Unknown origin of error message

micheal9054
 

In my own case I was talking to a remote Atmel device, i realised some systems may have more than a single port and different com numbers. The resolution was to mod the atmel code to report to a handshake request and cycle the open com upwards to 10 in a simple repeat until open, then send the handshake, wait for reply, if not continue.
Solved the problem adequately.

you can wrap the relevant info in a DATA / READ arrangement and replace com% = OPENUP("COM1:9600,N,8,1") with


RESTORE +1:timeout%=0
DATA x, "COM1:9600,N,8,1", and so on
REPEAT
timeout% + = 1
READ com$:com% = OPENUP("com$")
UNTIL com%>0 OR timeout%=x

x being the number of $ in the line, so if timeout%=x and com%=0 didn't and can't open, if com% is true then timeout% carries the comport physical number.

Mike


Re: ON MOVE, is my understanding right?

 

Ah, got it. I can't pass @msg% and @lparam% as parameters because there's a chance they get interrogated at different times, it has to be in a single statement. All's well now, thanks.

A


Re: ON MOVE, is my understanding right?

Richard Russell
 

--- In bb4w@..., <roberts.mugswell@...> wrote:
> But that doesn't trap all the window size changes.

 

Oh yes it does!

 

> Have I got something wrong, or is this the right way to do it?

 

You have got something wrong.  The issue is described in the Help documentation under 'Hints and Tips... Re-entrant ON MOVE interrupts':

 

http://www.bbcbasic.co.uk/bbcwin/manual/bbcwini.html#hint12

 

There are other, more complicated, solutions to the problem when the method outlined in the manual isn't appropriate.

 

Richard.


Re: Unknown origin of error message

Richard Russell
 

--- In bb4w@..., <bb4w@...> wrote:

> make sure when you open the comport that it is opened!

 

I would second that.  It is almost certain that the 'Invalid channel' error arises because you attempted to open a file or port (with OPENIN or OPENUP) but didn't check that the returned handle was non-zero.

 

Does your program make provision for customizing the COM port number, for example by storing it in a configuration file or the registry?  If not, how does the end user tell the program what number his particular serial port is (even if there's only one it's not always COM1)?

 

Richard.


ON MOVE, is my understanding right?

 

I need to know the window size so that I can force a program to redraw when the window size changes. So I use ON MOVE and flag the event if @msg%=5. But that doesn't trap all the window size changes. If I grab the bottom right corner, right edge or bottom edge, then it works, but if I grab the top of]r left edge, ir I click the 'maximise' button, it doesn't.

The following program skeleton shows what I mean:

DIM Rc% 15
ON MOVE PROCmove(@msg%,@lparam%):RETURN
REPEAT
SYS "GetSystemMetrics",0 TO w% :REM get the screen size for the computer display
SYS "GetSystemMetrics",1 TO h%
PRINT TAB(0,0)"GetSystemMetrics" TAB(20)"w=";w%, "h=";h%
SYS "GetClientRect",@hwnd%,Rc%
w%=Rc%!8 : h%=Rc%!12+2 :REM size of window after status bar added
PRINT TAB(0,2)"GetClientRect" TAB(20)"w=";w%, "h=";h%
UNTIL INKEY(10)>0
END

DEFPROCmove(M%,S%)
PRINT TAB(0,4)"@msg%=";M% TAB(20)"W=";S%AND&FFFF, "H=";S%>>>16
ENDPROC

Have I got something wrong, or is this the right way to do it?

Alan Roberts


Re: Unknown origin of error message

micheal9054
 

--- In bb4w@yahoogroups.com, Ian Wade G3NRW <g3nrw-radio@...> wrote:

I have written a simple BBC Basic program that makes a tcp connection to
a remote host, then reads from/writes to that host. The program also
opens a COM port.

When running the program here, everything is fine (and so easy with BBC
Basic!).

However, someone else is now testing the program. He is running the
compiled .exe version -- he does not have BBC Basic on his machine. The
program successfully makes the tcp connection, but then, when attempting
to read from the port, an error message box pops up. The title bar says
simply "Error", and the message text says simply "Invalid channel".

I have no idea where this message came from.

As part of initialisation, the program contains these lines:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
install @lib$+"SOCKLIB"
proc_initsockets

on error sys "MessageBox",@hwnd%,report$,0,0 : proccleanup : quit
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This is the only mention of "Message Box" in the whole program, so I
assume this is what's producing the Error pop-up.

Is there any way of tracking down exactly what caused the error message
to appear and what it means?

--
73
Ian, G3NRW
make sure when you open the comport that it is opened! I wrote a program a few years ago and had these problems. the error occurs when the opened com was not infact opened, you try to listen or send ans the error pops up as the channel was not opened.


Unknown origin of error message

Ian_Wade_G3NRW
 

I have written a simple BBC Basic program that makes a tcp connection to
a remote host, then reads from/writes to that host. The program also
opens a COM port.

When running the program here, everything is fine (and so easy with BBC
Basic!).

However, someone else is now testing the program. He is running the
compiled .exe version -- he does not have BBC Basic on his machine. The
program successfully makes the tcp connection, but then, when attempting
to read from the port, an error message box pops up. The title bar says
simply "Error", and the message text says simply "Invalid channel".

I have no idea where this message came from.

As part of initialisation, the program contains these lines:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
install @lib$+"SOCKLIB"
proc_initsockets

on error sys "MessageBox",@hwnd%,report$,0,0 : proccleanup : quit
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This is the only mention of "Message Box" in the whole program, so I
assume this is what's producing the Error pop-up.

Is there any way of tracking down exactly what caused the error message
to appear and what it means?

--
73
Ian, G3NRW


Re: Site closure

Simon Mathiassen <simon@...>
 

I'm assuming it because David's announcement - which I saw purely by
chance - says the site "will close". If he was prepared for it to
remain online (for example by transferring the domain to another owner)
surely he would have made some moves in that direction first - such
as contacting people, like me, whom he knows would be interested in
keeping it alive.
Well, I have now asked him directly whether he would transfer the domain
to me, which he replied positively to, so i will not expect the
www.bb4wgames.com domain to die any time soon. If left to my devices, it
will also be non-static, so any new BB4W based game will be included in
the list.

Regards,

Simon

3581 - 3600 of 23951