subversion | 1 Mar 15:31 2012

SVN: teeemcee/5082 Make most slices.bi functions extern "C", remove SliceSetScreenX/Y (scre

teeemcee
2012-03-01 06:31:47 -0800 (Thu, 01 Mar 2012)
123
Make most slices.bi functions extern "C", remove SliceSetScreenX/Y (screen pos can't be modified
directly), add to slices.h
---
U   wip/slices.bas
U   wip/slices.bi
U   wip/slices.h
subversion | 1 Mar 15:31 2012

SVN: teeemcee/5083 More fonts from Kizul: 1-bit version of 10x10 font, updated 10x20 font

teeemcee
2012-03-01 06:31:50 -0800 (Thu, 01 Mar 2012)
70
More fonts from Kizul: 1-bit version of 10x10 font, updated 10x20 font
---
D   wip/fonttests/1020font2.bmp
A   wip/fonttests/NewFont10x10x1.bmp
A   wip/fonttests/NewFont10x20x1.bmp
Jay Tennant | 1 Mar 15:56 2012

Re: SVN: teeemcee/5082 Make most slices.bi functions extern "C", remove SliceSetScreenX/Y (scre

> From: subversion <at> HamsterRepublic.com
> Sent: Thursday, March 01, 2012 8:32 AM
> 
> teeemcee
> 2012-03-01 06:31:47 -0800 (Thu, 01 Mar 2012)
> 123
> Make most slices.bi functions extern "C", remove SliceSetScreenX/Y (screen pos can't be modified
directly), add to slices.h

Wait, they can't be modified? How are they updated?
James Paige | 1 Mar 16:04 2012

Re: SVN: teeemcee/5082 Make most slices.bi functions extern "C", remove SliceSetScreenX/Y (scre

On Thu, Mar 01, 2012 at 06:56:07AM -0800, Jay Tennant wrote:
> > From: subversion <at> HamsterRepublic.com
> > Sent: Thursday, March 01, 2012 8:32 AM
> > 
> > teeemcee
> > 2012-03-01 06:31:47 -0800 (Thu, 01 Mar 2012)
> > 123
> > Make most slices.bi functions extern "C", remove SliceSetScreenX/Y (screen pos can't be modified
directly), add to slices.h
> 
> Wait, they can't be modified? How are they updated?

A slice's screen position strictly depends on the entire chaing of 
realtive x/y positions of all of a slice's ancestors, parent, 
grandparent, great-grandparent, all the way back to the root slice. 
screen x and y are re-computed when the slice tree is drawn.

Take a look at DefaultChildRefresh and DefaultChildDraw in slices.bas to 
see how it works.

---
James Paige
Jay Tennant | 1 Mar 19:01 2012

Gui slices, required state

The GUI system is evolving to be much more related and affected
by slices. There was discussion on SelectableSlice's, but I'd like
to discuss what kind of slices are necessary for the GUI system.

The most basic GUI slice (ie. client area) requires a few states:
-isFocused
-isEnabled
-isClipping
-positionRect
-clippingRect

The basic slice already maintains position and clipping, leaving:
-isFocused
-isEnabled

The following GUI objects have requirements in addition to that.

Button requires:
-isPushed (or checked)
-text (for the button label)

Pull-down list requires:
-isPushed
-selected item
-list of items

Drop-down menu:
-isPushed
-text (for the menu label)
-list of items
(Continue reading)

Ralph Versteegen | 2 Mar 05:26 2012
Picon

Re: Gui slices, required state

On 2 March 2012 07:01, Jay Tennant <hierandel8 <at> crazyleafgames.com> wrote:
> The GUI system is evolving to be much more related and affected
> by slices. There was discussion on SelectableSlice's, but I'd like
> to discuss what kind of slices are necessary for the GUI system.
>
> The most basic GUI slice (ie. client area) requires a few states:
> -isFocused
> -isEnabled
> -isClipping
> -positionRect
> -clippingRect
>
> The basic slice already maintains position and clipping, leaving:
> -isFocused
> -isEnabled
>
> The following GUI objects have requirements in addition to that.
>
> Button requires:
> -isPushed (or checked)
> -text (for the button label)

The text should be a separate child slice. Also, the button should
also have a separate Rectangle child slice instead of drawing the
button directly:

ButtonSlice
\-RectangleSlice
  \-TextSlice

(Continue reading)

Jay Tennant | 2 Mar 06:39 2012

Re: Gui slices, required state

> From: Ralph Versteegen <teeemcee <at> gmail.com>
> Sent: Thursday, March 01, 2012 10:27 PM
> 
> On 2 March 2012 07:01, Jay Tennant <hierandel8 <at> crazyleafgames.com> wrote:
> > The GUI system is evolving to be much more related and affected
> > by slices. There was discussion on SelectableSlice's, but I'd like
> > to discuss what kind of slices are necessary for the GUI system.
> >
> > The most basic GUI slice (ie. client area) requires a few states:
> > -isFocused
> > -isEnabled
> > -isClipping
> > -positionRect
> > -clippingRect
> >
> > The basic slice already maintains position and clipping, leaving:
> > -isFocused
> > -isEnabled
> >
> > The following GUI objects have requirements in addition to that.
> >
> > Button requires:
> > -isPushed (or checked)
> > -text (for the button label)
> 
> The text should be a separate child slice. Also, the button should
> also have a separate Rectangle child slice instead of drawing the
> button directly:
> 
> ButtonSlice
(Continue reading)

subversion | 2 Mar 07:23 2012

SVN: teeemcee/5084 Opps, turns out that r5082 broke compiling on Windows. Insert a bunch of

teeemcee
2012-03-01 22:23:12 -0800 (Thu, 01 Mar 2012)
100
Opps, turns out that r5082 broke compiling on Windows. Insert a bunch of ugly EXTERN "C"'s to fix :(
---
U   wip/custom.bas
U   wip/slices.bas
U   wip/slices.bi
subversion | 2 Mar 16:40 2012

SVN: teeemcee/5085 hspeak: check source directory for includes before current directory

teeemcee
2012-03-02 07:40:43 -0800 (Fri, 02 Mar 2012)
68
hspeak: check source directory for includes before current directory
---
U   wip/hspeak.exw
Ralph Versteegen | 2 Mar 18:13 2012
Picon

Re: SVN: teeemcee/5077 Set the visibility of map layers based on whether they're set to visible

On 29 February 2012 12:54, James Paige <Bob <at> hamsterrepublic.com> wrote:
> On Wed, Feb 29, 2012 at 12:25:44PM +1300, Ralph Versteegen wrote:
>> On 29 February 2012 12:01, James Paige <Bob <at> hamsterrepublic.com> wrote:
>> > On Wed, Feb 29, 2012 at 11:51:26AM +1300, Ralph Versteegen wrote:
>> >> On 29 February 2012 04:01, James Paige <Bob <at> hamsterrepublic.com> wrote:
>> >> > On Mon, Feb 27, 2012 at 11:14:57PM -0800, subversion <at> HamsterRepublic.com wrote:
>> >> >> teeemcee
>> >> >> 2012-02-27 23:14:57 -0800 (Mon, 27 Feb 2012)
>> >> >> 106
>> >> >> Set the visibility of map layers based on whether they're set to visible in the map editor (fixes bug 952)
>> >> >> ---
>> >> >> U   wip/game.bas
>> >> >
>> >> > I wonder if this breaks any games that left layers disabled in the
>> >> > editor but that did not intend them to be disabled in the game? Seems
>> >> > like rpgbatch could tell us, maybe?
>> >> >
>> >> > ---
>> >> > James
>> >>
>> >> Luckily that would only affect games made with nightlies since Zenzizenzic.
>> >
>> > Yeah, you are right. The chances of a game being broken by this are
>> > pretty slim, so I am not worried.
>> >
>> > One thing that I am^H^Hwas a little worried about is that if I read the
>> > code correctly, the visibility of map layers was never changed when you
>> > moved from map to map, and now with this fix it is. That means a script
>> > might have hidden a map layer and then expected it to stay hidden as the
>> > player moved from map to map. That would have been bad scripting, but it
(Continue reading)


Gmane