Paradox Community

Items in pnews.paradox-development

Subject:Re: make menu
Date:Mon, 5 Mar 2018 07:04:37 -0500
From:"Steven Green" <greens@diamondsg.com>
Newsgroups:pnews.paradox-development
so, ultimately, the rules for addtext() seem the same in p7 and p9.. 
"constant", done internally and/or manually, must be between 8000 and 
10000.. the values in that field, in the menu table, are between 50 and 
31000.. so, p7 ignores the rules completely, everything is enabled.. p9, 
everything between 8000 and 10000 is enabled, but so are 21000 and 29000..

so I renumbered everything in the 8000s, and went on to the next disaster..


--

Steven Green
Myrtle Beach, South Carolina, USA

http://www.OasisTradingPost.com

Collectibles and Memorabilia
Vintage Lego Sets and Parts
- and Paradox support, too
"Steven Green"  wrote in message news:5a9bf9b2$1@pnews.thedbcommunity.com...

yep, it was the way "constant" was being used.. differences between the book
and actual results.. I never used it that way, either, but I can change it
to make it complaint.. thanks for steering me in the right direction


--

Steven Green
Myrtle Beach, South Carolina, USA

http://www.OasisTradingPost.com

Collectibles and Memorabilia
Vintage Lego Sets and Parts
- and Paradox support, too
"Steven Green"  wrote in message news:5a96a41a$1@pnews.thedbcommunity.com...

I understand your point, I just haven't gone down that trail yet.. it worked
flawlessly up thru p7, so it's gotta be something internal like that, that
changed in a way we'd never see 99% of the time.. I won't have a chance to
go back to it for a few days.. I can probably modify the process to use the
real menu text, there's only one duplication in the actual menus, so it'll
be easy to alter one of them


--

Steven Green
Myrtle Beach, South Carolina, USA

http://www.OasisTradingPost.com

Collectibles and Memorabilia
Vintage Lego Sets and Parts
- and Paradox support, too
"Jim Moseley"  wrote in message news:5a95c88f$1@pnews.thedbcommunity.com...


Steven,

The more I think about it, the more I'm guessing the issue is the menuAction
constants.  If you just use random numbers, you'll probably run into the
'real' menuAction values, like SAVE, PRINT, etc.

So, to use your own values, you have to add UserAction to it.  This makes
sure you don't conflict.

I could see the standard menuAction values showing as disabled, since they
would only be actionable from their correct context.

(Note - all of this is off the top of my head, so I might have the
UserAction,
etc., wording wrong)

HTH,
Jim Moseley 


Copyright © 2004 thedbcommunity.com