@NinjaCyborg

A GUI Amiga program will always use shared memory as it is required for the message passing from Intuition to the program.

@NinjaCyborg

If it were ported/created, what hardware would be used?

@arfcarl

Just set it in your Makefile. That's what I do.

gcc with -lstdc++ seems to work but I changed it to be g++ which implies the stdc++ lib.

I think my compiler setting (with -lstdc++) was before I started modifying the Makefile directly and so is not needed with g++.

@arfcarl

Hey arfcarl.

I have had a look at the configuration for a C++ project I am working on and the below config works for me with GCC 8.1.0. I imagine it will work with 8.3.0 but I don't want to upgrade in the middle of a project so haven't done it yet.
Sorry there are no images. I'm not sure how to upload them here. If someone were to tell me how it's done without hosting them, that would be handy

G++ Version Info:
g++ (adtools build 8.1.0) 8.1.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Make Tab Settings:
There is nothing special here, though I manage my own Makefile once the basic skeleton is generated.
I leave the Create Makefile unticked.
Builder name is "SDK:c/make -f"
Makefile name is "Makefile" though obviously change the name if yours is different.

Compiler Tab Settings:
Compiler name is set to "Specify >>" and the name supplied is "gcc:bin/g++"
I don't have anything further here that is special.

Target Settings:
I set up a target with the settings below ...
Linker Name is "gcc:bin/g++"
Linker Switches is "-lstdc++
Objects and libs specified as needed, though most is in the makefile.

The Makefile contains the following which may assist in your setup. It was originally generated automatically, then I edited it accordingly and stopped it generating automatically:
I also use Hans's debugging harness which is pretty handy.

Hope it all helps.

Cheers, Steady.

===================================
#
# HexSee Makefile
#

###################################################################
##
##//// Objects
##
###################################################################
HexSee_OBJ := \
HexSee.o \
RSApplication.o RSProcess.o RSTask.o \
RSWindow.o HSMainWin.o \
Debug.o retrami.o \
HexGadget.o

###################################################################
##
##//// Variables and Environment
##
###################################################################

CCPP := gcc:bin/g++
CC := gcc:bin/gcc

TARGET := HexSee

INCPATH := -I.

CPPFLAGS := $(INCPATH) -gstabs -mcrt=clib2 -athread=native
CFLAGS := $(INCPATH) -gstabs -mcrt=clib2 -athread=native

DFLAGS :=

# ----- UNCOMMENT DIFFERENT DFLAG LINES TO CHANGE THE LOGGING BEHAVIOUR -----
# DFLAGS for logging all debug messages
DFLAGS := -DDEBUG -DTARGET="$(TARGET)"

# DFLAGS for static debug level
#DFLAGS := -DDEBUG -DDEBUG_LOGLEVEL=DBG_WARNING -DTARGET="$(TARGET)"

# DFLAGS for user settable logging level

#DFLAGS := -DVARLEVEL_DEBUG -DTARGET="$(TARGET)"

###################################################################
##
##//// General rules
##
###################################################################

.PHONY: all all-before all-after clean clean-custom realclean

all: all-before HexSee all-after

all-before:
# You can add rules here to execute before the project is built
@echo "Copying latest binary and header from HexGadget project"
copy /HexGadget/HexGadget.h HexGadget.h
copy /HexGadget/HexGadget.o HexGadget.o

all-after:
# You can add rules here to execute after the project is built

clean: clean-custom
@echo "Cleaning compiler objects..."
@rm -f #?.o

realclean:
@echo "Cleaning compiler objects and targets..."
@rm -f #?.o HexSee

###################################################################
##
##//// Targets
##
###################################################################

HexSee: $(HexSee_OBJ)
@echo "Linking HexSee"
@$(CCPP) -o HexSee $(HexSee_OBJ) $(DFLAGS) $(CPPFLAGS)
@echo "Removing stale debug target: HexSee"
@rm -f HexSee.debug


###################################################################
##
##//// Standard rules
##
###################################################################

# A default rule to make all the objects listed below
# because we are hiding compiler commands from the output

.c.o:
@echo "Compiling $<"
@$(CC) -std=c11 -c $< -o $*.o $(DFLAGS) $(CFLAGS)

.cpp.o:
@echo "Compiling $<"
@$(CCPP) -std=c++14 -c $< -o $*.o $(DFLAGS) $(CPPFLAGS)

#
# C++ 2014
#
RSTask.o: RSTask.cpp RSTask.h retrami.h
RSProcess.o: RSProcess.cpp RSProcess.h RSTask.h retrami.h
RSApplication.o: RSApplication.cpp RSApplication.h RSProcess.h RSTask.h retrami.h
HexSee.o: HexSee.cpp HexSee.h RSApplication.h RSProcess.h RSTask.h retrami.h
RSWindow.o: RSWindow.cpp RSWindow.h retrami.h
HSMainWin.o: HSMainWin.cpp HSMainWin.h RSWindow.h retrami.h

#
# C 2011
#
debug.o: Debug.c Debug.h
retrami.o: retrami.c retrami.h

I use it with C++. I override it to specifically call g++.
I don't have the config with me where I am right now but can post it later if someone else doesn't do it first.
I have been using C++ with gcc 8.1

*** RESOLVED ***

I'm happy to say I was doing something stupid but just posting my answer in case anyone searching in future ...

Ummm .... I split the OM_SET and OM_UPDATE processing but forgot to move the code into OM_UPDATE that actually extracted the GadgetInfo from the passed message into a local variable and I was using that NULL variable when processing the update taglist ... oops

Anyway, I will still submit this example when done for people looking for an example of this stuff since there is not much around.

A couple of extra things.

This is on AmigaOS 4.1 FE.

I also tested by creating a separate scroller and propgclass gadget but the effect was the same ... very puzzling.

There are very few reaction gadget implementation samples so I plan to release the source for this gadget to help others in future if I can get this right.

Hi all,

I have question about a custom Reaction Gadget processing OM_UPDATE messages from another gadget.

My gadget is receiving updates from the Scroller gadget (or Prop gadget as there is no guarantee for a scroller) attached to the Window object (with WINDOW_VertProp tag).

I set up ICA_MAP and ICA_TARGET for the Scroller to point to my gadget and map SCROLLER_Top accordingly. I receive the update message from which I obviously want to upate my display. However, the GadgetInfo passed is always NULL.

I don't know how to either:
1) get scroller to supply GadgetInfo
2) or create a gadget info in order to trigger GM_RENDER.

I tried to workaround by processing the message in the application with IDCMP_IDCMPUPDATE by supplying the ICTARGET_IDCMP ICA_TARGET, but that means I cannot identify interim scroller reports and the gadget is overloaded. Plus, I believe this is not the philosophy of BOOPSI and I am probably going the wrong way about it.

Does anyone have some idea what I might be missing here to cause GadgetInfo to be NULL?

@mritter

Class is defined in intuition/classes.h

@Kamelito

That dos.library note is just saying that dos.library <36 is "special" and is not set up normally due to it primarily being a way to call the internal functions supplied by Tripos.

I don't think that implies you do not need to Forbid()/Permit() when patching >=36 functions on any library.

Personally, I think it comes down to the library in question ... Some (like exec) would likely need a Disable if you change functions that can be called from interrupts, otherwise Forbid would be enough. You wouldn't want to change the function right as another program is calling it.

Open up DiskImageGUI and select the disk you want gone ... then press the eject button.

Hmmm. Would appdir:odyssey work if odyssey had not yet been run a first time?

Awesome as usual!

@Thematic

On AmigaOS you can't have a window wider than the screen ... until recently.

The 3.1.4 version of intuition.library will let you do it and so does AmigaOS 4.x.

@Hans

I agree. Focusing on a faster hard reset would be more productive.

This will be really handy!

Have you tried replacing the battery?

@mritter0

I noticed that it was mounting GoogleDrive too in the same manner as was mentioned earlier. I was wondering if you were doing something special, but I guess it is just waiting to be mounted when searched for.

P.S. Program looks great. Nice work!

Oh, ok. Still good to know if someone else comes across this topic when trying to solve a similar issue.

How was it solved?