Jump to content


Photo
- - - - -

INVALID GUI OBJECT SPECIFIED


2 replies to this topic

#1 Albert Ho

Albert Ho

    Member

  • Members
  • PipPip
  • 19 posts
  • Gender:Male

Posted 03 January 2003 - 03:26 AM

Hi, I got a question here that would like to ask anyone out there. I'm currently using Studio+ (comes with proiv 5.5000 with ActiveX support). When I try to add an ActiveX field into my LS logic, I got this error 'INVALID GUI OBJECT SPECIFIED', however I am able to add other types of GUI object. Prior to that step, I have successfully added quite a number of ActiveX components into my proiv repository from the Tools->ActiveX menu.

Thanks
Albert.

Attached Thumbnails

  • ActiveX_Error.jpg


#2 Andy Jones

Andy Jones

    Member

  • Members
  • PipPip
  • 41 posts
  • Gender:Male

Posted 03 January 2003 - 11:04 PM

Albert,

Run @VAR and edit &$@GUI_OBJ2. It appears there's a comma missing from the end which is causing this. That should fix it.

Andy
Nothing is foolproof to a sufficiently talented fool...

Don't learn from your own mistakes - it's safer and more entertaining to learn from the mistakes of others!

Just because you can, it doesn't mean you should!

#3 DARREN

DARREN

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 396 posts
  • Gender:Male
  • Location:Florida,USA

Posted 04 January 2003 - 12:06 AM

Just a little recommendation, gleaned from nothing more than my personal experience of developing GUI apps in PROIV. The definition of Buttons, Icons and ActiveX controls as dynamics (fields) binds them allot closer to the timing cycle. As such, when the cycle they belong to is exited, they are no longer active. They also do not become 'active' until they are visited in the timing cycle. It is far better to define such object on the format of the cycle - the objects are therefore 'available' as soon as the format (canvas) is rendered and they 'persist' for the life of the format. As the 'set properties' functionality is now available, their look and state can be changed dynamically. The one caveat to this general rule is their employment in paging screens and list boxes (icons only). As I say, this is only my personal recommendation, as PROIV supports both.
Things should be made as simple as possible, but not simpler



Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users