关于头文件定义编号的问题

发布于 2024-08-18 01:29:06 字数 445 浏览 4 评论 0原文

我从未尝试过在没有 GUI 设计器的情况下开发 GUI，现在我正在通过《Palm OS 编程：开发人员指南》一书学习如何开发 Palm OS 应用程序。在它上面我有这段代码，它是一些 GUI 项目的声明：

#define HelloWorldForm 1000
#define HelloWorldButtonButton 1003
#define HelloWorldMenuBar 1000

#define GoodnightMoonAlert 1101

#define FirstBeep 1010

#define SecondBeepmore 1000

我想知道一些事情：

我需要以某种顺序执行此操作？
为什么我需要申报这个数字？
他们会在哪些方面帮助我？
他们有什么与他们的物品类型相关的东西吗？

原文

I never tried to do a GUI without a GUI designer and now I'm learning how to develop Palm OS applications with the book Palm OS Programming: The Developers Guide. And on it I have this code that is a declaration of some GUI items:

#define HelloWorldForm 1000
#define HelloWorldButtonButton 1003
#define HelloWorldMenuBar 1000

#define GoodnightMoonAlert 1101

#define FirstBeep 1010

#define SecondBeepmore 1000

I want to know some things:

I need to do this in a type of order?
Why I need to declare this numbers?
In what they are going to help me?
They have anything connected to the type of item they are?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

南街九尾狐 2024-08-25 01:29:06

它们是资源 ID。您不需要定义此类宏，但如果您不这样做，则当您尝试在代码中引用 UI 小部件时，您将不得不使用原始整数值。例如，获取指向 UI 控件的指针的典型方法是调用：

FormType* formP = FrmGetActiveForm();
UInt16 index = FrmGetObjectIndex(formP, objectID);
ControlType* controlP = FrmGetObjectPtr(formP, index);

您需要获取指向 UI 小部件的指针，以便执行诸如读取其状态（例如复选框）、更改资源 ID 和从 FrmGetObjectPtr 返回的

指针所做的操作之间不存在类型安全；您有责任跟踪哪个 ID 对应于哪种类型的控件（常见做法是使用描述性名称）。

They resource IDs. You aren't required to define such macros, but if you don't, you'll instead have to use the raw integer values when you try to refer to the UI widgets in code. For example, the typical way you'd get a pointer to a UI control would be to call:

FormType* formP = FrmGetActiveForm();
UInt16 index = FrmGetObjectIndex(formP, objectID);
ControlType* controlP = FrmGetObjectPtr(formP, index);

You'd need to get pointers to the UI widgets in order to do things such as reading their states (such as for checkboxes), changing text labels, showing or hiding them dynamically, etc.

There's no type safety between the resource IDs and what you do with the pointer you get back from FrmGetObjectPtr; it's your responsibility to keep track of which ID corresponds to which type of control (the common practice is to use descriptive names).

回复收藏 0 原文