Jorge Aldo G. de F. Junior wrote:
> and actually i prefer to setup properties of objects using xml
> properties instead of xml text
>
> instead of
> 192.168.1.180
Both examples are valid XML, so I don't see any issue the way I am using
it. My previous example was just that, an example. My actual
On Thu, 28 Jan 2010, Jorge Aldo G. de F. Junior wrote:
i mean that FPC-XML tries to be too general and this leads to too
cumbersome code in various situations (FPC-XML is clearly overkill for
my needs).
But FPC-XML is not meant for storing objects. It is meant to
read any correctly formed X
"Example XML, and there isn't a limit to the nesting of options."
no theres no limit for nested tags, they are stored in a tree plus a
linear list indexed by instance names
(nodes without instance names will receive a random instance name -
and be basically out of reach by the linear list - but w
but theres a flaw in my model (that doesnot means much in what im doing):
the properties in the XML file must match exactly the properties each
object has.
else the properties are lost..
(the xml file can have less properties than the object but not the
other way around: the xml loader cannot fo
i mean that FPC-XML tries to be too general and this leads to too
cumbersome code in various situations (FPC-XML is clearly overkill for
my needs).
2010/1/28 Michael Van Canneyt :
>
>
> On Thu, 28 Jan 2010, Jorge Aldo G. de F. Junior wrote:
>
>> im actually needing better RTTI as to allow easier m
each tag generates a new instance of the class
you can add a property (that all objects have) called InstanceName
something
using the instance name the class factory can differentiate from other
instances (factory.instance['blabla'] retrieves the correct instance,
or, factory.dotnotation['rootta
On 28 January 2010 16:10, Jorge Aldo G. de F. Junior wrote:
>
> Whenever the xml loader finds a it will
> create an instance of TMyClass and set the published properties
> accordingly (Using RTTI)...
I like that idea, but how flexible is? By that I mean, I have nested
tags (using the same elemen
On 28 Jan 2010, at 15:26, Felipe Monteiro de Carvalho wrote:
I am having trouble with the delphi mode and objective pascal. If I
use this defines:
{$mode delphi}{$modeswitch objectivec1}
Then I get an error in this line:
MainWindow.contentView.addSubview(TextField);
simpleform.lpr(63,26) E
Hello,
I am having trouble with the delphi mode and objective pascal. If I
use this defines:
{$mode delphi}{$modeswitch objectivec1}
Then I get an error in this line:
MainWindow.contentView.addSubview(TextField);
simpleform.lpr(63,26) Error: Unknown record field identifier "ADDSUBVIEW"
And
On Thu, 28 Jan 2010, Jorge Aldo G. de F. Junior wrote:
im actually needing better RTTI as to allow easier method invocation...
But generally i feel my way of doing XML is better than FPC defaults
(Too generic, tries to solve too many problems with the same code)
What exactly do you mean by
im actually needing better RTTI as to allow easier method invocation...
But generally i feel my way of doing XML is better than FPC defaults
(Too generic, tries to solve too many problems with the same code)
___
fpc-pascal maillist - fpc-pascal@lists.f
with my system would be simply something like
Type
TMyClass = Class(TXMLNode)
Private
fSomething : String;
Public
Constructor Create(Const aInstanceName : String); Override;
Class Function XMLTag: String; Override;
Published
Property Something : String Read fSomethi
On 28 Jan 2010, at 10:30, Roland Turcan wrote:
Hello friends,
It started to show this %subject% since I added some code into
The internalerror is 200501152, not 20051152
{$IF MyBoolCondition}
example:
That example does not compile, and even after fixing it so that it
does compile, it
Hello friends,
It started to show this %subject% since I added some code into
{$IF MyBoolCondition}
example:
{$MODE Delphi}
Unit MyUnit;
interface
Uses MyConditions;
{$IF MyCond}
//some declaration
implementation
// some code
{$ELSE}
//some declaration
implementation
// some code
{$IF
Uff,
first, I made a typo. I meant "class" instead of "call".. *g*
Thanks for the hint with the 64bit-thingy. :)
Second, I finally got it to work with some "assembler magic".
(Well, honestly, there is no magic after all. ;) )
=> http://www.lazarusforum.de/viewtopic.php?p=35280#p35280
Thanks f
On 28 January 2010 10:30, Michael Van Canneyt wrote:
>>
>>
>> SetObjectProp(AObject, LPropInfo, TObject(PtrUInt(APropValue)));
>
> This is correct _if_ APropvalue is a 64-bit integer on a 64-bit system.
In that case APropValue will be a reference to a Object. I trust
reference to objects on a 64
On Thu, 28 Jan 2010, Graeme Geldenhuys wrote:
Hi,
If I compile the code snippet shown below in 'mode delphi' it works fine.
If I try and compile it with 'mode objfpc' it fails with a compiler error
as shown here:
/home/graemeg/programming/personal/fpginstall/src/rttihelpers.pas(156,43)
Error
17 matches
Mail list logo
