Stats

Replies 2
Subscribers 159
Views 1386
Members are here 0

Can't get popup to gray Oops

I have a popup definition like this:

(setq userData (axlUIGetUserData))
(putprop userData userData->popupId 'oldPopup)

(setq popupList (axlSelectPopupList))
(setq popupList (cons (list "Next" 'CAL_cvnNext) popupList))
(setq popupList (cons (list "Cancel" 'CAL_cvnCancel) popupList))
(setq popupList (cons (list "Oops" 'CAL_cvnOops) popupList))
(setq popupList (cons (list "Done" 'CAL_cvnDone) popupList))

(setq popupFull (axlUIPopupDefine nil popupList))
(putprop userData popupFull 'popupFull)

(setq popupList (axlSelectPopupList))
(setq popupList (cons (list "Cancel" 'CAL_cvnCancel) popupList))
(setq popupList (cons (list "Done" 'CAL_cvnDone) popupList))

(setq popupNoOops (axlUIPopupDefine nil popupList))
(putprop userData popupNoOops 'popupNoOops)

;Now activate the initial popup with "Oops" and "Next" grayed out
(axlUICmdPopupSet popupFull)
(axlUIPopupSet popupNoOops)

When this code is executed the popup will have Next and Oops grayed out, When a start transaction occurs I execute (axlUIPopupSet popupFull) and nothing is grayed out. If I rollBack this transaction and there are no more transactions to roll back I execute (axlUIPopupSet popupNoOops). But it doesn't gray out Next or Oops.

Anyone with any ideas on why it's not graying out Next or Oops?

Thanks,

Craig

Parents

eDave over 12 years ago

Hi Craig,

I haven't had a good look at your code yet but check for the declaration of
local variables. You may need to declare your transaction mark variable
(and others) as global.

Cheers,
Dave
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

eDave over 12 years ago

Hi Craig,

I haven't had a good look at your code yet but check for the declaration of
local variables. You may need to declare your transaction mark variable
(and others) as global.

Cheers,
Dave
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data

Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.