xboxscene.org forums

Pages: 1 2 3 [4] 5

Author Topic: Upcoming Skinning Features  (Read 384 times)

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Upcoming Skinning Features
« Reply #45 on: January 08, 2004, 05:02:00 PM »

:::sigh:::

Well, didn't fix the text resizing issue, but give the latest "WIP" a whirl, as I've posted it.

Opacity isn't functional yet, but color should be working (so for text, you could use that to alter the opacity)
Logged

geniusalz

  • Archived User
  • Hero Member
  • *
  • Posts: 1635
Upcoming Skinning Features
« Reply #46 on: January 08, 2004, 05:28:00 PM »

I'm on it
Is the ease factor in yet?
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Upcoming Skinning Features
« Reply #47 on: January 08, 2004, 05:29:00 PM »

smile.gif
Logged

geniusalz

  • Archived User
  • Hero Member
  • *
  • Posts: 1635
Upcoming Skinning Features
« Reply #48 on: January 08, 2004, 05:42:00 PM »

<EaseFactor>1.0</EaseFactor> ?
Color tween works sweet.
Logged

geniusalz

  • Archived User
  • Hero Member
  • *
  • Posts: 1635
Upcoming Skinning Features
« Reply #49 on: January 08, 2004, 05:56:00 PM »

laugh.gif
All I see is (float) (double) 1.0f etc etc
Didn't know C++ was that bitchy about types (I thought java was bitchy enough)

Anyway,
>>>    return fValue;
should be
>>>   return fReturn;

And I read somewhere pow was overloaded.
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Upcoming Skinning Features
« Reply #50 on: January 08, 2004, 05:59:00 PM »

QUOTE (geniusalz @ Jan 8 2004, 09:56 PM)
You made mincemeat of my code! laugh.gif
All I see is (float) (double) 1.0f etc etc
Didn't know C++ was that bitchy about types (I thought java was bitchy enough)

Anyway,
>>>    return fValue;
should be
>>>   return fReturn;

Doh! Quick fix... I'm uploading the update at the moment. 1 minute for the binaries, a bit longer for the source.
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Upcoming Skinning Features
« Reply #51 on: January 08, 2004, 06:01:00 PM »

Yeah, pow() goes a bit crazy, and I like to cast, anyway.... it always pays to make explicit casts for things (prevents some potential bugs)
Logged

geniusalz

  • Archived User
  • Hero Member
  • *
  • Posts: 1635
Upcoming Skinning Features
« Reply #52 on: January 08, 2004, 06:24:00 PM »

CODE
 
    0xA8FFFFFF
    
    
   MenuP1
   MenuP3
   
   both
   0.2
   0xD4FFFFFF
   0x00000000
   MenuScroll
    

    
 

 
    0xD4FFFFFF
    
    
   Menu0
   MenuP2
   0xFFFFFF00
   0xA8FFFFFF
   
   both
   0.2
   MenuScroll
    

    
 

 
    0xFFFFFF00
    
    
    
   MenuN1
   MenuP1
   0xD4FFFFFF
   0xD4FFFFFF
   
   both
   0.2
   MenuScroll
    

    true
 

 
    0xD4FFFFFF
    
    
   MenuN2
   Menu0
   0xA8FFFFFF
   0xFFFFFF00
   
   both
   0.2
   MenuScroll
    

    
 

 
    0xA8FFFFFF
    
   
   MenuN3
   MenuN1
   0x00000000
   0xD4FFFFFF
   
   both
   0.2
   MenuScroll
    

    
 
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Upcoming Skinning Features
« Reply #53 on: January 08, 2004, 06:58:00 PM »

I'll take a look at things, but the tween is already "cooked" at that point to be a value from 0.0 to 1.0

Dunno why it's not working with the period tag. Strange.
Logged

geniusalz

  • Archived User
  • Hero Member
  • *
  • Posts: 1635
Upcoming Skinning Features
« Reply #54 on: January 08, 2004, 07:13:00 PM »

huh.gif

edit:
   else if ( _tcsicmp( sEaseType, _T("in") ) == 0 )
   {
      m_iEaseType = ETT_NONE;
   }
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Upcoming Skinning Features
« Reply #55 on: January 09, 2004, 02:07:00 AM »

QUOTE (geniusalz @ Jan 8 2004, 11:13 PM)
Up/down problem happens with 'out' and 'both'.  'In' doesn't work at all, even though the code is the simplest huh.gif

edit:
   else if ( _tcsicmp( sEaseType, _T("in") ) == 0 )
   {
      m_iEaseType = ETT_NONE;
   }

OK.... figured out a few problems, and fixed them.

Try out the latest update which I just upped a few minutes ago.

Now off to work (no net access there, either sad.gif but I'll be busy testing product on the bench, so no time for it anyway... I'll make an appearance around lunch time)
Logged

geniusalz

  • Archived User
  • Hero Member
  • *
  • Posts: 1635
Upcoming Skinning Features
« Reply #56 on: January 09, 2004, 03:04:00 PM »

CODE
 
    0xA8FFFFFF
    
    
   MenuP1
   MenuP2
   500
   in
   0.33
   0xD4FFFFFF
   0x00000000
   MenuScroll
    

    
 

 
    0xD4FFFFFF
    
    
   Menu0
   MenuP2
   0xFFFFFF00
   0xA8FFFFFF
   500
   in
   0.33
   MenuScroll
    

    
 

 
    0xFFFFFF00
    
    
    
   MenuN1
   MenuP1
   0xD4FFFFFF
   0xD4FFFFFF
   500
   in
   0.33
   MenuScroll
    

    true
 

 
    0xD4FFFFFF
    
    
   MenuN2
   Menu0
   0xA8FFFFFF
   0xFFFFFF00
   500
   in
   0.33
   MenuScroll
    

    
 

 
    0xA8FFFFFF
    
   
   MenuN2
   MenuN1
   0x00000000
   0xD4FFFFFF
   500
   in
   0.33
   MenuScroll
    

    
 
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Upcoming Skinning Features
« Reply #57 on: January 09, 2004, 03:08:00 PM »

I think it has something to do with the position... I see the effect right now (time for dinner, though), as I was just checking out the color tweening myself.
Logged

geniusalz

  • Archived User
  • Hero Member
  • *
  • Posts: 1635
Upcoming Skinning Features
« Reply #58 on: January 09, 2004, 03:44:00 PM »

My guess is that the problem has to do with the fact that there are only 5 textboxes on the screen at any given time.  When going 'next', each one moves in from the 'next' position.  Since there is no textbox that has 'next' as the topmost textbox, it disappears.

Maybe I'll add a duplicate text element at each end
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Upcoming Skinning Features
« Reply #59 on: January 09, 2004, 03:46:00 PM »

QUOTE (geniusalz @ Jan 9 2004, 07:44 PM)
My guess is that the problem has to do with the fact that there are only 5 textboxes on the screen at any given time.  When going 'next', each one moves in from the 'next' position.  Since there is no textbox that has 'next' as the topmost textbox, it disappears.

Maybe I'll add a duplicate text element at each end

Yes, that's it. It needs an "invisible" item on each end, for the end item to fade into.
Logged
Pages: 1 2 3 [4] 5