Date   
Re: Wake on LAN (WoL)

Richard Russell
 

On Sun, Jan 14, 2018 at 07:03 pm, Storer, Darren wrote:
Has anyone implemented Wake on LAN (WoL) in BB4W?
Do you mean that the BB4W program will be sending the wake packet, or that it runs on the PC that's being woken?

Richard.

Wake on LAN (WoL)

Storer, Darren
 

​Hi,

Has anyone implemented Wake on LAN (WoL) in BB4W? I'm looking for a WoL example to integrate with a program to control a Sony Bravia TV via the Simple IP protocol.

Thanks in advance for any pointers...

Darren

Re: Android update kills BBC BASIC?

Richard Russell
 

On Sat, Jan 13, 2018 at 06:22 pm, Lindsay Reid wrote:
At least you have the same problem/hardware/OS as me
The difference is that mine is working again!  :-)

I've filed a bug but I don't suppose SDL will be fixed any time soon, so I'll continue to apply my patch until it is.   Fortunately the bug only affects Android, which happens also to be the only OS for which I build SDL 2.0 from the source so is amenable to this approach.  The Windows, Linux, Mac OS and Raspberry Pi editions of BBCSDL all use the pre-built SDL2 library available from the repositories etc., so patching isn't an option.

Richard.

Re: Android update kills BBC BASIC?

 

Sorry for lack of reply. I'll wait for the time being. At least you have the same problem/hardware/OS as me so I'll leave it with you for now.

Many thanks.

Re: Android update kills BBC BASIC?

Richard Russell
 

On Wed, Jan 10, 2018 at 06:15 am, Richard Russell wrote:
Are you happy to wait until I release an 'official' update
I will assume that your failure to respond means that you are happy to wait.

Richard.

Re: Windows 10 Gestures

Mark Moulding
 

This probably doesn’t completely address your issue, but it may help show somewhere else to research:
 
I have an application I wrote that uses a “rubberband box” to zoom into an area of an image.  The problem was that, on touch screens with Windows 7 or above, this would activate the touch-scrolling feature.  To disable this, and make the touch screen respond just like a regular mouse (without the scrolling gesture), I used the following registry change:
 
HKEY_CURRENT_USER, Software\Microsoft\Wisp\Touch\PanningDisabled=1
 
There are a bunch of other possible entries under Wisp also, all of which seem poorly documented (or not at all).  Still, I suspect your solution may reside there...
~~
Mark Moulding
 
 
 
 

Re: Windows 10 Gestures

Norman Vingoe
 

You say it works with a 'real' mouse attached? I realise a mouse would be cumbersome, but how about a trackball (inverted ball mouse)? That is, if the stick PC has sufficient USB ports

Re: Windows 10 Gestures

Richard Russell
 

On Thu, Jan 11, 2018 at 03:19 am, Chris Coxall wrote:
The question I'm asking could a separate stand alone small application for enabling or disabling these gestures, for the computer as a whole, be created bbc4w?
The SetProp function you refer to doesn't affect global state (MSDN says "Adds a new entry or changes an existing entry in the property list of the specified window").  You could try calling it (assuming you can discover the window handle to which it needs to be applied) but I wouldn't be confident that it will work 'cross process'.  Be prepared to experiment!

Richard.

Windows 10 Gestures

Chris Coxall
 



 

Can anyone help with this. I am building a handheld Windows 10 PC to be able to replicate the programming and work I do with out of production Windows Mobile Phone\PDAs.

I'm using a Kiano Slim Stick PC Plugged into a 5 inch HDMI screen. A resistive touch panel overlay on the screen and USB PenMount controller for stylus touch control on the small screen.

A test run on a mock up build showed stylus control and the use of the on screen keyboard to be OK for most expected use. BUT!

A problem was found in a windows desktop publisher software. Stylus movement on the screen pans the desktop publisher page around the applications work area. Selecting a DTP object i.e. text frame, picture or other object items to position somewhere else on the page will just pan the complete page around the work area. To move an object around the page the selected object needs to be slashed right first then held to move it around the work area. This is not easy to make happen and when positioning is paused the user has to again make a number attempts to move the object. None of this happens when using an external mouse.

Gestures are being used here. They are not PenMount software gestures I have them disabled and when they were enabled they didn’t seem to do anything. The gestures being applied seem to be 3 basic Windows OS single touch gestures. Drag finger left to right to move selected, long press for right click and flicks up or down to pan. See here Windows 10 single touch gestures. https://msdn.microsoft.com/en-us/library/windows/desktop/dd940543(v=vs.85).aspx

 

In Windows 10 settings “Pen and Touch” only two settings are available double click and long press. For the desk top publisher application I do not need a pan gesture the application has its own button for panning. Between the PenMount driver and Windows 10 settings there is no way to disable unwanted gestures. An option to disable these gestures is needed for PenMount installation to be of use for stylus control on small screens.



The Windows 10 operating system seems to me at fault here as it gives no notification that these gestures are in use. After web searching for many hours and trying out help site recommendations nothing in Windows 10 settings to disable gestures was found.

could a separate small application for enabling or disabling these gestures be created



On the bottom of this web page there is some C++ code that seems to suggest it could be.
https://msdn.microsoft.com/en-us/library/windows/desktop/dd562171(v=vs.85).aspx

Code Portion

"
C++

const DWORD_PTR dwHwndTabletProperty =

TABLET_DISABLE_PRESSANDHOLD | // disables press and hold (right-click) gesture

TABLET_DISABLE_PENTAPFEEDBACK | // disables UI feedback on pen up (waves)

TABLET_DISABLE_PENBARRELFEEDBACK | // disables UI feedback on pen button down (circle)

TABLET_DISABLE_FLICKS; // disables pen flicks (back, forward, drag down, drag up)

SetProp(hWnd, MICROSOFT_TABLETPENSERVICE_PROPERTY, reinterpret_cast<HANDLE>(dwHwndTabletProperty));
"



This code given is for building into programmers own applications. The question I'm asking could a separate stand alone small application for enabling or disabling these gestures, for the computer as a whole, be created bbc4w?

Thanks in Advance



Looking forward to your response.

Regards Chris Coxall

Re: Android update kills BBC BASIC?

Richard Russell
 

On Wed, Jan 10, 2018 at 06:07 am, Lindsay Reid wrote:
Exactly the same has happened to me on a Oneplus 5
Are you happy to wait until I release an 'official' update, once the discussions at the SDL forum have come to some conclusion, or would you prefer a quick fix - with an unapproved patch to SDL - to get you back up-and-running?

Richard.

Re: Android update kills BBC BASIC?

 

Exactly the same has happened to me on a Oneplus 5. All other apps seem fine. Was fine prior to Oxygen update

Re: Android update kills BBC BASIC?

Richard Russell
 

On Tue, Jan 9, 2018 at 04:26 pm, Richard Russell wrote:
It could be a bug that has been accidentally introduced, or it could be a legitimate change that has somehow caused SDL 2.0 to fail.
It appears to be a bug in SDL - or at least a feature of SDL that has been broken by an Android update.  I am currently involved in an exchange at the SDL forum to decide how it should best be tackled.  Because (unlike the other editions) BBC BASIC for Android ships with SDL bundled, I can at least patch it myself rather than having to wait for an official update.

Richard.

Re: Android update kills BBC BASIC?

svein svensson
 

BBC Basic running ok here.

Tested two programs from each category.

Samsung Galaxy S8 with the latest update (it reports).

Regards Svein

Android update kills BBC BASIC?

Richard Russell
 

An OS update to my Android phone (OnePlus 5) today has killed BBC BASIC: the only things that still work are scrolling the file menu and the Back button!  Anything else, such as attempting to run a program, causes a crash.

This is obviously rather worrying.  I think it's highly unlikely that my code is at fault, because it still runs fine in Windows, Linux, Mac OS and Raspberry Pi - as well as on my other Android devices (which have not received a recent update).  The problem could be specific to OnePlus's 'Oxygen OS' variant of Android or to the latest security update to Android Oreo in general.  It could be a bug that has been accidentally introduced, or it could be a legitimate change that has somehow caused SDL 2.0 to fail.

If you have an Android device, and it offers you an OS update in the near future, can I please ask you to run BBC BASIC before and after the update, and to report if it stops working for you as well.

Richard.

Re: Proposal to change the meaning of '<<<'

J.G.Harston
 

I've just done a text search and have found no instances of '<<<' outside a couple of strings.

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

Re: Proposal to change the meaning of '<<<'

Richard Russell
 

On Sat, Jan 6, 2018 at 02:19 am, Ric wrote:
seems to be sensible except that it is 3 characters long.
But so is '>>>' which has been in BBC BASIC for at least 30 years, so I don't see how that can be an objection.  Indeed the only reason that '<<<' is accepted by BB4W and BBCSDL is because the code which handles '>>>' also recognises '<<<' as a side-effect, and with no extra effort.

Aliasing '<<<'  to '<<', as I do currently, seems natural to me because exactly the same thing happens in x86 assembly language.  The shift mnemonics SAR (signed shift right, >> in BBC BASIC) and SHR (unsigned shift right, >>> in BBC BASIC) are distinct and of course generate different opcodes.  But SAL and SHL (which you can think of as << and <<< in BBC BASIC) generate the same instruction:

065C1744 C1 F8 05  sar eax,5
065C1747 C1 E8 05  shr eax,5
065C174A C1 E0 05  sal eax,5
065C174D C1 E0 05  shl eax,5

Maybe by the time we get to 512 bits (hyperthetically) we could have <<<<<<
I know there was a smiley, but that's a false analogy.  >> and >>> are distinct only to allow you specify signed and unsigned shift-right operations; the same pair of operators suits for any number of bits.

Richard.

Re: Proposal to change the meaning of '<<<'

Ric
 

Pretty sure I've never used it by mistake, or deliberately, seems to be sensible except that it is 3 characters long. Maybe by the time we get to 512 bits(hyperthetically) we could have <<<<<<😜

Ric

Sent from my HTC

----- Reply message -----
From: john_fowler_son@...
To: <bb4w@groups.io>
Subject: [bb4w] Proposal to change the meaning of '<<<'
Date: Fri, Jan 5, 2018 09:46

Pretty sure I have never used this as I was never aware it was not a syntax error, so this sounds a good propsal to e.

Howard

Re: Proposal to change the meaning of '<<<'

Howard
 

Pretty sure I have never used this as I was never aware it was not a syntax error, so this sounds a good propsal to e.

Howard

Re: Proposal to change the meaning of '<<<'

dai_m_leeds
 

Hi Richard,

I can see how that could be useful, and there's no real excuse that I can see for having it in existing code.

Best wishes,

D

Re: Proposal to change the meaning of '<<<'

 

Almost certain I’ve never used that (except perhaps in a string). It’s not present as a token in a .bbc file, I presume, so searching program files for its presence should be straightforward. I vote yes.