Love it!
On Tue, Mar 31, 2020 at 07:29 Ken Pettit wrote:
>
> On 3/26/20 7:00 PM, John R. Hogerhuis wrote:
> >
> >
> >
> > Don't ask, don't tell :-)
> >
> > sprintf at least is inherently dangerous and should never be used.
> > Should always use snprintf so you're committing to a certain buffer
On Fri, Mar 27, 2020 at 6:18 PM Brian K. White wrote:
> On 3/27/20 9:14 PM, Kevin Becker wrote:
> > The official sourceforge version builds on Fedora 31 with the distro
> > FLTK cleanly for me now. Thanks!
> >
> > As a side note, I'm leery of sourceforge too, but it has changed
> > ownership
On Fri, Mar 27, 2020 at 6:14 PM Kevin Becker wrote:
> The official sourceforge version builds on Fedora 31 with the distro FLTK
> cleanly for me now. Thanks!
>
> As a side note, I'm leery of sourceforge too, but it has changed ownership
> again since the days when they were injecting adware and
On 3/27/20 9:14 PM, Kevin Becker wrote:
The official sourceforge version builds on Fedora 31 with the distro
FLTK cleanly for me now. Thanks!
As a side note, I'm leery of sourceforge too, but it has changed
ownership again since the days when they were injecting adware and such
into
The official sourceforge version builds on Fedora 31 with the distro
FLTK cleanly for me now. Thanks!
As a side note, I'm leery of sourceforge too, but it has changed
ownership again since the days when they were injecting adware and such
into installers.
On Fri, 2020-03-27 at 20:01 -0400,
I've deleted github.com/bkw777/VirtualT because the upstream original
builds cleanly now, and although I don't love sourceforge, it does turn
out to offer basic collaboration like github/gitlab, where anyone can
make an account, fork, modify, and submit back to the original, all
browseable in
On 3/26/20 9:44 PM, Ken Pettit wrote:
Hey Brian,
No, I didn't get any of these warnings, but then I didn't have the -Wall
flag set. When I set that ... oh my! I will have to go through and do
some cleanup ... I don't like warnings!
I'm pulling down my github copy because now the
On Thu, Mar 26, 2020 at 7:10 PM Ken Pettit wrote:
>
> Heck, programmer's have it easy these days ... they get 1's *and* 0's.
> When I was a kid, we only had 0's!
>
> Ken
>
>
Not judging your code or your advanced age ;-)
-- John.
Just to be clear, Fedora's distro supplied version of FLTK is 1.3.5
which is the current stable release on fltk.org
On Thu, 2020-03-26 at 21:40 -0400, Brian K. White wrote:
> On 3/25/20 10:27 AM, Ken Pettit wrote:
> > Hey Guys,
> > Okay, I have fixed this bug (in src/file.cpp). The de-tokenizer
>
On 3/26/20 7:00 PM, John R. Hogerhuis wrote:
Don't ask, don't tell :-)
sprintf at least is inherently dangerous and should never be used.
Should always use snprintf so you're committing to a certain buffer size.
Yep. But then again, almost all of this code was written over 10 year
On 3/26/20 9:44 PM, Ken Pettit wrote:
Hey Brian,
No, I didn't get any of these warnings, but then I didn't have the -Wall
flag set. When I set that ... oh my! I will have to go through and do
some cleanup ... I don't like warnings!
On the plus side, when I did this the first time it
On Thu, Mar 26, 2020 at 6:44 PM Ken Pettit wrote:
> Hey Brian,
>
> No, I didn't get any of these warnings, but then I didn't have the -Wall
> flag set. When I set that ... oh my! I will have to go through and do
> some cleanup ... I don't like warnings!
>
> Ken
>
>
Don't ask, don't tell :-)
Hey Brian,
No, I didn't get any of these warnings, but then I didn't have the -Wall
flag set. When I set that ... oh my! I will have to go through and do
some cleanup ... I don't like warnings!
Ken
On 3/26/20 6:40 PM, Brian K. White wrote:
On 3/25/20 10:27 AM, Ken Pettit wrote:
Hey
On 3/25/20 10:27 AM, Ken Pettit wrote:
Hey Guys,
Okay, I have fixed this bug (in src/file.cpp). The de-tokenizer was
not testing for quoted strings. I pushed the changes to the git repo
here if anyone wants to pull it and compile prior to an official VT
1.8 release:
git clone
ust remove them from the
feature set and freshen up the documentation?
Regards, Peter
Message: 16
Date: Wed, 25 Mar 2020 06:49:35 -0700
From: Ken Pettit mailto:petti...@gmail.com>>
To: m100@lists.bitchin100.com <mailto:m100@lists.bitchin100.com>
Subject: Re: [M100] Building Vir
d
to (like cassette support), or just remove them from the feature set and
freshen up the documentation?
Regards, Peter
Message: 16
Date: Wed, 25 Mar 2020 06:49:35 -0700
From: Ken Pettit
To: m100@lists.bitchin100.com
Subject: Re: [M100] Building VirtualT
Message-ID: <5e7b616f.6010...@gmail.com&
orth. :-)
> Cheers, Bert
>
>
> Original message
> From: Ken Pettit
> Date: 3/25/20 12:44 (GMT-06:00)
> To: m100@lists.bitchin100.com
> Subject: Re: [M100] Building VirtualT
>
>
> Hi Kevin,
>
>
>
> Okay, thanks. Guess I'm going to
: Ken Pettit
Date: 3/25/20 12:44 (GMT-06:00)
To: m100@lists.bitchin100.com
Subject: Re: [M100] Building VirtualT
Hi Kevin,
Okay, thanks. Guess I'm going to have to spend some time tonight
getting a Fedora VM up and running (or downloaded).
Ken
On 3/25/20 8
ret any characters within as ASCII characters and not
BASIC keywords.
Regards,
Peter
Message: 10
Date: Tue, 24 Mar 2020 13:27:39 -0700
From: Ken Pettit mailto:petti...@gmail.com>>
To: m100@lists.bitchin100.com <mailto:m100@lists.bitchin100.com>
Subject: Re: [M100] Bui
> > >
> > > > I am not sure if the keyword GOTO is the actual
> > > > substitution, as I am away from my "development"
> > > > computer
> > > > and can verify, but it illustra
Message: 10
Date: Tue, 24 Mar 2020 13:27:39 -0700
From: Ken Pettit mailto:petti...@gmail.com>>
To: m100@lists.bitchin100.com <mailto:m100@lists.bitchin100.com>
Subject: Re: [M100] Building VirtualT
Message-ID: <5e7a6d3b.4020...@gmail.com
<mailto:5e7a6d3b.4020...@
aracters within as ASCII characters and not BASIC keywords.
Regards,
Peter
Message: 10
Date: Tue, 24 Mar 2020 13:27:39 -0700
From: Ken Pettit mailto:petti...@gmail.com>>
To: m100@lists.bitchin100.com <mailto:m100@lists.bitchin100.com>
Subject: Re: [M100] Building Virt
r pairs and interpret any
> > characters within as ASCII characters and not BASIC
> > keywords.
> >
> >
> >
> > Regards,
> >
> >
> >
> > Peter
> >
etti...@gmail.com>>
To: m100@lists.bitchin100.com <mailto:m100@lists.bitchin100.com>
Subject: Re: [M100] Building VirtualT
Message-ID: <5e7a6d3b.4020...@gmail.com
<mailto:5e7a6d3b.4020...@gmail.com>>
Content-Type: text/plain; charset="window
occurrences of the " character pairs and interpret any characters
within as ASCII characters and not BASIC keywords.
Regards,
Peter
Message: 10
Date: Tue, 24 Mar 2020 13:27:39 -0700
From: Ken Pettit mailto:petti...@gmail.com>>
To: m100@lists.bitchin100.com <mailto:m100
On 3/25/20 12:23 AM, Peter Noeth wrote:
Does that include bug fixes from v1.7?
I sent Ken a PM back a while ago describing a bug I found, but got no
response.
Sorry about that Peter, I don't even recall seeing this email or knowing
about this bug. For a while there, my email client was
On Wed, Mar 25, 2020 at 1:19 AM Tom Wilson wrote:
>
> On Wed, Mar 25, 2020 at 1:09 AM John R. Hogerhuis
> wrote:
>
>>
>>
>> On Wed, Mar 25, 2020 at 1:05 AM Tom Wilson wrote:
>>
>>> Yeah, I experienced the same thing. At the very least, the de-tokenizer
>>> needs to scan for quotes and set an
On Wed, Mar 25, 2020 at 1:11 AM Tom Wilson wrote:
>
>> I guess the question becomes, what do you want it to do?
>>
>> What does the Model 100 ROM do when you save that program as ASCII?
>>
>> If it keeps those bytes as binary for VT to do the same behavior it would
>> have to understand whether
On Wed, Mar 25, 2020 at 1:09 AM John R. Hogerhuis wrote:
>
>
> On Wed, Mar 25, 2020 at 1:05 AM Tom Wilson wrote:
>
>> Yeah, I experienced the same thing. At the very least, the de-tokenizer
>> needs to scan for quotes and set an "inQuote" flag when it hits a quote and
>> export those as their
>
>
> I guess the question becomes, what do you want it to do?
>
> What does the Model 100 ROM do when you save that program as ASCII?
>
> If it keeps those bytes as binary for VT to do the same behavior it would
> have to understand whether it's detokenizing a token, a string, the
> contents of a
On Wed, Mar 25, 2020 at 1:05 AM Tom Wilson wrote:
> Yeah, I experienced the same thing. At the very least, the de-tokenizer
> needs to scan for quotes and set an "inQuote" flag when it hits a quote and
> export those as their ASCII value, not their token code. However, it would
> be really nice
On Wed, Mar 25, 2020 at 12:24 AM Peter Noeth wrote:
> Does that include bug fixes from v1.7?
>
> I sent Ken a PM back a while ago describing a bug I found, but got no
> response.
>
> The problem occurs when transferring a BASIC program from VirtualT to the
> PC in ASCII format. The bug concerns
a flag to track the occurrences of the "
> character pairs and interpret any characters within as ASCII characters and
> not BASIC keywords.
>
> Regards,
>
> Peter
>
>
> Message: 10
>Date: Tue, 24 Mar 2020 13:27:39 -0700
>From: Ken Pettit
>T
pret any characters within as ASCII characters and
not BASIC keywords.
Regards,
Peter
Message: 10
Date: Tue, 24 Mar 2020 13:27:39 -0700
From: Ken Pettit
To: m100@lists.bitchin100.com
Subject: Re: [M100] Building VirtualT
Message-ID: <5e7a6d3b.4020...@gmail.com>
Content-Type: t
Yes,
It is on SourceForge here:
git clone https://git.code.sf.net/p/virtualt/code virtualt
I will have MANY more changes to commit that are not in there yet.
Ken
On 3/24/20 7:20 PM, Brian K. White wrote:
Applied, thank you.
Tom's fix is in there now too.
This is still behind though.
Applied, thank you.
Tom's fix is in there now too.
This is still behind though. Whatever Ken and Steve have done recently
is not here.
Ken is your git repo on github or gitlab or someplace else public like that?
--
bkw
On 3/24/20 7:04 PM, Joshua O'Keefe wrote:
Here's a diff for building
Here's a diff for building your tree on modern OSX. It's a pretty small
diff -- just fixing Darwin.mk to use a modern arch (i386 and ppc aren't
buildable any more), and fixing a pointer comparison to an int (which is an
error on clang). The resulting binary runs, although I don't know enough
Hey Brian,
I think I found some of those array size fixes also, but not sure I
found all the same one you did perhaps. I will double-check your repo.
The extra warning parameter on the "Cancel button" in display.cpp was
correct ... I also made that change.
Ken
On 3/24/20 3:28 PM, Brian
Isn’t Ken just updating the SourceForge repo? There’s not a new build from
there, but I’ve seen checkin comments.
I have been able to get VirtualT to build on Windows with Visual Studio,
but I did have to locate the older version of FLTK. I may pull the latest
repo to update my working copy and
This version has a handful of build fixes and array size fixes, but does
not yet have the speed fix Tom Wilson posted.
Well, my best guess at the proper fixes. I made the compiler warnings go
away, but I'm not 100% sure they are really the right way to fix each item.
Some arrays looked like
Hey Guys,
Steven Hurd also converted the SourceForge.net cvs repo to a git repo.
Both he and I have been making updates to that repo. I am working
toward a VT 1.8 release.
Ken
On 3/24/20 1:22 PM, Kevin Becker wrote:
For what it's worth, I just built VirtualT on Fedora 31 using Brian's
For what it's worth, I just built VirtualT on Fedora 31 using Brian's github. I
didn't build fltk myself, I used the packaged versions.
git clone https://github.com/bkw777/VirtualT.git
sudo dnf install fltk fltk-devel fltk-static fltk-fluid libXinerama-devel
libjpeg-devel
export
How about Windows?
Anyone have a formula for what one needs to compile VT on Windows?
thanks.
sorry meant instructions on the Bitchin100 wiki.
http://bitchin100.com/wiki/index.php?title=Building_VirtualT_on_Linux
On Sat, Feb 1, 2020 at 9:42 AM Stephen Adolph wrote:
> I was able to compile virtualT1.7, as it stands on Sourceforge, using the
> instructions at club100, on the following
I was able to compile virtualT1.7, as it stands on Sourceforge, using the
instructions at club100, on the following system
Ubuntu 14.04 LTS
FLTK 1.3.5 obtained from FLTK site
GCC 4.8.4
I got a few warnings but no errors.
seems to work in linux.
Why I am doing this: extend VirtualT to support
any reason why these might not work on Ubuntu 16.04 LTS?
On Wed, Jan 8, 2020 at 12:12 AM Brian K. White wrote:
> Ubuntu 19.10
>
> gcc 9.2.1
>
> fltk 1.4.0
>actually "git clone https://github.com/fltk/fltk.git;
>And the CMake directions in the middle of here:
>
Ubuntu 19.10
gcc 9.2.1
fltk 1.4.0
actually "git clone https://github.com/fltk/fltk.git;
And the CMake directions in the middle of here:
https://github.com/fltk/fltk/blob/master/README.CMake.txt
"
mkdir build
cd build
cmake ..
make
sudo make install
"
I didn't supply
What specific versions of Linux, gcc, and FLTK were used? Any changes to
build FLTK?
Thank you for sharing.
Regards,
rcs
On Mon, Jan 6, 2020 at 10:17 PM Brian K. White wrote:
> I was just now able to build the latest FLTK and VirtualT on linux with
> the following changes from the v1.7
48 matches
Mail list logo
